JP4811451B2 - Database system and data generation method - Google Patents

Description

  The present invention relates to a search technique for information stored in a database.

  Conventionally, various systems (information retrieval systems) for searching knowledge data in a database have been constructed in order to efficiently use data (knowledge data) accumulated as knowledge in specific groups such as companies and academic societies. Yes. In such an information retrieval system, it is generally not preferable to give access rights to all users from the viewpoint of confidentiality. Therefore, when a user tries to search for knowledge data in a database, the password input, etc. And whether or not the user has an access right to the knowledge data is managed to determine whether or not search is possible (for example, Patent Document 1).

  Prior art documents relating to such technology include the following.

Japanese Patent No. 2737238

  However, in the above-described conventional information retrieval system, a user who has access right can obtain information he wants to know, but a user who does not have access right stores information he wants to know in the group. It is not possible to obtain even information on whether or not the data is used, and the knowledge data cannot be sufficiently utilized.

  For example, when a new theme is set up as a research theme in a company, etc., even if information on similar themes has been accumulated in other departments in the company before, the right to access knowledge data in other departments Otherwise, even search of information will be rejected, so it will not be possible to obtain information on whether or not information on new themes has been accumulated in the company, and funding for research and development etc. and duplicate investment of human resources will be done, etc. This will cause harmful effects.

  The present invention has been made in view of the above problems, and an object of the present invention is to provide an information search system capable of effectively using stored data while maintaining confidentiality of data stored in a database. And

In order to solve the above-mentioned problem, the invention of claim 1 is a database system having a database for storing structured data in which user information is defined by tag information, the user information included in the structured data being And setting means for setting user access rights to the structured data, extracting means for extracting a keyword from the structured data, a keyword extracted from the structured data by the extracting means, and the setting means With respect to a specific keyword by analyzing the keyword-related data, a construction unit that builds keyword-related data that associates the structured data with the user whose access right is set by of the user, access rights for each user settings has access Characterized in that it comprises generation means for generating a Know-Who data by rank, and storage means for storing the Know-Who data in accordance with the number of structured data including the particular keyword are .

  The invention according to claim 2 is the database system according to claim 1, wherein the structured data includes mail data in XML format.

  Further, the invention of claim 3 is the database system according to claim 1 or claim 2, comprising: a reception unit that receives a query from a user; a recognition unit that recognizes a keyword from the query; and the recognition unit. Detecting Know-Who data corresponding to the recognized keyword from the storage means, detecting means for detecting structured data corresponding to the keyword from the database, Know-Who data detected by the detection means, Output means for outputting structured data.

  Further, the invention of claim 4 is the database system according to claim 3, wherein the user who has input the query to the structured data detected by the detecting means has an access right. Even if not, the Know-Who data detected by the detecting means is output.

Further, the invention of claim 5 is a data generation method in a database system for storing structured data in which user information is defined by tag information, and the structured data is generated according to the user information included in the structured data. A setting step for setting user access rights to data; an extraction step for extracting keywords from the structured data; a keyword extracted from the structured data in the extraction step; and the structured data in the setting step A construction step of constructing keyword-related data in which the access right is set for the user and the structured data, and analyzing the keyword-related data, thereby allowing a user who has the access right to a specific keyword , access rights are set with respect to each user Characterized in that it comprises a generation step of generating a Know-Who data by ranking according to the number of structured data including the specific keyword has.

  As described above, according to any of the first to fifth aspects of the invention, it is possible to effectively use the stored data while maintaining the confidentiality of the data stored in the database. For example, the user can grasp the authority for the information corresponding to the input keyword.

  According to the third aspect of the present invention, the authority for the information corresponding to the input keyword can be grasped while maintaining confidentiality, and the accumulated data can be effectively used. Furthermore, according to the invention described in claim 4, even if the user who entered the query does not have access to the detected structured data, it corresponds to the entered keyword. The authority to information can be grasped, and the accumulated data can be used effectively.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

<First Embodiment>
<Outline of information retrieval system>
FIG. 1 is a diagram showing an overview of an information search system 1 according to the first embodiment of the present invention.

  In the information search system 1, a mail server 11, a database server (hereinafter “DB server”) 12, and a firewall dedicated machine (hereinafter “FW dedicated machine”) 15 can communicate with each other via a network line 20. The in-house LAN 50 is formed by being connected. A Web server (World Wide Web Server) 13 is communicably connected to the network line 20 via the FW dedicated device 15. The in-house LAN 50 is communicably connected to the Internet line 70 via the router 60, and the Web server 13 is also communicably connected to the Internet line 70 via the router 60. Further, a plurality of terminal devices such as a PDA 81, a mobile phone 82, and a personal computer (hereinafter “PC”) 83 are communicably connected to the Internet line 70.

  The mail server 11 is a computer that performs transmission / reception processing of electronic mail between a terminal device outside the company via the Internet line 70 and a terminal device (not shown) belonging to the in-house LAN 50 and between terminal devices belonging to the in-house LAN 50. The e-mail data sent and received (hereinafter referred to as “mail data”) is stored.

  Further, the DB server 12 reads the mail data stored in the mail server 11 at a predetermined timing (for example, every day at midnight) for a predetermined period (here, one day), and stores data in XML format (hereinafter referred to as “XML format data”). This is a computer that constructs a database (hereinafter referred to as “XML mail DB”) by converting it into “XML mail data”) and registering (storing) it in a built-in hard disk, for example.

  Furthermore, the Web server 13 is a computer that provides content to be browsed by a Web browser, and resources provided by the Web server 13 for access from the terminal devices 81 to 83 (for example, an information search function described later). It has a function for determining availability (authentication function) and a function for providing a search result in response to an information search request from the terminal devices 81 to 83 (information search function).

  Each of these servers 11 to 13 realizes various functions by executing a program stored in a built-in storage unit (for example, a hard disk) by a built-in CPU. For example, the Web server 13 executes a program stored in a built-in storage unit by a CPU, and thereby cooperates with the DB server 12 and the like to provide a search result to the terminal devices 81 to 83. A function, that is, an information retrieval system is realized.

  Users of the PDA 81, the mobile phone 82, and the personal computer 83 can access the Web server 13 via the Internet line 70 and browse the content provided by the Web server 13 by using a Web browser in each terminal device. it can.

  The firewall dedicated device 15 has a function of monitoring a communication request from an external device such as each of the terminal devices 81 to 83 to the in-house LAN 50 via the Internet line 70 and passing only necessary communication. Block unauthorized data intrusion and unauthorized access.

  The router 60 is a device that relays between networks and controls a data relay route based on an IP address or the like, as in a general case.

<Information search function>
FIG. 2 is a diagram showing an overview of the information search function according to the first embodiment. Hereinafter, the information search function will be described with reference to FIG.

<Register email data>
For example, if mail data 101 as shown in FIG. 2 is stored in the mail server 11, the DB server 12 reads the mail data 101, converts it into XML format data (XML mail data), and registers (stores) ) At this time, the DB server 12 tags the mail data as shown in FIG. 3 by using the information of the header part H, the part of the body B is tagged as contents, and the start tag and the end tag are used. By enclosing, it can be converted into the XML format as shown in FIG.

  Here, as shown in FIG. 5, each XML mail data is stored in the DB server 12 in a hierarchical data structure in which elements are in a tree shape. That is, the DB server 12 constructs a database (XML mail DB) that stores a plurality of XML mail data based on a plurality of mail data stored in the mail server 11.

  In FIG. 5, triangle marks and lines indicate the hierarchical structure of the tags, and square marks indicate the content portion surrounded by the start tag and the end tag. Specifically, if the parent-child relationship of the tag is expressed as subordinate to the parent, the header tag and the contents tag are subordinate to the mail tag, and the received tag and message-id tag are further subordinate to the header tag. , From tag, to tag, subject tag,... Are subordinate to each other, and a tag original surrounding the mail body is subordinate to the contents tag. And it stores in the DB server 12 as a structure where the contents of the tag depend on each tag. Note that the description such as (10, 1000) shown in FIG. 5 and subsequent figures indicates the position (pos) where the tag and the contents surrounded by the tag are stored in the DB server 12.

  Here, the tables shown in FIGS. 6A to 6C show the relationship between the path name (Pathname) and the path ID (PathID) assigned to each tag, and the document ID (DocID) assigned to the path ID. And the relationship between the path ID (PathID) and the storage position (Pos), and the relationship between the document ID (DocID), the path ID (PathID), the content (Value) enclosed by the tag, and the storage position (Pos), respectively. The DB server 12 manages the storage of XML data using tables as shown in FIGS. 6 (A) to 6 (C).

<Setting of access authority for XML mail data>
When the DB server 12 registers each XML mail data, the DB server 12 responds to the user corresponding to the mail address surrounded by the From tag, To tag, Cc tag, and Bcc tag corresponding to the information of the header part of the XML mail data. Then, an access right to the XML mail data is given. That is, the DB server 12 generates and sets information (access authority table to be described later) for specifying the user's access authority to a plurality of XML mail data based on the sender and receiver information included in each mail data. To do. Therefore, it is possible to easily set the access authority without performing a complicated operation such as the administrator of the DB server 12 manually setting the access authority.

  Hereinafter, a method for automatically setting access authority for XML mail data will be described in detail.

  FIG. 7 is a diagram for explaining a method for setting an access right to XML mail data.

  First, the administrator of the DB server 12 provides a user code (User Code), a user ID (User ID), a mail address (Mail address), and an authentication password (Password) as shown in FIG. The associated table (hereinafter referred to as “authentication table”) is stored in a hard disk or the like built in the DB server 12 in advance. Note that the information described in the authentication table shown in FIG. 7A is arbitrarily assigned and determined for each employee.

  Then, when registering the XML mail data, the DB server 12 extracts the mail address surrounded by the From tag, To tag, Cc tag, and Bcc tag, and refers to the authentication table shown in FIG. Thus, each XML mail data (in this case, a data code (Data code) attached to each XML mail data) and a user code (User code) corresponding to the mail address described in the header part of each XML mail data. And a table as shown in FIG. Further, as shown in FIG. 7C, the DB server 12 also creates and stores a table in which the data code (Data code) of each XML mail data is associated with the storage location (Pos).

  Further, the DB server 12 is based on the table shown in FIG. 7B, as shown in FIG. 7D, a table associating XML mail data with users who have access rights to the XML mail data. (Hereinafter referred to as “access authority table”). Here, as shown in FIG. 7D, an access authority table in which a data code attached to each XML mail data is associated with a user code is created.

  Specifically, in the access authority table shown in FIG. 7D, two users with user codes 1001 and 1209 have access rights to XML mail data with a data code of 1000000000, and the data code is Three users with user code 1193,2480,1001 have access rights for XML mail data of 1000003928, and user code is 2904,3098,1193 for XML mail data with Data code of 1111111111 It shows that three users have access rights.

  In the information search system 1, the Web server 13 manages access to XML mail data from an external terminal device based on the access authority table created in this way. This access authority table is stored in a hard disk or the like built in the DB server 12. That is, the DB server 12 stores an access authority table that is information (access authority information) that defines user access authority for a plurality of XML mail data.

<Search for XML mail data>
As described above, the users of the terminal devices 81 to 83 can browse the content provided by the Web server 13 or use resources by accessing the Web server 13 using a Web browser. However, browsing all contents provided by the Web server 13 or using resources from all terminal devices outside the company is not preferable from the viewpoint of maintaining confidential information. Therefore, in the information search system 1, at least a specific resource (here, the XML mail data search processing function) is permitted to use the resource only when the authentication function authenticates that the user is usable. To do.

  For example, when an attempt is made to access a web page provided by the web server 13 from the terminal device 81 using a web browser, an authentication screen is displayed on the display screen of the terminal device 81 by the authentication function of the web server 13. This authentication screen is configured to input a user ID and password and click an execution button. The Web server 13 stores in advance a table similar to the authentication table shown in FIG. 7A on a built-in hard disk or the like, and compares the user ID and password entered on the authentication screen with the authentication table. Thus, it is authenticated / determined whether or not the terminal device that is going to access the Web page provided by the Web server 13 from outside is used by the employee. If it is determined that the employee is accessing, the resource provided by the Web server 13 (in this case, the information search function) is available, and the terminal device 81 can search for information (search). Screen) is displayed. This search screen is configured such that a search process is performed when a phrase such as a keyword is input and an execution button is clicked.

  Next, the operation flow of the information search process will be described.

  FIG. 8 is a flowchart showing an operation flow of the information search process, and this operation flow is realized by executing a program stored in the Web server 13.

  First, for example, when a user such as the terminal device 81 inputs a phrase (for example, “lens configuration of a digital camera”) as a search condition on a search screen displayed using a Web browser and clicks an execution button, A query indicating the search condition is transmitted from the terminal device 81 or the like to the Web server 13. Then, when the Web server 13 receives the search condition, the Web server 13 starts the operation flow of the information search process of FIG. 8 and proceeds to step S1. That is, when the Web server 13 receives a search request including a search condition from the user, the operation flow of the information search process is started.

  In step S1, a keyword is recognized from the query, and the process proceeds to step S2.

  In step S2, information in a category to be searched (here, an XML mail DB stored in the DB server 12) is searched to detect XML mail data including the keyword recognized in step S1, and step S3. Proceed to Here, XML mail data including the keyword recognized in step S1 is detected for the entire text of all XML mail data stored in the XML mail DB in the DB server 12. That is, in response to a search request from the user, XML mail data (also referred to as “corresponding data”) corresponding to the search condition is detected from the XML mail DB. For example, XML mail data 101 including the phrase “lens configuration of digital camera” in Subject is detected.

  In step S3, the access authority with respect to the XML mail data detected in step S2 (hereinafter, “detected XML mail data”) is referred to, and the process proceeds to step S4. Here, an access authority table as access authority information as shown in FIG.

  In step S4, based on the reference result in step S3, it is determined whether or not the user who transmitted the query has an access right to the detected XML mail data detected in step S2. Here, if the user who sent the query has an access right to the detected XML mail data, the process proceeds to step S5. If the user does not have an access right, the process proceeds to step S6.

  For example, assuming that the XML mail data 101 is detected in step S2, as shown in FIG. 2, when the user who has transmitted the query related to “the lens configuration of the digital camera” is Mr. Yamada, FIG. As shown in D), since the XML mail data 101 has an access right, the process proceeds to step S5. On the other hand, if the user who sent the query related to “the lens configuration of the digital camera” is Mr. nakata, as shown in FIG. 7D, he / she has access rights to the XML mail data 101. Therefore, the process proceeds to step S6.

  In step S5, data relating to the list of detected XML mail data as shown in FIG. Here, a screen based on the search result (search result screen) is displayed on the terminal device 81 or the like that has received the search result. FIG. 9 shows a search result screen. Here, since the user has an access right to the detected XML mail data, the ID (file) of the file storing the detected XML mail data is displayed on the search result screen. ID) 1R is displayed in a color (for example, blue) different from the surrounding character color, and the file ID1R and the corresponding XML mail data (stored in the DB server 12) are linked. That is, when a user such as the terminal device 81 puts the mouse pointer AR on the file ID 1R and presses the execution button on the search result screen, the Web server 13 reads the corresponding detected XML mail data from the DB server 12, Output to the terminal device 81 or the like. As a result, the contents of the XML mail data can be displayed on the screen of the terminal device 81 or the like.

  On the other hand, in step S6, a list of detected XML mail data as shown in FIG. 10 and data related to user information (user information) having an access right to the detected XML mail data are directed to the terminal device 81 as a search result. Output, and the operation flow of the information search process is terminated. Here, a search result screen based on the search result is displayed on the terminal device 81 or the like that has received the search result. FIG. 10 shows a search result screen. Here, since the user does not have access rights to the detected XML mail data, the ID of the file storing the detected XML mail data displayed on the search result screen. (File ID) 2R is not linked to the corresponding XML mail data. That is, in step S4, if it is determined that the user does not have access to the detected XML mail data, information indicating the presence of the detected XML mail data in the XML mail DB (here, the search result screen displays The displayed file ID 2R information) is output to the terminal device 81 of the user who has transmitted the search request.

  As described above, when the user does not have access right to the detected XML mail data, the file ID 2R of the detected XML mail data displayed on the search result screen is not linked to the corresponding XML mail data. . However, instead, a mail address list MA is displayed on the search result screen as information on users who have access rights to the detected XML mail data. That is, if it is determined in step S4 that the user does not have access rights to the detected XML mail data, the person who has a predetermined right (for example, access right) to the detected XML mail data. As personal information, information of a user who has an access right to the detected XML mail data (here, mail address information) is output to the terminal device 81 of the user who issued the search request.

  As a result, a user such as the terminal device 81 can know that information related to the input word (here, detected XML mail data) is stored in the DB server 12, and information related to the detected XML mail data. You can know who the user has.

  Further, on the search result screen shown in FIG. 10, the mail address list MA is displayed in a color (for example, blue) different from the character color around the search result screen. When a specific mail address is selected by moving the mouse pointer AR to each mail address on the search result screen and the execution button is pressed, a form of a transmission mail message with the selected mail address as a destination is displayed. Therefore, a user such as the terminal device 81 can easily send an e-mail to a user who has access rights to the detected XML mail data. As a result, the user such as the terminal device 81 can easily request the disclosure of the detected XML mail data and the teaching of the information related to the detected XML mail data to the user who has the information related to the detected XML mail data. . As a result, the stored data can be used more effectively while maintaining the confidentiality of the stored data in the database.

  As described above, in the information search system 1 according to the first embodiment, when the Web server 13 searches for XML mail data in the DB server 12 based on a search condition that includes a specific keyword, the search condition is satisfied. In response to a search request from a user who has access rights to XML mail data, a list of XML mail data as search results is disclosed, and disclosure of the XML mail data shown in the list is allowed.

  On the other hand, for a search request from a user who does not have access to the XML mail data satisfying the search condition, a list of XML mail data satisfying the search condition is disclosed as a search result. Disclosure of the content itself is prohibited. That is, in response to a search request from the user, data corresponding to the search condition is detected from the database, and even if the user does not have access to the data, information on the existence of the data However, in response to a search request from a user who does not have access to the data, one of the search result outputs, for example, information that links the file ID and XML mail data, etc. The output of some information is restricted. As a result, it is possible to effectively use the stored data while maintaining the confidentiality of the data stored in the database.

  In addition, in response to a search request from a user who does not have access rights to XML mail data satisfying the search condition, the disclosure itself of the XML mail data is prohibited, but the XML mail data satisfying the search condition is accessed. E-mail address etc. are disclosed as personal information regarding authorized users. That is, the content output as the search result is changed according to the presence or absence of the access right. As a result, it is possible to effectively use the stored data while maintaining the confidentiality of the data stored in the database.

  In other words, regardless of whether or not there is an access right, an information search process for data stored in the DB server 12 (here, XML mail data) is allowed. As a result, it is easy to know whether or not knowledge data is accumulated in a specific group in the company, etc., preventing human and financial waste such as duplicate research and duplicate investment. can do.

Second Embodiment
In the information search system 1 according to the first embodiment, the mail data stored in the mail server 11 is converted into XML mail data in the XML format and registered in the DB server 12 as a search target. In the information retrieval system 1A according to the second embodiment, instead of the mail server 11, a file server 11A is communicably connected to the network line 20 to form an in-house LAN 50A. The configuration of the information search system 1A according to the second embodiment is the same as that of the information search system according to the first embodiment except that the file server 11A exists instead of the mail server 11 to form the in-house LAN 50. Since the configuration is the same as that of the system 1, the same reference numerals are given to the same parts in FIG. In the second embodiment, as in the first embodiment, the Web server 13 executes the program stored in the built-in storage unit by the CPU, thereby cooperating with the DB server 12 and the like. An information search function for providing a search result to the terminal devices 81 to 83, that is, an information search system is realized.

<Information search function>
FIG. 12 is a diagram illustrating an outline of an information search function according to the second embodiment. Hereinafter, the information search function according to the second embodiment will be described with reference to FIG.

<Register folders and files>
For example, as shown in FIG. 12, a folder storing a plurality of data files related to “pulverized toner” (hereinafter “folder-pulverized toner”) and a folder storing a plurality of data files related to “polymerized toner” ( Hereinafter, it is assumed that “folder-polymerized toner”) is stored in the file server 11A. Here, the folder name of the folder-pulverized toner is “pulverized toner”, the folder name of the folder-polymerized toner is “polymerized toner”, and the format of the data file belonging to each folder is, for example, txt , Pdf, doc, xls format, etc. are possible.

  Here, the DB server 12 reads out the data file stored in the file server 11A at a predetermined timing (for example, every day at midnight), that is, at a predetermined period (here, every day). Convert to XML format using conversion software according to the format. At this time, for example, regarding the data content itself in each data file, elements that can be tagged are tagged, but in principle, the attribute value of the file and the data content itself are tagged. Data converted to the XML format in this way (hereinafter “XML file data”) is stored in the DB server 12.

  FIG. 13 is a diagram illustrating a storage state of XML file data stored in the XML format. In FIG. 13, it is assumed that the data content itself in the data file is targeted for data that cannot be tagged.

  The XML file data is stored in the DB server 12 in a hierarchical data structure with elements in a tree shape. In FIG. 13, as in FIG. 5, triangle marks and lines indicate the hierarchical structure of tags, and square marks indicate the contents surrounded by start tags and end tags. Specifically, if the parent-child relationship of the tag is expressed as that the child is subordinate to the parent, for example, the property tag and the contents tag that enclose information on the attribute value of the file are subordinate to the Datafile1 tag. In addition, for the property tag, the author tag that encloses the information of the file creator, the creation_date tag that encloses the information of the creation date, the saved_date tag that encloses the information of the save date, the folder tag that encloses the information of the folder name, While the size tag surrounding the information is subordinate, the contents tag is subordinate to the original tag surrounding the content of the data file itself. In this way, the content corresponding to each tag is stored in the DB server 12 as a structure depending on each tag.

  Further, the DB server 12 associates a plurality of XML file data using XML, RDF, or the like according to the attribute of the XML file data that is tagged and stored as described above. For example, when each XML file data is registered and stored in the DB server 12, a folder name (for example, “pulverized toner”) surrounded by a folder tag of each XML file data is detected as a theme. If the detected theme is not stored in the theme listed in the file list stored in the DB server 12, the theme is added to the file list. Note that if the detected theme is already stored in the file list, the theme is not added to the file list. Furthermore, in the file list, each XML file data is associated with a theme that coincides with the content enclosed by the folder tag of each XML file data to construct data (hereinafter “file list data”).

  Specifically, if the parent-child relationship of the tag is expressed as that the child is subordinate to the parent, as shown in FIG. 14, the tag surrounding the file list includes a plurality of themes (for example, “pulverized toner” and “ A tag that encloses a data file name corresponding to XML file data that encloses the theme in a folder tag is subordinate to a tag that encloses each theme. For example, the XML file data of Datafiles 1 to 4 are subordinate to the theme “pulverized toner”, and the XML file data of Datafiles 1 to 4 are subordinate to the theme “polymerized toner”.

<Setting of access authority for XML file data>
Assuming that the access authority is set for each folder in the file server 11A, the DB server 12 uses the XML file based on the access authority set in the file server 11A when registering each XML file data. Automatically set access rights to data.

  Here, an automatic setting method of access authority for XML file data will be described.

  15 and 16 are diagrams for explaining an access authority setting method according to the second embodiment. In the file server 11A, as shown in FIG. 15, information (User Code, User ID) of a user having access authority, a password and an e-mail address corresponding to the user are defined for each folder (hereinafter referred to as “file server 11A”). , “Folder access authority table”) is stored in advance. For example, in the folder access authority table shown in FIG. 15, two users (Mr. Yamada and Mr. Suzuki) whose user codes are 1001 and 1209 for the folder-pulverized toner and 2480 for the folder-polymerized toner are used. And 2904 (Mr. Tanaka and Mr. Nakata) have access rights. The file server 11A manages access to each folder by storing the folder access authority table shown in FIG. 15 in a built-in hard disk or the like.

  Then, when registering the XML file data and creating the file list data, the DB server 12 reads the folder access authority table stored in the file server 11A, and uses the file name as the theme name as shown in FIG. A table (hereinafter referred to as “theme access authority table”) defining the access authority for the XML file data for each theme is created. Then, the DB server 12 stores the file list data as shown in FIG. 14 in a hard disk or the like incorporating a theme access authority table as shown in FIG.

  Thus, based on the theme access authority table stored in the DB server 12, access to the XML file data from the terminal devices 81 to 83 via the Web server 13 is managed.

<Search for XML file data>
Similarly to the information search system 1 according to the first embodiment, the information search system 1 </ b> A uses a Web browser from the terminal devices 81 to 83 to access a Web page provided by the Web server 13. If it is determined by the authentication function 13 that the employee is accessing, the resource (in this case, the information search function) provided by the Web server 13 becomes usable, and the search screen is displayed on the terminal devices 81-83. Is displayed.

  FIG. 17 is a flowchart showing an operation flow of information search processing according to the second embodiment. This operation flow is realized by executing a program stored in the Web server 13.

  First, when a user such as the terminal device 81 inputs a phrase (for example, “pulverized toner” or “polymerized toner”) as a search condition on the search screen provided by the Web server 13 and clicks the execution button, the search condition is changed. When the query shown is transmitted from the terminal devices 81 to 83 to the Web server 13 and the Web server 13 accepts the query, the operation flow of the information search process in FIG. 17 is started, and the process proceeds to Step S11.

  In step S11, a keyword is recognized from the query, and the process proceeds to step S12.

  In step S12, a search target category (here, XML file data stored in the DB server 12) is searched to detect XML file data including the keyword recognized in step S11, and the process proceeds to step S13. . Here, the search is performed on the entire text of the XML file data.

  In step S13, the access authority with respect to the XML file data detected in step S12 (hereinafter referred to as “detected XML file data”) is referred to, and the process proceeds to step S14. Here, the access authority for the detected XML file data can be recognized by comparing the theme access authority table stored in the DB server 12 with the file list data.

  In step S14, based on the reference result in step S13, it is determined whether or not the user who has transmitted the query has an access right to the detected XML file data. Here, if the user who sent the query has an access right to the detected XML file data, the process proceeds to step S15, and if the user does not have an access right, the process proceeds to step S16.

  For example, as shown in FIG. 12, when the user who has transmitted the query related to “pulverized toner” is Mr. Yamada, as shown in FIG. Since it has access right, the process proceeds to step S15. On the other hand, if the user who sent the query related to “polymerized toner” is Mr. Yamada, as shown in FIG. 16, he / she has access rights to the XML file data on the theme of “polymerized toner”. If not, the process proceeds to step S16.

  In step S15, data relating to a list of detected XML file data (here, a list of IDs (file IDs) of files storing the detected XML file data) as shown in FIG. 18 is directed to the terminal device 81 as a search result. To complete the operation flow of the information search process. Here, a search result screen based on the search result is displayed on the terminal device 81 or the like that has received the search result. FIG. 18 shows a search result screen. Here, since the user has an access right to the detected XML file data, the file ID 3R of the detected XML file data is the surrounding character color on the search result screen. Is displayed in a different color (for example, blue), and the file ID 3R and the corresponding XML file data (stored in the DB server 12) are linked.

  That is, when a user such as the terminal device 81 puts the mouse pointer AR on the file ID 3R and presses the execute button on the search result screen, the Web server 13 reads the corresponding detected XML file data from the DB server 12, Output to the terminal device 81 or the like. As a result, the contents of the detected XML file data are displayed on the screen of the terminal device 81 or the like.

  On the other hand, in step S16, a list of detected XML file data (here, a list of file IDs) as shown in FIG. 19 and data relating to information of a user who has access rights to the detected XML file data are used as search results for the terminal device. It outputs to 81 etc. and complete | finishes the operation | movement flow of an information search process. Here, a search result screen based on the search result is displayed on the terminal device 81 or the like that has received the search result. FIG. 19 shows a search result screen. Here, since the user does not have access rights to the detected XML file data, the file ID 4R is linked to the corresponding detected XML file data on the search result screen. It is not in a state. However, instead, a list MA2 of mail addresses is displayed on the search result screen as information (user information) of users who have access rights to the detected XML file data. As a result, the user such as the terminal device 81 can know that information (here, the detected XML file data) corresponding to the phrase including the input keyword is stored in the DB server 12 and the detected XML. It is possible to know who is a user who has information about file data.

  Also, on the search result screen shown in FIG. 19, the mail address list MA2 is displayed in a color (for example, blue) different from the character color around the search result screen. When a specific mail address is selected by moving the mouse pointer AR to each mail address on the search result screen and the execution button is pressed, a form of a transmission mail message with the selected mail address as a destination is displayed. Therefore, a user such as the terminal device 81 can easily transmit an e-mail to a user who has an access right to the detected XML file data. As a result, the user such as the terminal device 81 can easily request the disclosure of the detected XML file data and the teaching of the information related to the detected XML file data to the user who has the information related to the detected XML file data. .

  As described above, in the information search system 1A according to the second embodiment, when the Web server 13 searches for XML file data in the DB server 12 based on a search condition such as including a phrase such as a specific keyword, the search is performed. In response to a search request from a user who has access to the detected XML file data that satisfies the conditions, a list of detected XML file data as a search result is disclosed, and disclosure of the XML file data indicated in the list is also permitted. To do.

  On the other hand, for a search request from a user who does not have access to the detected XML file data satisfying the search condition, a list of detected XML file data satisfying the search condition is disclosed as a search result. Disclosure of the contents of XML file data is prohibited. However, instead, user information such as a mail address of a user who has access rights to the detected XML file data that satisfies the search condition is disclosed. That is, the content output as the search result is changed according to the presence or absence of the access right. In other words, regardless of whether or not there is an access right, search processing for data stored in the DB server 12 (here, XML file data) is allowed.

  Therefore, an information search system is provided that can effectively use the stored file data and XML file data while maintaining the confidentiality of the file data and XML file data stored in the file server 11A and the DB server 12. be able to. As a result, it is easy to know whether or not knowledge data is accumulated in a specific group in the company, etc., preventing human and financial waste such as duplicate research and duplicate investment. can do.

<Third Embodiment>
In the information search system 1 according to the first embodiment, for a search request from a user who does not have access rights to XML mail data satisfying the search condition, a list of XML mail data satisfying the search condition is displayed as a search result. Although disclosed, disclosure of the XML mail data is prohibited. However, user information such as a mail address of a user who has an access right to XML mail data satisfying the search condition is disclosed instead. On the other hand, in the information search system 1B according to the third embodiment, user information such as authority information related to keywords related to search conditions is further disclosed. The configuration of the information search system 1B according to the third embodiment is the same as the configuration of the information search system 1 according to the first embodiment shown in FIG. 1 except that the authority information is disclosed to the user. Therefore, the same reference numerals are assigned to the respective parts and the description thereof is omitted. In the following, different points such as disclosing authority information to the user will be mainly described.

  Also in the third embodiment, as in the first and second embodiments, the Web server 13 cooperates with the DB server 12 and the like by causing the CPU to execute a program stored in the built-in storage unit. Meanwhile, an information search function that provides search results to the terminal devices 81 to 83, that is, an information search system 1B is realized.

<Information search function>
FIG. 20 is a diagram illustrating an overview of an information search function according to the third embodiment. Hereinafter, the information search function will be described with reference to FIG.

<Registering XML mail data>
As shown in FIG. 20, if the mail data 301 to 303 are stored in the mail server 11, the DB server 12 reads the mail data 301 to 303 by the same method as in the first embodiment, and the XML mail data. 301 'to 303' are converted and registered. Note that the storage and management method of XML mail data is the same as that in the first embodiment described above, and a description thereof will be omitted here.

<Setting of access authority for XML mail data>
Regarding the setting of the access authority for the XML mail data, when the DB server 12 registers the XML mail data by the same method as in the first embodiment, the From tag corresponding to the header part information of the XML mail data, To The access authority to the XML mail data is automatically set for the user corresponding to the mail address enclosed by the tag, the Cc tag, and the Bcc tag.

  Specifically, for example, for XML mail data 301 ′ converted from mail data 301, access authority is set for Mr. Yamada and Mr. suzuki, and for XML mail data 302 ′ converted from mail data 302, Access authority is set for Mr. Yamada and Mr. tanaka, and for XML mail data 303 ′ converted from the mail data 303, access authority is set for Mr. Yamada and Mr. saito. These access authorities are stored in the form of an access authority table as shown in FIG. 7D, as in the first embodiment.

  Further, in the information search system 1B according to the third embodiment, when the DB server 12 registers XML mail data, a user who has an access right for a specific keyword is set as the number of access rights for each user. Data generated by ranking according to this (hereinafter “Know-Who data”) is accumulated. For example, as shown in FIG. 20, Know-Who data 309 for the keyword “camera lens” is stored. Here, a person who has an access right for a specific keyword, in particular, a person who has an access right for a lot of XML mail data can be regarded as an authority for the specific keyword.

<Generation of Know-Who data>
Hereinafter, a method of generating Know-Who data will be described.

  When registering XML mail data in the DB server 12, first, keywords are detected for the entire text of the XML mail data. Note that keyword detection can be realized by extracting words by a technique such as morphological analysis.

  Next, if the detected keyword (hereinafter referred to as “detected keyword”) is not stored in a list of keywords stored in the DB server 12 (hereinafter referred to as “keyword list”), the detected keyword is determined as a keyword. Add to list. If the detected keyword is already stored in the keyword list, the detected keyword is not added to the keyword list.

  Then, in the keyword list, for each XML mail data, the detected keyword is associated with a user having an access right (here, a user ID), and further, data (hereinafter, “ Keyword related data "). For the keyword-related data, each element can be stored in a tree-like hierarchical data structure using, for example, XML or RDF.

  Specifically, if the parent-child relationship of the tag is expressed as that the child is subordinate to the parent, as shown in FIG. 21, a tag surrounding the keyword list includes a plurality of keywords (for example, “camera lens”). A tag that encloses a plurality of keywords is subordinate to a tag that encloses a user ID of a user who has access rights to the XML mail data including the keywords, and further encloses a user ID. The tag is associated with the data ID of XML mail data having access rights for the keyword to which the user is dependent.

  By analyzing the keyword-related data constructed in this way, Know-Who data indicating authority information for a specific keyword is generated. Specifically, for example, based on the keyword-related data shown in FIG. 21, for the keyword “camera lens”, four authorities (yamada, suzuki, tanaka, saito) subordinate to the keyword “camera lens” are authorized. Furthermore, Know-Who data 309 (FIG. 20) can be generated by ranking in descending order of the number of XML mail data subordinate to each authority.

  The DB server 12 constructs and stores one database (hereinafter, “Know-Who database”) by generating and storing Know-Who data for a plurality of keywords.

<Search for XML mail data>
As for the search of the XML mail data, as in the information search system 1 according to the first embodiment described above, the XML mail in the DB server 12 is based on the search condition that the Web server 13 includes a phrase such as a specific keyword. When searching for data, in response to a search request from a user who has access rights to XML mail data that satisfies the search condition, a list of XML mail data as a search result is disclosed, and the XML mail shown in the list is disclosed. Disclosure of data is allowed.

  Furthermore, here, when searching XML mail data in the DB server 12 based on a search condition that includes a phrase such as a specific keyword, whether or not the XML mail data that has transmitted the search request has an access right. Regardless, as part of the search result, Know-Who data relating to a specific keyword is output to the user.

  FIG. 22 is a flowchart showing an operation flow of information search processing according to the third embodiment. This operation flow is realized by executing a program stored in the Web server 13. Note that the operation flow shown in FIG. 22 has the same parts as the operation flow shown in FIG. 8, and the same step numbers are assigned to the parts and the description thereof is omitted, and the parts specific to the third embodiment are omitted. This will be described below.

  In step S1, the keyword is recognized from the query and the process proceeds to step S2, and the process also proceeds to step S21. That is, here, the process of step S2 to step S6 and the process of step S21 to step S22 are performed in parallel.

  In step S21, information in the Know-Who database stored in the DB server 12 is searched, Know-Who data corresponding to the keyword recognized in step S1 is detected, and the process proceeds to step S22.

  In step S22, data relating to Know-Who data as shown in FIG. 23 is output to the terminal devices 81 to 83 as search results, and the operation flow of the information search process is terminated. Here, a search result screen based on the search result is displayed on the terminal device 81 or the like that has received the search result. The search result screen is displayed in a form including a ranking table indicating authority information related to a specific keyword (for example, “camera lens”) based on Know-Who data 309 as shown in FIG. 23, for example. Is done. Therefore, the data output in step S22 and the data output in step S5 or S6 may be output to the user in a combined form.

  In this ranking table, the mail address of each authority is described, and this mail address is displayed in a color (for example, blue) different from the surrounding character color. That is, in step S4, whether it is determined that the user does not have the access right for the detected XML mail data or if it is determined that the user has the access right, As personal information about a person who has a predetermined right for the detected XML mail data, information indicating the authority regarding the search condition (for example, keyword) is output to the terminal device 81 of the user who issued the search request. . Here, since the detected XML mail data is detected based on the search condition, a search request is made for information indicating the authority for the detected XML mail data as person information about a person who has a predetermined right for the detected XML mail data. It can also be seen that it is output toward the terminal device 81 of the user who issued

  When a specific mail address is selected by moving the mouse pointer AR to each mail address on the search result screen and the execution button is pressed, a form of a transmission mail message with the selected mail address as a destination is displayed.

  Therefore, the user of the terminal devices 81 to 83 can grasp the authority for the information corresponding to the input keyword, and can easily transmit an e-mail to the authority. As a result, the user of the terminal devices 81 to 83 can easily contact the authority for the information he / she wants to know, and can easily ask for various information related to the keyword.

  As described above, in the information search system 1B according to the third embodiment, when the Web server 13 searches for XML mail data in the DB server 12 based on a search condition such as including a phrase such as a specific keyword, the search is performed. Regardless of whether or not there is an access right to the XML mail data that satisfies the condition, the authority information related to the specific keyword is disclosed to the user who made the search request. In other words, in response to a search request from the user, data corresponding to the search condition is detected from the database, and even if the user does not have access to the data, the authority regarding the data is set. Inform.

  Therefore, for example, since it is possible for the user to listen to information related to the data, the validity of the stored data is maintained while maintaining the confidentiality of the data stored in the DB server 12 (here, XML mail data). An information search system that can be used can be provided. In other words, since it is easy to know whether knowledge data is accumulated within a specific group such as in-house, it prevents human and monetary waste such as duplicate research and duplicate investment. be able to.

<Others>
The embodiment of the present invention has been described above. However, the present invention is not limited to the above-described content, and it is needless to say that various modifications can be applied.

  For example, in the embodiment described above, when registering each XML mail data, the DB server 12 is surrounded by the From tag, To tag, Cc tag, and Bcc tag corresponding to the information of the header part of the XML mail data. The access right to the XML mail data is automatically set for the user corresponding to the e-mail address. However, the present invention is not limited to this. For example, the sender and the receiver included in each mail data Based on at least one of the information, information for specifying the user's access authority to a plurality of XML mail data may be generated and set. With such a configuration, the access authority can be easily set without performing a complicated operation such as an administrator of the DB server 12 manually setting the access authority.

  In the above-described embodiment, the Web server 13 is accessed from the outside such as the terminal devices 81 to 83 via the Internet line 70, and a search request is transmitted from the terminal devices 81 to 83 to the Web server 13. However, the present invention is not limited to this. For example, a server having a search function similar to the Web server 13 (hereinafter referred to as “search server”) and a terminal device are directly connected to the in-house LAN. The terminal device may be configured to access the search server via the in-house LAN and transmit a search request to the search server.

  In the third embodiment described above, when XML mail data is a search target, authority-related information is output to a user who has made a search request. However, the present invention is not limited to this. For example, As in the second embodiment, even when XML file data is a search target, information related to the authority is output to the user who has transmitted the search request in the same manner as in the third embodiment. Also good.

  In the embodiment described above, for users who do not have access rights to the detected XML mail data or the detected XML file data detected by the Web server 13, the detected XML mail data or the detected XML file data Information indicating presence / absence and personal information regarding detected XML mail data and detected XML file data have been disclosed. However, the present invention is not limited to this. For example, the access right to the detected XML mail data detected by the Web server 13 is given. For a user who does not have the data, only the data corresponding to the information in the header part of the mail data (partial data of the XML mail data) may be disclosed. That is, when it is determined in the operation flow of the information search process in the Web server 13 that the user does not have access right to the detected XML mail data, a part of the detected XML mail data is searched for. It is good also as a structure which outputs toward the terminal device 81-83 of the user who transmitted.

  In other words, the degree of disclosure of detected XML mail data for a user who does not have access rights to certain detected XML mail data by the Web server 13 is higher than the degree of disclosure of detected XML mail data for users who have access rights. You may make it control so that it may become small. In other words, depending on whether or not there is an access right to the detected XML mail data, the degree to which data in the database (for example, XML mail DB) stored in the DB server 12 can be browsed is controlled to be different. Also good.

  With such a configuration, it is possible to effectively use the stored data while maintaining the confidentiality of the data stored in the database.

  As information to be disclosed to users who do not have access rights, for example, various information related to XML mail data is prepared and disclosed, not the entire contents of XML mail data, such as abstracts for each XML mail data. Also good.

  In the above-described embodiment, the Web server 13 controls the output of information directed to the user according to the presence or absence of access rights to the detected XML mail data and the detected XML file data. However, the present invention is not limited to this. For example, depending on whether or not there is an access right to the database stored in the DB server 12, a resource that can obtain a search result that makes it possible to access each data in the database and the database as a result It is also possible to selectively use a resource that can obtain a search result that cannot be accessed for each piece of data.

  Specifically, based on the user ID and password input when the user is authenticated by the authentication function of the Web server 12, the access right to all or a specific part of the data stored in the DB server 12 Is determined by referring to an access authority table or the like stored in the DB server 12. Then, it may be configured such that a resource (information search function) capable of obtaining a search result that can access the data accessible by the user can be used.

  In other words, the following configuration may be used. Information that defines the usable range of the information search function of the Web server 13 for the user based on the use request of the information search function for the Web server 13 from the user (for example, the access authority table here) Etc. (use authority information)). Based on the reference result, the usable range of the information search function for the user is determined. Based on the determination result, the usable range of the information search function for the user is determined. The usable range referred to here is a search result (for example, the link linked to the detected mail data as the search result) that can finally access the data in the database stored in the DB server 12. A list of detected mail data), information indicating the presence of data in the database stored in the DB server 12, personal information (email address, etc.) on users who have access to the data, This refers to a range in which various functions for searching personal information (authority data) and the like related to search conditions can be used as appropriate.

  In other words, the Web server 13 limits a part of information to be searched based on information (usage authority information) that defines the usable range of the information search function of the Web server 13 for the user. Also good.

  Even with such a configuration, the same effects as those of the above-described embodiment can be obtained.

  In the above-described embodiment, the database stored in the DB server 12 is constructed by data in the XML format. However, the present invention is not limited to this. For example, even if the database is constructed by a relational database (RDB). good. Specifically, when the database is constructed by the RDB in the DB server 12 according to the first embodiment, for example, a record is given to each mail data, and each mail data related to each mail data described in “from”, “to”, etc. A database may be constructed by using a table structure in which information is field information.

It is a figure showing the outline of information retrieval system 1 concerning a 1st embodiment. It is a figure which shows the outline | summary of the information search function which concerns on 1st Embodiment. It is a figure which shows mail data. It is the figure which showed what converted the mail data into the XML format. It is a figure explaining the storage state of the mail data stored in the XML format. It is a figure explaining the storage state of the mail data stored in the XML format. It is a figure explaining the setting method of the access authority to XML mail data. It is a flowchart which shows the operation | movement flow of an information search process. It is a figure explaining the screen which displays a search result. It is a figure explaining the screen which displays a search result. It is a figure showing an outline of information retrieval system 1A concerning a 2nd embodiment. It is a figure which shows the outline | summary of the information search function which concerns on 2nd Embodiment. It is a figure explaining the storage state of the mail data stored in the XML format. It is a figure explaining the storage state of the mail data stored in the XML format. It is a figure explaining the setting method of access authority. It is a figure explaining the setting method of access authority. It is a flowchart which shows the operation | movement flow of an information search process. It is a figure explaining the screen which displays a search result. It is a figure explaining the screen which displays a search result. It is a figure which shows the outline | summary of the information search function which concerns on 3rd Embodiment. It is a figure shown about the storage state of the information in a keyword list. It is a flowchart which shows the operation | movement flow of an information search process. It is a figure explaining the screen which displays a search result.

Explanation of symbols

1, 1A, 1B Information retrieval system 11 Mail server 11A File server 12 Database server (DB server)
13 Web server 50 Internal LAN
70 Internet line 81-83 Terminal equipment

Claims (5)

A database system having a database for storing structured data in which user information is defined by tag information,
In accordance with user information included in the structured data, setting means for setting user access rights to the structured data;
Extraction means for extracting keywords from the structured data;
Construction of constructing the keywords extracted from the structured data by the extracting means, and user access rights set for the structured data by said setting means, the keyword-related data associated with a said structured data Means,
By analyzing the keyword-related data, with respect to a specific keyword, users who have access rights are ranked according to the number of structured data including the specific keyword for which access rights are set for each user . Generating means for generating Know-Who data by
Storage means for storing the Know-Who data;
A database system comprising: The database system according to claim 1, wherein
The structured data is
A database system including mail data in XML format. The database system according to claim 1 or 2, wherein
Accepting means to accept queries from users,
Recognition means for recognizing a keyword from the query;
Detecting means for detecting Know-Who data corresponding to the keyword recognized by the recognition means from the storage means, and detecting structured data corresponding to the keyword from the database;
Output means for outputting Know-Who data and structured data detected by the detection means;
A database system comprising: The database system according to claim 3, wherein
The output means is
Outputting the Know-Who data detected by the detecting means even when the user who has input the query for the structured data detected by the detecting means does not have the access right. A featured database system. A data generation method in a database system for storing structured data in which user information is defined by tag information,
Setting a user's access right to the structured data according to user information included in the structured data;
An extraction step of extracting keywords from the structured data;
Construction of constructing the keywords extracted from the structured data in the extraction step, and the user access right is set for the structured data in said setting step, the keyword-related data associated with a said structured data Steps,
By analyzing the keyword-related data, with respect to a specific keyword, users who have access rights are ranked according to the number of structured data including the specific keyword for which access rights are set for each user . A generation step for generating Know-Who data by
A data generation method comprising:

Images