JP2003303199A - Knowledge information collecting system and knowledge information collecting method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To realize a mechanism for listing processing states of collection/ registering for each document collection. <P>SOLUTION: In a Web collecting module 111, a status information file for managing a progress state related to the document collection is produced in starting each document collection, and status information indicating the progress state of the document collection is written into the status information file corresponding to the document collection. In a registering module 12, a status indicating the progress state of the registering is written into the status information file corresponding to the document collection to be registered in response to the progress of the started registering. A status list screen indicating the present progress state related to each document collection is displayed on a screen through a managing interface 112 based on status information held in each status information file. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a knowledge information collecting system and a knowledge information collecting method used in a knowledge management system, and particularly to a knowledge information collecting system and knowledge for collecting document information to be registered in a knowledge database from a network. Regarding information collection method.

[0002]

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

This knowledge management system is for accumulating and managing knowledge information such as personal know-how in a knowledge database. By combining it with a search function such as natural language search, the accumulated knowledge information can be efficiently stored. It is possible to make full use of it.

By the way, in such a knowledge management system, how to efficiently collect and store knowledge information is an important point. In particular, since Web information on the Internet is a treasure trove of knowledge, a mechanism for efficiently collecting necessary information from the Internet is needed.

[0005]

However, when collecting Web information from the Internet, it is necessary to sequentially collect a large number of document file groups related to each other while following the link information. It usually takes a lot of time. Furthermore, in order to use the document information collected from the Internet as knowledge, it is necessary to register the document information in the knowledge database of the knowledge management system.
The registration process also takes time.

For this reason, particularly when a plurality of collection processes having different collection starting points are set and the collection results are registered in the knowledge database, the progress status greatly differs for each set collection process. It becomes difficult to understand which collection processing is what kind of collection / registration processing situation. Also, similar problems occur when collecting Web information and collecting information from other information sources such as a database at the same time.

The present invention has been made in consideration of such circumstances, and a knowledge information collecting system and a knowledge information collecting system capable of easily grasping the collecting / registering processing status of each of a plurality of document collecting processings. The purpose is to provide a method.

[0008]

In order to solve the above-mentioned problems, the present invention is a knowledge information collecting system for collecting document information to be registered in a knowledge database from a network. Document collection means for executing a plurality of document collection processes corresponding to each of the plurality of setting information based on each of the plurality of setting information indicating a collection condition, the document collection process being performed for each document collection process to be processed. A status information file for managing the progress of collection processing from the start of collection to registration is created, and the status information file corresponding to the document collection processing is created in accordance with the progress of the document collection processing to be processed. Document collecting means for writing status information indicating the progress of the document collecting process, and each document collecting process A registration request issued from the document collecting means each time it is completed, and a registration process for registering the result of the document collection process requested by the registration request in the knowledge database in the order in which the registration request is received. The registration means to be executed, and in accordance with the progress of the registration process that has started execution, status information indicating the progress status of the registration process is added to the status information file corresponding to the document collection process that is the target of the registration process. A status list screen showing the current progress status of each of the document collection processes based on the registration means to be written and the status information held in the status information file corresponding to each of the document collection processes for which the document collection process is started. And a status display means for displaying.

In this knowledge information collecting system, in the document collecting means, a status information file is created at the start of each document collecting process for managing the progress of the document collecting process from the collection start to the registration. In accordance with the progress of the document collection process, status information indicating the progress of the document collection process is written in the status information file corresponding to the document collection process.
A registration request is issued from the document collection means each time the document collection processing is completed, and the registration processing is executed by the registration means in the order in which the registration requests are received. In this registration means, the status information indicating the progress status of the registration process is written in the status information file corresponding to the document collection process that is the target of the registration process in accordance with the progress of the registration process that has started to be executed. . In this way, by using the status information file created for each document collection process and writing the progress status of the document collection process and the progress status of the registration process for each document collection process in the same status information file, It is possible to individually manage the status of collection / registration related to each document collection process in which the document collection process is started. Then, the status display unit displays a status list screen showing the current progress status of each document collection process based on the status information held in the status information file corresponding to each document collection process. Therefore, it is possible to easily grasp the collection / registration processing status of each of the plurality of document collection processing.

Further, according to the present invention, in a knowledge information collecting system for collecting document information to be registered in a knowledge database, the knowledge information collecting system is provided corresponding to each of a plurality of different information sources, and each of the information sources corresponds to a document file. A plurality of document collection means for executing a document collection process for collecting a group, wherein each document collection means manages the progress status from the collection start to the registration regarding the document collection process at the start of the document collection process. And a plurality of document collecting means for writing status information indicating the progress of the document collecting process to the status information file corresponding to the document collecting process in accordance with the progress of the document collecting process. Receiving a registration request issued each time each of the plurality of document collecting means completes the document collecting process, The registration means for sequentially executing the registration process for registering the result of the document collection process requested by the registration request in the knowledge database in the order in which the registration requests are received. In addition, a registration unit that writes status information indicating the progress status of the registration process to a status information file corresponding to the document collection process that is the target of the registration process, and the document collection started by the plurality of document collection units. Based on the status information held in the status information file corresponding to each processing, a status list screen showing the current progress status from the collection start to the registration regarding the document collection processing of each of the plurality of document collection means is displayed. And a status display unit for controlling the status.

In this knowledge information collecting system, a plurality of document collecting means are provided, and the document collecting process for each of a plurality of different information sources is executed. Even in this case, the document collecting process is also performed. By writing the progress status of the document collection processing and the progress status of the registration processing for each document collection process in the same status information file using the status information files created corresponding to each, for example, from the network. It is possible to manage the status of collection / registration related to various collection processing such as collection, collection from filing system, collection from database, etc.

[0012]

BEST MODE FOR CARRYING OUT THE INVENTION Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 shows the overall configuration of a knowledge management system using a knowledge information collecting system according to an embodiment of the present invention. This knowledge management system is for providing services such as collection, analysis, and search of knowledge information, and includes a Web collection system 11, a registration module 12, and a knowledge engine 13.
Etc. These Web collection system 1
1, the registration module 12, and the knowledge engine 13 are realized as a program executed on the server computer. The web collection system 11 and the registration module 12 configure a knowledge information collection system for collecting knowledge information used in the knowledge management system. This knowledge information collecting system executes a process of collecting a document such as a Web page from the Internet / Intranet 30 and registering the content of the document in a knowledge database (knowledge DB) 131 of the knowledge management system. Web collection system 11 is We
b collection module 111, management interface 11
2 and the registration directory 113.

The Web collection module 111 is a program for collecting various document files on the Internet / Intranet 30 and outputting them in a format that can be registered in the knowledge DB 131. This Web collection module 11
1 has a multi-thread structure, and HTTP (Hype
Document file acquisition processing from the Internet / Intranet 30 by rText Transfer Protocol) can be performed in parallel. HTTP is used by each Web server 31, which is an information site (Web site) on the Internet / Intranet 30, to send HTML (Hyper Text Markup).
Language) is a communication protocol for obtaining a document described in Language. Web collection module 111
URL specified in the setting information that specifies the collection condition (Unif
(orm Resource Locator) document file is acquired from the Internet / Intranet 30, and if the acquired document file contains the URL of the link destination, the URL
By further performing the recursive processing of further acquiring the document file of, the related document file group is sequentially acquired from the Internet / Intranet 30. In this case, it is necessary to analyze the acquired document file in order to detect the link information (URL) to another document file. In the analysis process, not only the detection of the link information but also the knowledge Extraction of text data to be registered in the DB 131 is also executed.

The document file to be collected is created not only by a hypertext file (HTML file) that can describe a URL that is link information to another file, but also by a text file (plane text) and various application programs. Document files of various file formats (for example, Portable Document Format files, document files created by word processing software, files created by spreadsheet software, presentation data files created by presentation data creation software, etc.) Be the target.

The Web collection module 111 acquires attribute information to be registered in the knowledge DB 131 and extracts the above-mentioned text data for each document file collected from the Internet / Intranet 30. The attribute information acquired from each document file is, for example, the URL of the document file, file creation date / time (update date / time), and the like. Then, the Web collection module 111 creates a registration file in which the attribute information of each of the document files and the text data are described, and outputs it to the registration directory 113. Here, the registration file is
It means a file having a predetermined description format as a common interface for registering document information of each of a plurality of types of document files having different file formats in the knowledge DB 131. This registration file is used to register the document information of each of a plurality of types of document files in the knowledge DB 131 in a common format. In this embodiment,
XML (eXtensible Markup Langua) as a registration file
ge) is used.

The management interface 112 is a program for setting the contents of each web collection process (hereinafter referred to as a web collection process task) to be executed by the web collection module 111, and the web collection conditions for each web collection process task. Of the Web collection module 111, and the functions of managing and presenting the collection status of each Web collection processing task. This management interface 112 allows the web server 22 to execute CGI (Common) so that an administrator user can perform necessary operations on the web browser 21 of the user terminal.
It is realized as an external program (CGI program) that can be started through the Gateway Interface.

Further, the Web collection system 11 includes a Web
As a file for managing and controlling the operation of the collection module 111, a lock file 201,
A control file 202, a setting file 203, a result file 204, and a log file 205 are provided.

The lock file 201 is a file for exclusive control for preventing double activation of the Web collection module 111. The control file 202 is a file used by the management interface 112 to stop the Web collection module 111. For example, in the case of interrupting a Web collection processing task that is being executed in response to an instruction from an administrator user. Used for. The administrator user can specify the interruption during the collection execution through the management interface 112.

The setting file 203 is a file for describing setting information for designating the Web collection condition for each Web collection processing task, and here, a plurality of setting information corresponding to each of the plurality of Web collection processing tasks is set. Can hold. The web collection condition of each web collection processing task is set by the administrator user. The Web collection conditions include at least the origin address information (origin URL) indicating the location of the document file that should be the origin of information collection from the Internet / Intranet 30, and the upper limit of the number of document files or the number of link stages to be collected. It includes the collection range information, etc. The web collection operation of the web collection module 111 is controlled based on the web collection conditions. That is, the Web collection module 111 sequentially collects the document file group related to the document file specified by the starting point URL within the range defined by the collection range information.

The Web collection condition also includes a knowledge database name that specifies the knowledge database of the registration destination. That is, in the knowledge DB 131, a plurality of knowledge databases having different types of accumulated documents are defined, and the plurality of knowledge databases are managed by respective knowledge database names. Configuration file 20
By designating the knowledge database name of the registration destination for each Web collection task by the setting information of 3, the collected document information can be registered in an arbitrary knowledge database in the knowledge DB 131.

Further, as the collection range information, it is possible to set the type of file format to be collected, the collection condition when recollecting, and the like. Here, recollection means
For example, it refers to the second and subsequent web collection processes when the same web collection processing task is periodically executed by the web collection module 111, and the web collection process when the interrupted web collection processing task is restarted.

The result file 204 includes a list of previously collected document files and the like as a result of the Web collection process for each W.
This is a file for managing each eb collection task, and here, a list of URLs acquired as a result of Web collection, acquisition date and time, the number of acquired document files, etc.
It is output for each eb collection processing task. The result file 204 is used for the purpose of presenting the collection status of each Web collection processing task to the user and for the purpose of improving the efficiency of recollection. This result file 204 is used to detect a document file deleted from an information site on the Internet / Intranet 30 among the document files that have been collected in the past, or a restart point when the Web collection process is interrupted midway. Can be detected, and further, the document file updated on the Internet / Intranet 30 from the time of the previous collection can be detected.

The log file 205 is a file for managing the success or failure of acquisition of a document file by the Web collection module 111 and the type of error.

The registration directory 113 is a knowledge DB 13
This is a storage area for outputting the document content to be registered in 1. The above-mentioned registration file in which the attribute information and the text data extracted from each document file by the Web collection module 111 are described is output here. Web
The collection module 111 has two first and second processing modes for extracting text data.

In the first processing mode, analysis processing is performed on document files of all file formats to extract text data, and link information (URL) is detected (URL is detected only in HTML files. Target).
In the second processing mode, only the HTML file and the text file (PlainText) are analyzed to extract the text data and further the link information (URL) is detected (URL is detected only in the HTML file. ), For example, the analysis process is not performed on a document file of another file format such as Portable Document Format (hereinafter referred to as a content file).

When the second processing mode is used, HTML
With regard to PlainText, the text data and attribute information are described in the registration file and output to the registration directory 113. On the other hand, Portable Document
For files of other formats such as Format, the content file is output as it is to the registration directory 113, and the attribute information of the file and the path name of the content file are described on the registration file. In addition, in the second processing mode, it is important to perform the extraction of the text data in the analysis process for the file that needs the analysis process for detecting the link information. You may make it extract text data only for a target.

In both the first and second processing modes, the Web collecting module 111 is
When the processing of the collection task is completed, the registration module 12
To request the registration module 12 to register the document. In the registration request file, the file name of the registration file, the knowledge database name of the registration destination, etc. are described.

The registration module 12 registers the attribute information and text data of each document file collected by the Web collection module 111 in the knowledge DB 131.
That is, the registration module 12 acquires the corresponding registration file in response to the registration request from the Web collection module 111, extracts the attribute information and text data described for each document file on the registration file, and acquires the knowledge. It is registered in the registration destination knowledge database of the DB 131. The registration module 12 also has a text data extraction function, and if the path name of the content file is described in the registration file, the registration module 12 will use the text from the content file specified by the path name. The data is extracted and registered in the relevant registration destination knowledge database of the knowledge DB 131.

Further, the registration module 12 also executes the registration process of the documents collected by the collection modules other than the Web collection module 111. Other collection modules include, for example, a file collection module that collects document information from a file server of an electronic filing system, a database (RDB) collection module that collects document information managed by the RDB database server, and an electronic bulletin board format. Community collection module that collects the document information posted there from the community, the user collection module that the user uses to convert the document files of various application programs into the output format of the registration file (XML), and the like. The registration module 12 is commonly used by each of these collection modules. The registration file in the XML format described above is used as an interface to the registration module 12 for any of the collection modules. That is, the registration module 12 receives the registration request issued each time each collection module completes the collection task, and in the order of reception of the registration request, the registration file of the registration file which is the result of the document collection processing requested by the registration request. A registration process for registering the contents in the corresponding registration destination knowledge database of the knowledge DB 131 is sequentially executed.

The knowledge engine 13 performs a knowledge analysis process for utilizing the information accumulated in the knowledge DB 131. In this knowledge analysis process, a process of analyzing a feature of each of a large amount of document information accumulated in the knowledge DB 131 and extracting an important word, a clustering process of classifying and organizing the document information into a plurality of categories according to the feature, and the like are performed. Be seen.
The knowledge engine 13 is provided with a knowledge engine 132 for performing a natural language search, and each user accesses the knowledge engine 132 from the web browser 41 of the user terminal through the web server 42.
The knowledge accumulated in the knowledge DB 131 can be searched from the Web browser 41. Since the attribute information of each document stored in the knowledge DB 131 also includes the URL of the document, the original document can be acquired from the corresponding information site and displayed on the Web browser 41. The search process can be performed by selecting a certain knowledge database name and targeting only the selected knowledge database, or by targeting all knowledge databases in the knowledge DB 131.

Next, the functional configuration of the Web collection module 111 will be described with reference to FIG. The web collection module 111 includes a collection control unit 301,
It has an attribute extraction unit 302, a text extraction unit 303, and a format conversion unit 304. Collection control unit 301
For each of all the setting information held in the setting file 203, the Web specified by the setting information
Run collection tasks one at a time. A group of related document files is sequentially collected from the Internet / Intranet 30 starting from the starting point URL designated by the setting information for each Web collecting task. The URL to the linked document included in the acquired document file is the URL list 30
5, the collection processing is recursively executed while acquiring URLs from the URL list 305. URL
The result file 204 described above can be used as the list 305. The collection range is limited by the collection conditions held in the setting file 203.

Each collected document file is first sent to the attribute extraction unit 302, where the attribute information of each document file is acquired. Next, the text extraction unit 303 analyzes the document and extracts the text data to be registered in the knowledge DB 131 and the link destination URL to be acquired next. For example, for an HTML file, extraction of text data is performed by extracting a portion other than the HTML tag. The extracted text is divided into a title and a body (body). The link destination URL is acquired by acquiring the HREF value of the A tag and the AREF tag, the SRC value of the FRAME tag, the IFRAME tag, the LAYER tag, and the REFRESH value of the META tag. When operating in the above-described second processing mode, the processing of the text extracting unit 303 is H
This is done only for TML files and text files, not for document files of other file formats such as Portable Document Format.

The attribute information and text data acquired from each document file are sent to the format conversion unit 304,
Then, it is formatted into an output format according to the description format of the XML registration file and is output on the registration directory 113. In one registration file, for example, attribute information and text data for about 1000 document files are described. The attribute information and path name of the document file for which the text extraction has not been performed are described in the registration file.

The above processing is similarly performed for each document file collected by recollection.

Next, an example of the output format of the registration file will be described with reference to FIGS. 3 and 4.

FIG. 3 shows an example of an output format when the text extraction unit 303 extracts text. Tag at the beginning of the file <? Xml version = "1.0" encod
ing = "Shift_JIS"?>, <KnowledgeSystem> indicates the beginning of the file, and the end tag </ KnowledgeSystem>
Indicates the end of the file.

Attribute information and text data of one document file are described in each record enclosed by <RECORD> and </ RECORD>. The meaning of the tag in each record is as follows.

MODE: Mode information for designating the operation mode of the registration module 12. This mode information instructs registration or deletion of document information (text data and attributes) in the knowledge DB 131 for each document file.
Either 2 = registration (overwrite) or 0 = delete. In case of deletion, only TYPE and UNIQUE of the following tags are output.

TYPE: Indicates the type of collection. In this example, it is always "Web collection". UNIQUE: A unique key for identifying the document file registered in the knowledge DB 131. Usually, the URL of the document is used as a unique key.

ORGDATE: Indicates the creation date (or update date) of the document file. TITLE: Indicates the title of the document file. The text data extracted from the title part of the HTML file becomes the title. No title is output for files other than HTML files. This title is used as the title of each document file displayed on the search screen.

AUTHOR: Describe the host name (host address of URL) of the information site that owns the document file. DATE: Describe the date part of ORGDATE above. URL: URL of the document file. It has the same value as UNIQUE. BODY: The text data extracted from the document file is described.

FIG. 4 shows an example of an output format relating to a document file for which the text extraction unit 303 has not performed text extraction.

No text data is described in BODY.
In PATH1 in the area enclosed by BDYFILE></BDYFILE>, the path name to the content file output on the registration directory 113 is described. DEL = 1 instructs the registration module 12 to delete the original file in the registration directory 113 after extracting the text data from the content file. If the Web collection module 111 operates in the second processing mode, the HT
Text data is described in BODY for the ML file and plain text, and the path name of the content file is described in BDYFILE for document files (content files) of other file formats.

Next, referring to the flowchart of FIG.
Web collection module 1 for collected document files
A procedure of a series of processing executed in 11 will be described.

First, the knowledge DB is acquired from the collected document files.
Attribute information to be registered in 131 (URL, AUTHOR, ORGDATE,
DATE) is acquired (step S101). The attribute information can be acquired by using the value returned from the information site by HTTP, the value added in the collected document file, or the like. After that, in the second processing mode, the file type is determined based on the extension of the collected document file, and the file is an HTML file, a plain text file, or a file of another file format other than that. Is determined (steps S102 and S103). The collected document file is H
If the file is a TML file or a plain text file (YES in step S103), the above-mentioned text extraction processing (text extraction and link URL detection in the case of an HTML file) is executed (step S10).
4), and processing to describe the attribute information and text data in the above-mentioned format on the registration file (text data is BODY
Is inserted) (step S105). On the other hand, HT
If the file has a file format other than the ML file or the plain text file (step S103)
No), the file is directly output to the registration directory 113 (step S106), and then the attribute information and the path name of the file are described in the registration file (the path name is described in BDYFILE) ( Step S107).

If the document file of the target URL cannot be acquired from the Internet / Intranet 30, the content of the document file is already in the knowledge DB1.
Mode information (MOD
E) = 0 (delete) is described in the registration file.

Further, in the first processing mode, the processes of steps S102 and S103 are not performed, but the processes of steps S104 and S105 are executed for all the acquired files.

Next, referring to the flowchart of FIG.
The procedure of the registration process executed by the registration module 12 will be described.

Upon receiving the registration request from the Web collection module 111, the registration module 12 acquires the registration file (XML file) specified by the registration request file from the Web collection module 111 from the registration directory 113, and from the registration file. While fetching records one by one, the following processing is performed for each record. First, it is checked whether the mode information in the record to be processed is MODE = 0 or MODE = 2 (step S111,
S112).

When MODE = 2, the registration module 12
Is the data item (TYPE, UNIQUE, ORGDATE, TITLE, AUTH) described in each tag according to each tag in the record.
The contents of OR, DATE, URL, and BODY) are registered in the registration destination knowledge database in the knowledge DB 131 specified by the registration request file (step S113). If the text data does not exist in the BODY tag, the text data will not be registered. Then, it is judged whether or not the path name is described in the tag of BDYFILE (step S114). If the path name is described (YES in step S114), the corresponding content file is acquired from the storage area specified by the path name (step S115), and the process of extracting text data from the content file is executed. Performed (step S1
16). Then, the extracted contents are registered in the registration destination knowledge database as text data of the corresponding document file (step S117).

When MODE = 0, the attribute information and text data of the registered document file designated by UNIQUE in the record are searched from the knowledge DB 131, and the registered content is deleted from the registration destination knowledge database (step S118).

Similar processing is executed for registration requests from each collection module other than the Web collection module 111. Since there is one registration module 12 in this system, the registration processing is executed one by one in order.

FIG. 7 shows the relationship between the state of the document file (Web content) on the Internet / Intranet 30 and the registration / deletion process to be performed on the knowledge DB 131. In the present embodiment, the following processing is performed based on the policy of reflecting the state of the latest Web content on the Internet / Intranet 30 in the knowledge DB 131 as much as possible.

(1) The updated Web content is overwritten on the knowledge DB 131 (MODE = 2). Updated W
When registering the attribute information and text data of the eb content, the UNIQUE is the same as the UNIQUE of the pre-update Web content already registered in the knowledge DB 131. Therefore, MODE = 2 updates (overwrites) the attribute information and text data of the pre-update Web content already registered in the knowledge DB 131 with the updated Web content attribute information and text data.

(2) The added Web contents are additionally registered in the knowledge DB 131 (MODE = 2). When registering the attribute information and text data of the added Web content, the UNIQUE is not registered in the knowledge DB 131. Therefore, by setting MODE = 2, the attribute information and text data of the added Web contents are stored in the knowledge DB 13.
You can additionally register to 1.

(3) The deleted Web contents are also deleted from the knowledge DB 131 (MODE = 0).

Next, the functions provided by the management interface 112 will be specifically described. As described above, the management interface 112 sets the Web collection task settings /
It is a user interface for managing and executing,
1) A function of creating a plurality of settings of a Web collection task and saving them in the setting file 204. 2) A function of performing management work such as displaying a list of collection settings and deleting. 3) Starting and ending collection (interruption and interruption). Resuming) function, 4) Status list display function that presents the collection status and results in real time,
To the admin user. The status list display function is a function of displaying a list of collection / registration statuses of all collection tasks on the screen of the administrator user's Web browser 21, and the administrator user can easily display the status for each collection task. The status such as “collecting”, “waiting for registration”, and “registering” is displayed so that the user can understand.

Here, "collecting" is a status indicating that the corresponding collecting task has been started and the collecting process is being executed. In the case of "collecting", the current number of collected items is also displayed. “Waiting for registration” is a status indicating that the collecting process of the corresponding collecting task is completed and is waiting for the registering process by the registration module 12. “Registering” is a status indicating that the registration process by the registration module 12 has started and is in the process of being registered. In the case of "registering", the number of registered items is displayed. The status indicating the status of collection / registration is updated in the order of “collecting” → “waiting for registration” → “registering”.

Next, with reference to FIG. 8, a mechanism for realizing the status list display of each collecting task will be described.

As described above, in this system,
Not only the Web collection module 111, but also the file collection module, the RDB collection module, the community collection module, and the user collection module are operating, and the registration module 12 is commonly used by these plurality of collection modules. Since the processing executed by each collection module for status management is the same, the function for status management will be described below, focusing on the Web collection module 111.

The web collection module 111 sequentially executes a plurality of web collection tasks designated by a plurality of setting information held in the setting file 203. In this case, the Web collection module 111 uses the W
For each eb collection task, a status information file 311 specific to the Web collection task is created at the start of the eb collection task.
The status information file 311 is a file for managing the progress status from the collection start of the Web collection task to the registration. For example, the setting name of the Web collection task and the year / month / day / hour / minute / second of the collection start. It is managed by the file name including and. At the time of creating the file, status information indicating “collecting” is written in the status information file 311. Then, the collection processing by the Web collection module 111 is performed while updating the value of the number of collections in the status information file 311. Web
When the collection processing by the collection module 111 is completed,
The Web collection module 111 writes status information indicating “waiting for registration” to the status information file 311, updates the status from “collecting” to “waiting for registration”, and then describes the document information collected by the Web collecting task. The registration file (XML file) and the registration request file including the registration request are output to the registration module 12.
The registration request file includes the file name of the status information file 311 corresponding to the corresponding Web collection task.

In accordance with the progress of the registration process that has started to be executed, the registration module 12 writes status information indicating the progress status of the registration process in the status information file 311 corresponding to the Web collection task that is the target of the registration process. Write. In this case, the status is updated from "waiting for registration" to "registering" at the start of the registration process. Then, the registration processing by the registration module 12 is performed while updating the value of the number of registrations in the status information file 311. When the registration process is completed, the corresponding status information file 311 is deleted by the registration module 12.

As described above, by writing the progress status of the collection processing and the progress status of the registration processing for each Web collection task in the same status information file 311, the collection / collection for each Web collection task for which the collection processing is started is started. The registration status can be managed individually.

The status list display program 312 is a program provided to display the status list display screen 313 on the terminal of the administrator user, and is realized as a part of the management interface 112 described above.
This status list display program 312 shows the current progress status from the start of collection to the registration of all collection processing based on the contents of the status information file 311 created each time a plurality of collection modules starts collection. The status list display screen 313 is displayed.

FIG. 9 shows the status list display screen 313.
An example of is shown. As shown in the figure, on the status list display screen, for each collection task started by a plurality of collection modules, "knowledge database name", "collection type", "setting name (collection task name)",
"Collection target", "Status", "Target number (Registered number / Collected number)" are displayed. In FIG. 9, the Web
For collection, the setting name (collection task name) is info
Three collection tasks of 1, info2 and info3 are executed, and the task of info1 is "registering", inf
It is shown that the task of o2 is “waiting for registration” and the task of info3 is “collecting”. Furthermore, the file collection task by the file collection module, the user collection task by the user collection module, the community collection task by the community collection module, and the two RDB collection tasks by the RDB collection module are also started, and the file collection task and the user collection task respectively "Waiting for registration", community collection task is "collecting", 2 RDs by RDB collection module
One of the B collection tasks is “waiting for registration” and the other is “collecting”. Since there is only one registration module 12, there is always one "registering" task. Also, for each collection module, there is always one task that is “collecting”.

Further, the status list display screen 313 is provided with a "status update" button 401 and a "status delete" button 402. When the “update status” button 401 is pressed, the status of each task is updated to the latest status. "Delete status" button 4
02 indicates the status display of the task selected on the status list display screen 313.
Used when removing from.

FIG. 10 shows the Web collection module 111.
The status information update processing by the registration module 12 is also shown.

(1) At the start of the Web collection task, W
A status information file 311 is created by the eb collection module 111, and the status information “collecting” is written therein. (2) During the collection process, the Web collection module 111
Every time a new document file is collected, the collection number information of the status information file 311 is updated. (3) When the collection process is completed, the Web collection module 1
11 is “waiting for registration” in the status information file 311
The status information of is written and the current status is updated from “collecting” to “waiting for registration”. (4) Then, the Web collection module 111 issues a registration request file to the registration module 12, and requests the registration module 12 to execute the registration process. After this, the web collection module 111 can start the next web collection task.

(5) At the start of the registration process, the registration module 12 writes the status information of "registering" in the status information file 311, and updates the current status from "waiting for registration" to "registering". (6) During the registration process, the registration module 12 updates the registration count information of the status information file 311 every time new document information is registered. (7) When the registration process is completed, the registration module 12
The status information “waiting for registration” is written in the status information file 311, and the current status is updated from “collecting” to “waiting for registration”. After this, registration module 1
2 starts the next collection task waiting for registration. The contents of the status information file 311 are periodically (for example, every 30 seconds) checked by the status list program 302, and the current status of each task is displayed on the status list display screen 313. When the "state update" button 401 is pressed, the contents of the status information file 311 are checked by the status list program 302 at that time, and the status list display screen 313 is updated to the latest state.

Next, with reference to the flowchart of FIG. 11, a series of processing procedures executed by the Web collection module 111 for each Web collection task will be described.

When executing the Web collection task, first,
The status information file 311 corresponding to the Web collection task to be processed is created, and the status information indicating "collecting" is written therein (step S20).
1). After that, the Web collection process of sequentially acquiring the document file group from the Internet / Intranet 30 is started based on the setting information corresponding to the Web collection task held in the setting file 203 (step S202). In the Web collection process, the document file specified by the origin URL is first acquired, and if the link destination URL is included, it is added to the result file 204. Every time the document file is acquired, the collection number information of the status information file 311 is updated by +1 (step S203). Then, it is determined whether or not the Web collection processing is completed depending on whether or not an uncollected URL is registered in the result file 204 (step S204). Until there are no uncollected URLs in the result file 204, the process of acquiring the document file specified by the URL (step S20).
2) and the collection number information update process (step S203) are repeatedly executed.

When the Web collection process is completed (step S
(YES at 204), after the status information indicating “waiting for registration” is written in the status information file 311, the current status is updated from “collecting” to “waiting for registration” (step S205), and then the registration request file. Is issued (step S206).

Next, with reference to the flowchart of FIG. 12, a procedure of a series of registration processes executed by the registration module 12 for each Web collection task will be described.

At the start of the registration process, first, the status information indicating "registering" is written in the status information file 311 corresponding to the Web collection task to be registered, which is designated by the registration file, and the current status is displayed. Is updated from "waiting for registration" to "registering" (step S211). Next, registration processing is performed in which the document information (attribute information and text) is registered in the knowledge database of the registration destination while fetching records one by one from the registration file (step S212). Every time the document information is registered, the registration number information of the status information file 311 is updated by +1 (step S213). The processes of steps S212 and S213 are repeatedly executed until registration of all records is completed. When registration of all records is completed (N in step S214)
O), the status information file 311 is deleted (step S215). By deleting this file, the Web collection task for which the registration process has been completed is automatically excluded from the status list display targets. The status list display program 312 includes all status information files 31.
1 is checked periodically, but by automatically deleting the corresponding status information file 311 when registration is completed, only the status information file 311 corresponding to each running task can be checked.

As described above, according to this embodiment, the collection / registration statuses of all the collection processes in operation can be displayed in a list, so that the administrator user does not perform log analysis or the like. It is possible to easily understand which collection process is in what kind of situation among the set collection processes.

Since all the functions of the knowledge information collecting 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 stored through the storage medium. It is possible to easily obtain the same effect as that of the present embodiment only by installing the program in a normal computer that can be connected to a computer network and executing the program.

Further, the present invention is not limited to the above-mentioned embodiment, but can be variously modified at the stage of implementation without departing from the spirit of the invention. Furthermore, 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 constituent elements are deleted from all the constituent elements shown in the embodiment, the problem described in the section of the problem to be solved by the invention can be solved, and the effect described in the section of the effect of the invention can be solved. When the above is obtained, the configuration in which this constituent element is deleted can be extracted as the invention.

[0078]

As described above, according to the present invention,
It is possible to easily grasp the collection / registration processing status of each of a plurality of document collection processing.

[Brief description of drawings]

FIG. 1 is a block diagram showing the configuration of a knowledge information collecting system according to an embodiment of the present invention.

FIG. 2 is an exemplary block diagram showing the functional configuration of a Web collection module provided in the knowledge information collection system of the same embodiment.

FIG. 3 is a diagram showing an example of an output format of a registration file used in the knowledge information collecting system of the embodiment.

FIG. 4 is an exemplary view showing another example of an output format of a registration file used in the knowledge information collecting system of the embodiment.

FIG. 5 is an exemplary flowchart showing a processing procedure of a Web collection module provided in the knowledge information collection system of the embodiment.

FIG. 6 is an exemplary flowchart showing a processing procedure of a registration module provided in the knowledge information collecting system of the embodiment.

FIG. 7: We in the knowledge information collecting system of the same embodiment
The figure which shows the relationship between b content and its registration processing.

FIG. 8 is a view for explaining the principle of status list display by the knowledge information collection system of the same embodiment.

FIG. 9 is an exemplary view showing an example of a status list display screen used in the knowledge information collecting system of the embodiment.

FIG. 10 is an exemplary view for explaining status information update processing by each of the Web collection module and the registration module provided in the knowledge information collection system of the embodiment.

FIG. 11 is an exemplary flowchart for explaining a series of processing procedures executed by each Web collection task by the Web collection module provided in the knowledge information collection system of the embodiment.

FIG. 12 is an exemplary flowchart illustrating a procedure of registration processing executed by a registration module provided in the knowledge information collecting system of the embodiment.

[Explanation of symbols]

11 ... Web collection system 12 ... Registration module 13 ... Knowledge engine 30 ... Internet / Intranet 111 ... Web collection module 112 ... Management interface 113 ... Registration directory 131 ... Knowledge database 132 ... Search engine 201 ... Lock file 202 ... control file 203 ... Setting file 204 ... Result file 205 ... log file 301 ... Collection control unit 302 ... Attribute extraction unit 303 ... Text extraction unit 304 ... Format conversion unit 311 ... Status information file 312 ... Status list display program 313 ... Status list display screen

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Koji Shioda             2-9 Suehiro-cho, Ome City, Tokyo Stock Market             Company Toshiba Ome Factory F term (reference) 5B075 ND03 NK44 QP01

Claims (8)

[Claims] 1. A knowledge information collecting system for collecting document information to be registered in a knowledge database from a network, wherein a plurality of the plurality of setting information indicating a collection condition of a document file group from the network are set. A document collection unit that executes a plurality of document collection processes corresponding to respective setting information, and manages the progress status from the collection start to the registration regarding the document collection process at the start of each document collection process to be processed. And a document collection unit that writes status information indicating the progress status of the document collection process to a status information file corresponding to the document collection process in accordance with the progress of the document collection process to be processed. , A registration request issued from the document collecting means each time each document collecting process is completed It is a registration unit that sequentially executes a registration process for registering the result of the document collection process requested by the registration request in the knowledge database in the order of acceptance and reception of the registration request. A registration unit that writes status information indicating the progress status of the registration process to a status information file corresponding to the document collection process that is the target of the registration process according to the progress, and a document collection process in which the document collection process is started. Knowledge comprising a status display means for displaying a status list screen showing the current progress status of each document collection process based on the status information held in the status information file corresponding to each process Information collection system. 2. The registration means includes means for deleting a status information file corresponding to the document collection process that was the target of the registration process when the registration process started was completed. Knowledge information collection system. 3. The document collection means writes status information indicating that the document collection process is being collected into a status information file corresponding to the document collection process at the start of the document collection process, and the started document When the collection process is completed, the status information of the status information file corresponding to the completed document collection process is
The registration means includes means for updating the status information indicating that the registration processing is being waited for by the registration means, and the registration means stores the status information file corresponding to the document collection processing targeted for the registration processing at the start of the registration processing. A means for updating the status information to the status information indicating that the registration process is being executed, and deleting the status information file corresponding to the document collection process which was the target of the registration process when the registration process started is completed. The knowledge information collecting system according to claim 1, further comprising: 4. The status information file includes document collection number information indicating the number of document files collected in the document collection process, and document information corresponding to each document file registered in the registration process. The document collection number information indicating the number of cases is included, and the document collection unit updates the document collection number information of the status information file every time a document file is collected from the network by the started document collection process. 4. The knowledge according to claim 3, wherein the registration means includes means for updating the document registration number information of the status information file every time the document information is registered in the knowledge database by the started registration process. Information collection system. 5. A knowledge information collecting system for collecting document information to be registered in a knowledge database, wherein the knowledge information collecting system is provided for each of a plurality of different information sources, and each collects a document file group from the corresponding information source. A plurality of document collecting means for executing the document collecting process for managing the progress of the document collecting process between the start of collection and the registration of the document collecting process at the start of the document collecting process. Create a status information file, and according to the progress of the document collection process,
A plurality of document collecting means for writing status information indicating the progress status of the document collecting processing into a status information file corresponding to the document collecting processing, and issued each time each of the plurality of document collecting means completes the document collecting processing. Registration means for accepting a registration request for registration, and sequentially executing registration processing for registering the result of the document collection processing requested by the registration request in the knowledge database in the order in which the registration request is received. A registration unit that writes status information indicating the progress status of the registration process to a status information file corresponding to the document collection process that is the target of the registration process, according to the progress of the registered process; Therefore, the status stored in the status information file corresponding to each document collection process started Knowledge comprising: a status display means for displaying a status list screen showing the current progress status from the start of collection to the registration regarding the document collection processing of each of the plurality of document collecting means based on the information. Information collection system. 6. The plurality of document collecting means, at least a first document collecting means for collecting document information published on an information site on a network, a file server of an electronic filing system, a database server, or an electronic filing system. The knowledge information collecting system according to claim 5, further comprising: second document collecting means for collecting document information from a bulletin board type community. 7. A knowledge information collecting method for collecting, from a network, document information to be registered in a knowledge database, based on each of a plurality of setting information indicating a collection condition of a document file group from the network, A document collection step that executes a plurality of document collection processes corresponding to each setting information, and manages the progress status from the collection start to the registration regarding the document collection process at the start of each document collection process to be processed. And a document collection step of writing status information indicating a progress status of the document collection process to a status information file corresponding to the document collection process according to the progress of the document collection process of the processing target. Is issued from the document collecting step each time each document collecting process is completed. A registration step of accepting a recording request, and sequentially executing a registration process for registering the result of the document collection process requested by the registration request in the knowledge database in the order in which the registration request is received. A registration step of writing status information indicating the progress status of the registration process to a status information file corresponding to the document collection process targeted for the registration process according to the progress of the registration process, and the document collection process is started. A status display step of displaying a status list screen showing the current progress status of each of the document collection processes based on the status information held in the status information file corresponding to each document collection process. How to collect knowledge information. 8. A knowledge information collecting method for collecting document information to be registered in a knowledge database, wherein a document collecting process for collecting a document file group from a plurality of different information sources is performed. In the document collection step to be executed, a status information file is created for each document collection process for each information source at the start of the document collection process for managing the progress of the document collection process from the start of collection to the registration. Then, according to the progress of the document collection process, a document collection step of writing status information indicating the progress status of the document collection process into a status information file corresponding to the document collection process, and a document for each of the information sources. Accepts a registration request issued from the document collection step each time the collection process is completed,
It is a registration step that sequentially executes a registration process for registering the result of the document collection process requested by the registration request in the knowledge database in the order in which the registration request is received. Together,
A registration step of writing status information indicating the progress of the registration process to a status information file corresponding to the document collection process that is the target of the registration process, and a document collection process for each of the multiple types of information sources. A status display step of displaying a status list screen showing the current progress status of each document collection process performed on the plurality of types of information sources, based on the status information held in the corresponding status information file. A method for collecting knowledge information, characterized by: