JP2009059026A - File retrieval device and file retrieval program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a file retrieval device for retrieving a target file from among files to be used by a plurality of users. <P>SOLUTION: An attribute item and attribute value are set in a product configured of a file. A retrieval attribute item and retrieval attribute value as retrieval conditions are designated in a retrieval condition display region 110. When a retrieval button 150 is depressed, information input to a retrieval condition display region 110 is transmitted to a file retrieval server, and a file is retrieved. As a retrieval result, the state of the retrieval attribute item and retrieval attribute value is displayed in a virtual folder tree display region 120. The virtual folder of the retrieval attribute value of the first retrieval attribute item is displayed in a first layer, and the virtual folder of the retrieval attribute value of the second retrieval attribute item is displayed under each folder of the first layer in a second layer. A product belonging to a folder selected in the virtual folder tree display region 120 is displayed in a product folder tree display region 130. The name of the file configuring the product is displayed in the second layer. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a file search device and a file search program, and more particularly to a file search device and a file search program for searching for a file used by a user.

  2. Description of the Related Art Conventionally, the use of computers has become common, and a single file is used every day by a plurality of users. In such a case, in order to make it easy to use a file used by a plurality of users, a method of predetermining a rule as to where to save the file is generally used. For example, a user who uses a file stores the file in a file server that can be connected via a network. In addition, there are cases where detailed rules for where to store files are determined. For example, a folder (product number folder) is created with a product number, and a shared file related to a product with that product number is stored in the product number folder. Furthermore, a folder corresponding to the business content may be created and managed under the product number folder. In addition, the management method for setting a rule for storing the file is not only performed when a plurality of users use the file, but also when a single user manages the file.

Further, in the file management method of the invention described in Patent Document 1, additional information is associated with a file, and the file is displayed based on the additional information. Specifically, the files are displayed in a hierarchical structure for each item of additional information, and the type of additional information in the first layer is designated to facilitate the search for the file.
JP-A-2005-216129

  However, when deciding a rule for where to save a file, there is a problem that it is difficult to find a target file unless the user observes the rule when saving the file. Even if you save the file in the correct location, if you forget the rules for saving when using the file, or if you want to use it by a user who does not know the rules themselves, There is a problem that it is difficult to find a file.

  Further, when the file name is not accurately remembered, it is difficult to find the target file. Furthermore, even if it is known that a file described in a certain item exists, it is difficult to find a target file if it is unknown which file the file is. For example, when searching for a design drawing of a part A, consider a case in which files are managed in folders for each product. In this case, even if it is known that the part A has been used in the past, it is difficult to find out if the part A is used for which product.

  Further, in the file management method of the invention described in Patent Document 1, when hierarchical display is performed with additional information, only the type of additional information in the first hierarchy is specified. Therefore, it is easier to find the file to some extent, but it is only hierarchized with additional information, and folders are displayed for each value that the additional information takes, so it takes time to find the file you want from these There is a problem that it takes. In particular, it is difficult to search when there are a large number of values of additional information. For example, when the additional information “person in charge” is displayed as the first layer in the person-in-charge view, if there are a large number of persons in charge (for example, 50 people), it is troublesome to find the target person in charge.

  The present invention has been made to solve the above-described problems, and an object of the present invention is to provide a file search device and a file search program that can easily search for a target file from files used by a user.

  In order to solve the above problem, in the file search device of the invention according to claim 1, an attribute item and a value of the attribute item are associated with a product that is a data file or a group of one or more data files. An attribute information storage means for storing attribute information associated with the attribute value, the attribute item for searching the data file or the deliverable, and a search condition for acquiring a condition of the attribute value of the attribute item A condition attribute item that is the attribute item acquired by the search condition acquisition unit based on the attribute information stored in the attribute information storage unit, and an attribute value condition of the condition attribute item Extraction means for extracting the data file or the deliverable that matches the data file, and the data file or the deliverable extracted by the extraction means Distinguishably the attribute value matters attribute item, and, and a search result display means for identifiably displaying the data file or the product takes the same said attribute value.

  Further, in the file search device of the invention according to claim 2, in addition to the configuration of the invention of claim 1, the search condition acquisition means has the priority with the priority added to a plurality of the attribute items. The condition attribute item is acquired, and the search result display means sets the condition attribute item having the highest priority as a first hierarchy, lowers the priority, and sets the condition attribute item as a lower hierarchy, and the conditions of each hierarchy The attribute value of the attribute item is displayed in a tree structure with the names of the nodes in each hierarchy, and the data file or the deliverable that takes the attribute value that is the ancestor of the lowermost node is identified in the lowermost node The identification information to be displayed is displayed.

  Further, in the file search device of the invention according to claim 3, in addition to the configuration of the invention of claim 1 or 2, attribute template acquisition means for acquiring a group of one or a plurality of the attribute items as an attribute template; An attribute candidate value acquisition unit that acquires, for each attribute item, an attribute candidate value that is a candidate for the value of the attribute item belonging to the attribute template acquired by the attribute template acquisition unit; and acquired by the attribute template acquisition unit Corresponding to the attribute item of the attribute template, at least the attribute template storage means for storing the attribute candidate value acquired by the attribute candidate value acquisition means, and at least the attribute template stored in the attribute template storage means Attribute template acquisition means for acquiring one of the attribute templates; A first attribute item storage control unit for storing an attribute item belonging to the acquired attribute template that is the attribute template acquired by the attribute template acquiring unit in the attribute information storage unit by attaching the attribute item to the data file or the deliverable; Acquire at least one of the attribute candidate values stored in the attribute template storage means as the attribute value of the attribute item that is attached to the data file or the deliverable by the first attribute item storage control means. Attribute value acquisition means, and the attribute value acquired by the attribute value acquisition means as the attribute value of the attribute item to be attached to the data file or the deliverable by the first attribute item storage control means First attribute value storage control means for storing in the information storage means.

  In addition, in the file search device of the invention according to claim 4, in addition to the configuration of the invention according to claim 3, setting of an attribute value is indispensable or unnecessary for the attribute item belonging to the acquired attribute template. A setting information acquisition unit that acquires setting information indicating at least one of whether it is an arbitrary value or a fixed value, and the setting information acquisition unit for each attribute item that belongs to the acquisition attribute template File deliverable template storage means for storing the file deliverable template storing the setting information obtained by the step, wherein the attribute template acquisition means is the file deliverable stored in the file deliverable template storage means. Obtaining the attribute template by obtaining at least one of the templates, and obtaining the first attribute item; The memory control means stores the attribute items belonging to the acquired attribute template of the file deliverable template in the attribute information storage means attached to the data file or the deliverable, and the first attribute value storage control means The attribute value is stored in the attribute information storage unit according to the setting information of the file deliverable template.

  Further, in the file search device of the invention according to claim 5, in addition to the configuration of the invention according to any of claims 1 to 4, a common attribute which is an attribute item attached to all the files or the deliverables A common attribute item acquisition unit that acquires an item, and a common attribute candidate value that is one or more values that are candidates for the value of the common attribute item acquired by the common attribute item acquisition unit, for each common attribute item Common attribute candidate value acquisition means, and common attribute information for storing the common attribute candidate value acquired by the common attribute candidate value acquisition means corresponding to the common attribute item acquired by the common attribute item acquisition means And a second attribute for storing the common attribute item stored in the common attribute information storage unit in the attribute information storage unit in association with the data file or the product. At least one of the information storage control means and the common attribute candidate value stored in the common attribute information storage means is attached to the data file or the deliverable by the second attribute item storage control means. A common attribute value acquisition unit that acquires the common attribute value of the common attribute item, and the second attribute item storage control unit converts the common attribute value acquired by the common attribute value acquisition unit into the data file or the deliverable. And second attribute value storage control means for storing in the attribute information storage means as attribute values of the common attribute item.

  Further, in the file search device of the invention according to claim 6, in addition to the configuration of the invention of claim 5, whether or not an attribute value setting is indispensable for the common attribute item, is optional, or optional Or a fixed value, a common setting information acquisition unit that acquires setting information indicating at least one of the fixed value and the file deliverable template storage unit acquires the common setting information for each common attribute item Storing the setting information acquired by the means, and the second attribute item storage control means attaches the attribute item belonging to the acquired attribute template of the file deliverable template to the data file or the deliverable, and And storing the attribute value in the attribute information storage means according to the setting information of the file deliverable template. And to store the 憶 means.

  According to a seventh aspect of the present invention, there is provided a file search program for causing a computer to function as various processing means of the file search apparatus according to any one of the first to sixth aspects.

  In the file search device of the invention according to claim 1, the data file or the product extracted by the search condition is displayed so that the attribute value of the condition attribute item can be identified, and the data file or the result that takes the same attribute value Objects can be displayed in an identifiable manner. Therefore, it is easier to search for the desired data file or deliverable than when the information indicating the extracted file or deliverable is listed. In addition, since data files or deliverables are extracted under the condition of attribute item and attribute item attribute value, all data files or deliverables are obtained rather than being classified and displayed for each attribute item and attribute value. Easy to find data files and deliverables.

  In addition, in the file search device of the invention according to claim 2, in addition to the effect of the invention of claim 1, the condition attribute items have a hierarchical structure according to priority, and the names of the nodes in each hierarchy are attribute values. Thus, the attribute item and the attribute value can be displayed in an identifiable manner. And the identification information of the data file or deliverable which takes the attribute value used as the ancestor is displayed on the lowest layer node. Thereby, data files or deliverables having the same attribute value are displayed under the same lowest layer node. Therefore, data files or deliverables having the same attribute value can be identified. Furthermore, the tree structure makes it easy to see and understand. Therefore, it is easy to search for more desired data files and deliverables.

  Further, in the file search device of the invention according to claim 3, in addition to the effect of the invention of claim 1 or 2, the attribute value of the attribute item can be stored in the attribute information storage means using the attribute template. . Therefore, if the same attribute template is used for data files and deliverables having common contents and characteristics, setting of attribute items is easy. For example, data files and deliverables related to a certain product can be easily managed for each product by using the same attribute template even if the contents are different. Further, since unified attribute items and attribute candidate values are used, management becomes easy. For example, when setting an attribute item with the same meaning, a slightly different attribute item name is set, the expression of an attribute candidate value with the same meaning is slightly different, or the unit and digit of the attribute candidate value are different. There is nothing to do.

  In addition, in the file search device of the invention according to claim 4, in addition to the effect of the invention according to claim 3, setting of attribute values for attribute items is indispensable, unnecessary, or optional. The attribute value of the attribute item can be stored in the attribute information storage unit using the file product template that stores the setting information indicating at least one of the fixed value and the fixed value. Therefore, even if the same attribute template is used, whether the attribute value must be set according to the characteristics of the file or deliverable, whether it is not required, optional, or fixed This makes it easier to manage according to the content and characteristics of files and deliverables.

  In addition, in the file search device of the invention according to claim 5, in addition to the effect of the invention according to any one of claims 1 to 4, since common attribute items are attached to all data files or deliverables, Useful for managing data files or deliverables.

  Further, in the file search device of the invention according to claim 6, in addition to the effect of the invention of claim 5, whether to set an attribute value for a common attribute item is required or unnecessary, Since it can be set as an arbitrary value or a fixed value, management according to the contents and characteristics of files and deliverables becomes easier.

  The file search program of the invention according to claim 7 can achieve the same effect as the effect of the invention according to any one of claims 1 to 6.

  Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a system configuration diagram showing a system configuration of a file search system 5 using a file search server 1 which is a file search apparatus of the present invention. FIG. 2 shows files and deliverables managed by the file search system. It is a schematic diagram which shows a relationship. As shown in FIG. 1, the file search server 1 is connected to a network 3. A client 2 that is a terminal used by a user who uses the file search system can also be connected to the network 3. The client 2 connects to the file search server 1 via the network 3. In the file search server 1, a file search program is executed, and various processes according to requests from the client 2 are performed. In the client 2, a client file search program is executed, and the client 2 is connected to the file search server 1 and performs various processes in response to input from the user.

  In the present embodiment, the file search server 1 manages files in units of “deliverables” composed of one or a plurality of files. That is, the user registers one or a plurality of files as one “product” in the file search system 5. Furthermore, version management is possible for “deliverables”. The example shown in FIG. 2 shows the first to fourth versions of the product named “222-OOa-specification”. As shown in FIG. 2, the first-version product 51 includes a file 511 having a name “222XXa specification”. In the file search server 1, the file 511 at the time of registration is stored in the registered file storage area 155 (see FIGS. 8 and 9) of the HDD 15 of the file search server 1. The product name, the version number, and the storage location of the registered file are stored and managed in the product file information storage area 154 (see FIGS. 9 and 17).

  The product 52 of the second version is composed of two files, a file 521 named “222XXa specifications” and a file 522 named “222xxxa specifications-table”. Yes. Here, the file 511 configuring the first-version product 51 and the file 521 configuring the second-version product 52 have the same name “222XXa specification”, but register the first version. In the case where the contents of the file are changed after this, files having different contents are registered even with the same name.

  The product 53 of the third version is composed of two files: a file 531 named “222XXa specification” and a file 532 named “222XXa specification-table”. Yes. The product 54 of the fourth edition includes a file 541 named “222XXa specification”, a file 542 named “222XXa specification-table”, and “222XXa specification-photo”. ”And a file 543 named“ ”. Similar to the first-version file 511 and the second-version file 521, the third-version file 531 and the fourth-version file 541 have the same name “222 ○ a specification” but the contents of the file. Can be different. Similarly, the file 522, the file 532, and the file 542 have the same “222OO specification-table”, but the file contents may be different.

  Furthermore, in this embodiment, it is possible to set an “attribute item” for these version-managed “deliverables” and assign a value to the attribute item. An attribute item is an item of auxiliary information used to classify or characterize a deliverable. Here, the value of the attribute item is referred to as “attribute value”. In the present embodiment, this attribute item and attribute value are used to search for deliverables. By setting an attribute item suitable for the user's usage environment, it is possible to more efficiently find the desired product.

  In the present embodiment, the attribute items are classified into two categories, “common attribute items” and “individual attribute items”. The common attribute item is a common attribute item in the file search system 5 (see FIGS. 4 and 10). The individual attribute item is an attribute item set for each product (see FIG. 11). For example, when a file search system is used by a manufacturer, what is mainly handled is a “product” to be manufactured. Thus, for example, the use of “product”, “document type”, “series”, “drawing”, and “customer” as common attribute items can be considered. In addition, when used in financial institutions, the main thing to deal with is “money”. Therefore, for example, the use of “deposit type”, “customer”, and “store name” can be considered. In addition, when used at a patent office, “customer” and “special merchandise classification” can be considered as common attribute items. Since these “common attribute items” are attribute items that serve as the basis of the file search system 5, it is desirable to sufficiently examine and set the introduction environment at the time of introduction.

  Also, individual attribute items that match the characteristics of the deliverables are used. For example, when used by a manufacturer, attribute items indicating the characteristics of individual products are conceivable. If the product is a pan, for example, the use of “handle”, “material”, and “lid” can be considered. In addition, when used in a financial institution, “loan type”, “assessment”, “period”, and “document type” can be considered as long as it is a loan-related product. Further, when used at a patent office, “product series”, “person in charge”, “person in charge of customer”, and “application date” can be considered as a product of a patent application.

  In the present embodiment, an “individual attribute template” is used in order to simplify registration of individual attribute items (see FIGS. 5, 12, and 13). In this method, an individual attribute name of an individual attribute item and a value that the attribute item can take as an attribute value are registered as “individual attribute candidate values”. Thereby, when registering a deliverable, an individual attribute item can be easily registered by selecting an individual attribute template and selecting an attribute value from candidate individual attribute values. If it is a manufacturer, it can manage more systematically by using the same individual attribute template for every product. For example, in the case of a cookware manufacturer, for example, an individual attribute template for a pan, an individual attribute template for a frying pan, and an individual attribute template for a knife are created. If it is an automobile manufacturer, an individual attribute template for an engine, an individual attribute template for a door, and an individual attribute template for a seat are created.

  Next, a search screen used when searching for deliverables will be described with reference to FIG. FIG. 3 is a schematic diagram of a search screen 100 that is an example of the search screen. As shown in FIG. 3, the search screen 100 includes a search condition display area 110, a virtual folder tree display area 120, a deliverable tree display area 130, an attribute information display area 140, and a search button 150. In the search condition display area 110, a search condition is specified. As described above, the file search system 5 according to the present embodiment searches for a deliverable using an attribute item. Therefore, the search condition display area 110 includes an attribute item field, a search condition 1 field, a search condition 2 field, a search condition 3 field, a search condition 4 field, a search condition 5 field, and a search condition 6 field. The attribute item column is a list box for selecting one attribute item from previously registered attribute items. The search condition 1 column to the search condition 6 column are list boxes for selecting attribute values of attribute items selected in the attribute item column on the same row or “all attribute item values”. When “all attribute item values” is selected, all attribute candidate values are set as search attribute candidate values. When the search button 150 is pressed, a search based on information input in the search condition display area 110 is performed, and the search result is displayed in the virtual folder tree display area 120 and the deliverable tree display area 130.

  Hereinafter, an attribute item selected in the attribute item column and designated as a search target is referred to as a “search attribute item”, and an attribute value designated as a search target in the search condition 1 column to the search condition 6 column is referred to as a “search attribute value”. That's it. The search attribute item specified in the first line of the attribute item column is called the first search attribute item, the search attribute item specified in the second line is called the second search attribute item, and is designated in the nth line below. The search attribute item is referred to as the nth search attribute item. Similarly, the search attribute value specified in the first line of the attribute item column is referred to as the first search attribute value, the search attribute value specified in the second line is referred to as the second search attribute value, and is specified in the nth line hereinafter. The set search attribute value is referred to as an nth search attribute value.

  In the example illustrated in FIG. 3, the attribute item “product” is the first search attribute item, and “XX” and “XX” are the first search attribute values. The second search attribute item is “document type”, and the second search attribute value is “specification”. The third search attribute item is “series”, and the third search attribute values are “111” and “222”. In the example shown in FIG. 3, three search attribute items are specified. However, it is possible to specify more than three search attribute items by inputting attribute item names and attribute values in the fourth and subsequent rows. .

  In the virtual folder tree display area 120, the state of the search attribute item and the search attribute value specified in the search condition display area 110 are displayed. As shown in FIG. 3, a folder tree is displayed in the virtual folder tree display area 120. Here, a virtual folder whose folder name is the search attribute value of the first search attribute item is displayed in the first hierarchy of the tree, and the second search attribute is displayed below each folder of the first hierarchy in the second hierarchy. A virtual folder with the item search attribute value as the folder name is displayed. In the nth layer, a virtual folder with the search attribute value of the nth search attribute item as the folder name is displayed below each folder in the (n-1) th layer. Therefore, the hierarchy of the folder tree displayed in the virtual folder tree display area 120 and the display order of the folders are in accordance with the specification of the search attribute item and the search attribute value in the search condition display area 110.

  In the example shown in FIG. 3, the first search attribute item is “product”, and the first search attribute values “XX” and “XX”. Therefore, the “XX” folder and the “XX” folder are included in the first hierarchy. It is displayed. In the same hierarchy, from the search attribute value specified in the search condition 1 column, the search attribute value specified in the search condition 2 column, the search attribute value specified in the search condition 3 column, and the search condition 4 column From the retrieved search attribute value, the search attribute value specified in the search condition column 5 and the search attribute value specified in the search condition column 6 are ordered from the upper level (upper part of the virtual folder tree display area 120) to the lower level (lower part). Is displayed. Here, “XX” is designated in the search condition 1 column and “XX” is designated in the search condition 2 column, so the “XXX” folder is displayed at the top.

  Then, a “specification” folder that is the second search attribute value of the second search attribute item is displayed below the “XX” folder. Furthermore, a “specifications” folder is also displayed below the “XX” folder. The “111” folder and the “222” folder, which are the third search attribute values of the third search attribute item, are displayed below the “specification” folder below the “XX” folder. Here, “111” is designated in the search condition 1 column and “222” is designated in the search condition 2 column, so that the “111” folder is displayed at the top. Furthermore, the “111” folder and the “222” folder which are the third search attribute values of the third search attribute item are displayed below the “specification” folder below the “XX” folder.

  In the deliverable tree display area 130, deliverables belonging to the folder selected in the virtual folder tree display area 120 are displayed. In the virtual folder tree display area 120, a lowermost folder can be selected. In the example shown in FIG. 3, the “111” folder below the “specifications” folder below the “XXX” folder is selected and highlighted. The deliverables belonging to the folder are the deliverables extracted by the search. Hereinafter, the product extracted by the search is referred to as “extracted product”. Further, the names of the files constituting the extracted deliverable are displayed in the second hierarchy.

  In the example illustrated in FIG. 3, the attribute value “product” of the attribute item “product” in the “111” folder in the lower layer of the “specifications” folder in the “XX” folder is the attribute item “document type”. The attribute value “” is “specification” and the attribute item “series” has the attribute value “111”. The first version of the deliverable with the name “111-XXa-specification” and the first version of the deliverable with the name “111-XXb-specification”. The first version of the product with the name “111-XXa-specification” is composed of a file with the name “111XXa specification”, and the name “111-XXb-specification”. The first version of the deliverable is composed of a file with the name “111XXb specification” and a file with the name “111XXb specification attached”.

  In the attribute information display area 140, attribute information of the product selected in the product tree display area 130 is displayed. In the product tree display area 130, a product can be selected. In the example illustrated in FIG. 3, the first version of the product with the name “111-XXa-specification” is selected. In this deliverable, the common attribute items “product”, “document type”, “series”, “drawing”, “customer”, individual attribute items “type”, “trajectory”, “lighting” "Is registered. The attribute value of the common attribute item “product” is “XX”, the attribute value of the common attribute item “document type” is “specification”, the attribute value of the common attribute item “series” is “111”, and the individual attribute item The attribute value of “type” is registered as “P”, the attribute value of the individual attribute item “trajectory” is “rotation”, and the attribute value of the individual attribute item “lighting” is registered as “present”. Note that no attribute value is registered for the common attribute items “drawing” and “customer”.

  In the deliverable tree display area 130, a file name can also be selected. Therefore, the selected file can be acquired from the file search server 1 by a predetermined instruction (for example, double-clicking with the mouse, pressing the ENTER key, right-clicking to display the menu and selecting the “acquire” menu).

  Next, with reference to FIGS. 4 to 6, a screen displayed when a product is registered in the file search system 5 will be described. 4 is a schematic diagram of the common attribute information registration screen 210, FIG. 5 is a schematic diagram of the individual attribute template registration screen 220, and FIG. 6 is a schematic diagram of the deliverable template registration screen 230.

  First, the common attribute information registration screen 210 will be described with reference to FIG. In this common attribute information registration screen 210, a “common attribute item” is registered, and a value that is an attribute value of the “common attribute item” is registered as a “common attribute candidate value”. Since common attribute items are commonly used in the file search system 5, in actual operation, common attribute information (common attribute item name and common attribute candidate value) is registered using the common attribute information registration screen 210. This is performed by the system administrator when the file search system 5 is introduced.

  As shown in FIG. 4, the common attribute information registration screen 210 is provided with a common attribute information field 211, an add button 212, a change button 213, a delete button 214, a cancel button 215, and a confirm button 216. In the common attribute information column 211, a common attribute name column and a common attribute candidate value column are provided. In the common attribute name column, the “common attribute name” of the attribute item set as the common attribute item is displayed, and the common attribute candidate value of the common attribute item is displayed on the right. The common attribute name and the common attribute candidate value are stored as “common attribute information” in the common attribute information storage area 1511 (see FIGS. 9 and 10) of the HDD 15 of the file search server 1. In the common attribute information column 211, information stored in the common attribute information storage area 1511 is displayed. In the example illustrated in FIG. 4, the common attribute candidate values of the common attribute name “product” are “XX”, “XX”, “ΔΔ”, and “□□”. Common attribute candidate values for the common attribute name “document type” are “specification”, “plan”, “inspection method”, and “estimate”. Common attribute candidate values for the common attribute name “series” are “111”, “222”, “333”, “444”, and “555”. Common attribute candidate values for the common attribute name “drawing” are “special A0”, “A0”, “A1”, and “A2”. Common attribute candidate values for the common attribute name “customer” are “Company A”, “Company B”, “Company C”, “Company D”, and “Company E”.

  When the add button 212 is pressed on the common attribute information registration screen 210, a new line is inserted into the common attribute information column 211. Therefore, the common attribute name of the new common attribute item can be input in the common attribute name column of the added line, and the common attribute candidate value can be input in the common attribute candidate value column. In addition, when the change button 213 is pressed while the common attribute name displayed in the common attribute name column is selected by a mouse operation or a keyboard operation, the selected common attribute name and common attribute candidate value are input. Is possible. If the delete button 214 is pressed while the common attribute name displayed in the common attribute name column is selected, the selected common attribute item is deleted. When the confirm button 216 is pressed, the common attribute item displayed in the common attribute information column 211 is transmitted to the file search server 1 and stored in the common attribute information storage area 1511 as common attribute information in the file search server 1. Is done. When the cancel button 215 is pressed, the information input on the common attribute information registration screen 210 is discarded and the common attribute information storage area 1511 is not updated.

  In this way, common attribute candidate values are set as possible values for the common attribute items. Therefore, since the common attribute value of the common attribute item is only a predetermined common attribute candidate value, various users do not input various values. Therefore, different values with the same meaning are not input, and the common attribute item can be used effectively.

  Next, the individual attribute template registration screen 220 will be described with reference to FIG. As described above, in this embodiment, an “individual attribute template” is used to simplify the registration of individual attribute items (see FIGS. 12 and 13). This individual attribute template registration screen 220 is a screen for registering an “individual attribute template”. In actual operation, when a new classification (for example, introduction of a new series of products) occurs, an individual attribute template is registered on the individual attribute template registration screen 220.

  As shown in FIG. 5, the individual attribute template registration screen 220 includes an individual attribute template name field 221, an individual attribute information field 222, a new button 223, an add button 224, a change button 225, a delete button 226, a cancel button 227, and a confirmation. A button 228 is provided. The individual attribute template name column 221 is a list box, and the individual attribute template name of the individual attribute template stored in the individual attribute template storage area 1512 (see FIGS. 9 and 11) of the HDD 15 of the file search server 1 is displayed. It is selectable. By selecting an individual attribute template name in the individual attribute template name field 221, an individual attribute template to be edited can be designated.

  Information on the individual attribute template selected in the individual attribute template name field 221 is displayed in the individual attribute information field 222. In the individual attribute information column 222, an individual attribute name column and an individual attribute candidate value column are provided. In the individual attribute name column, “individual attribute name” of the individual attribute item of the selected individual attribute template is displayed, and an individual attribute candidate value of the individual attribute is displayed on the right side. If a new individual attribute template is to be registered, the new button 223 is pressed. Then, since the individual attribute template name field 221 can be input with characters, the user inputs a new individual attribute template name in the individual attribute template name field 221. Note that the individual attribute name and the individual attribute candidate value are not displayed in the individual attribute information column 222. In the example illustrated in FIG. 5, the individual attribute template “XX product Gr” has three individual attributes registered as individual attribute names “type”, “trajectory”, and “lighting”. The individual attribute candidate values of the individual attributes are “type” “P” and “M”, “trajectory” “rotation”, “door”, “slide”, and “lighting”. “Yes” and “No”.

  When the add button 224 is pressed, a new line is inserted into the individual attribute information field 222. Therefore, the individual attribute name of the new individual attribute can be input in the individual attribute name column of the added line, and the individual attribute candidate value can be input in the individual attribute candidate value column. When the change button 225 is pressed while the individual attribute name displayed in the individual attribute name column is selected, the selected individual attribute name and individual attribute candidate value can be input. If the delete button 226 is pressed while the individual attribute name displayed in the individual attribute name column is selected, the selected individual attribute is deleted. When the confirm button 228 is pressed, the individual attributes displayed in the individual attribute information column 222 are transmitted to the file search server 1 and stored in the individual attribute template storage area 1512 as individual attribute information in the file search server 1. The When the cancel button 227 is pressed, information input on the individual attribute template registration screen 220 is discarded and the individual attribute template storage area 1512 is not updated.

  Thus, individual attribute candidate values are set as possible values for the individual attribute items. Therefore, since the individual attribute value of the individual attribute item is only a predetermined individual attribute candidate value, various users do not input various values. Therefore, different values are not input as the same meaning, and individual attribute items can be used effectively. Individual attribute items can be grouped and registered as individual attribute templates. Therefore, unify the settings of individual attribute items in the same classification, such as using the same individual attribute template in the classification for managing the deliverables (for example, deliverables related to the same product, deliverables used in the same department) Convenient for.

  Next, the deliverable template registration screen 230 will be described with reference to FIG. The deliverable template registration screen 230 is a screen for registering a “deliverable template”. In the present embodiment, in order to simplify the setting of attribute items and attribute values to deliverables, attribute item combinations and attribute value setting information to attribute items are registered as “deliverable templates”. The setting information is a condition indicating whether registration of the attribute value is “required”, “impossible”, “arbitrary”, or “fixed value”. In this embodiment, setting information of “required”, “impossible”, “arbitrary”, “fixed value” is provided for common attribute items, and “required”, “impossible” for individual attribute items. ”And“ arbitrary ”setting information.

  As shown in FIG. 6, the deliverable template registration screen 230 includes an deliverable template name field 231, a new button 232, a common attribute information field 233, an individual attribute template selection field 234, an individual attribute information field 235, a confirm button 236, A cancel button 237 is provided. The deliverable template name field 231 is a list box, and the deliverable template name of the deliverable template stored in the template storage area 152 of the HDD 15 of the file search server 1 (see FIGS. 9, 12, and 13). Is selectable. By selecting a product template name in the product template name field 231, a product template to be edited can be designated. Information about the product template selected in the product template name column 231 is displayed in the common attribute information column 233, the individual attribute template selection column 234, and the individual attribute information column 235.

  The common attribute information column 233 includes a common attribute name column, a setting information column, and a fixed value column. The common attribute name column is a list box, and the common attribute name of the common attribute item stored in the common attribute information storage area 1511 can be selected. The setting information column is also a list box, and one setting information can be selected from “required”, “impossible”, “arbitrary”, and “fixed value”. Furthermore, the fixed value field is also a list box, and only when “fixed value” is selected in this setting information field, the common attribute name selected in the common attribute name field of the same column in the fixed value field. A common attribute candidate value of the common attribute item can be selected. When the new button 232 is pressed, characters can be input to the product template name field 231, and initial values are displayed in the common attribute information field 233, the individual attribute template selection field 234, and the individual attribute information field 235. Is done. For example, all of the setting information fields of the common attribute information field 233 are set to “arbitrary”, and are not selected in the individual attribute template selection field 234.

  In the example illustrated in FIG. 6, the setting information of the common attribute item whose common attribute name is “product” is “fixed value”, and the value is “XX”. The setting information of the common attribute item whose common attribute name is “document type” is also “fixed value”, and the value is “specification”. And the setting information of the common attribute item whose common attribute name is “series” is “required”, the setting information of the common attribute item whose common attribute name is “drawing” is “impossible”, The setting information of the common attribute item whose common attribute name is “customer” is “arbitrary”.

  The individual attribute template selection field 234 is a list box, and an individual attribute template name registered as “individual attribute template” can be selected. The individual attribute information column 235 includes an individual attribute name column and a setting information column. In the individual attribute name column, “individual attribute name” of the individual attribute item of the individual attribute template selected in the individual attribute template selection column 234 is displayed, and setting information of the individual attribute is displayed on the right side. The setting information column is a list box, and one setting information can be selected from “required”, “impossible”, and “optional”.

  In the example shown in FIG. 6, “XX product Gr” is selected as the individual attribute template. In the individual attribute name column, individual attribute item names “type”, “trajectory”, and “lighting” registered in the individual attribute template “XX product Gr” are displayed. And the setting information of the individual attribute item with the individual attribute name “type” is “required”, the setting information of the individual attribute item with the individual attribute name “trajectory” is “impossible”, and the individual attribute name “lighting” The setting information of the individual attribute item is “arbitrary”.

  As described above, since the setting condition of the attribute item can be set, a necessary attribute item value is not set and an unnecessary attribute item value is not set. In addition, since attribute item values can be fixed values, it is possible to manage them as fixed values by classification when managing deliverables (for example, deliverables related to the same product and deliverables used in the same department). . In addition, since common attribute items and individual attribute items can be grouped as a deliverable template, when registering deliverables, simply call the deliverable template and set the attribute item values, so attributes Items and attribute values can be set.

  Next, the deliverable registration screen 240 used when registering the deliverable in the file search system 5 will be described with reference to FIG. FIG. 7 is a schematic diagram of the product registration screen 240. In the product registration screen 240, a product name and version are input, an attribute value is set, and a file to be registered as this product is designated. Further, a product related to this product (hereinafter referred to as “link product”) is designated. As shown in FIG. 7, the product registration screen 240 includes a product name input field 241, a version input field 242, a product template selection field 243, a common attribute information field 244, an individual attribute information field 245, and a file specification field 246. , A file reference button 2461, a link product designation field 247, a link product reference button 2471, a confirmation button 248, and a cancel button 249 are provided.

  The product name input field 241 is a text box in which the name of the product to be registered is input. The version input field 242 is a text box in which the version number of the product to be registered is input. The deliverable template selection field 243 is a list box, and the deliverable template name of the deliverable template stored in the template storage area 152 of the HDD 15 of the file search server 1 can be selected. In the common attribute information column 244, the common attribute value of the common attribute item is designated. The common attribute value is specified by selecting a list in the list box. For common attribute items whose setting information is “fixed value” in the deliverable template selected in the deliverable template selection field 243, the list in the list box includes only values that are “fixed value”. Yes. For common attribute items whose setting information is “impossible”, a selectable list is not displayed in the common attribute item value column, and individual attribute values cannot be selected. For common attribute items whose setting information is “essential” or “optional”, all common attribute candidate values are listed.

  In the individual attribute information column 245, the individual attribute items set in the product template selected in the product template selection column 243 are displayed, and the individual attribute value is designated. Individual attribute values are specified by selecting a list in the list box. For individual attribute items whose setting information is “impossible” in the deliverable template selected in the deliverable template selection field 243, a selectable list is not displayed, and an individual attribute value cannot be selected. ing. For common attribute items whose setting information is “essential” or “optional”, all common attribute candidate values are listed.

  In the file designation field 246, a path indicating the location of the file to be registered is input. When the file reference button 2461 is pressed, a screen (not shown) in which a file name of a file stored in a storage medium that can be referred to by the client 2 can be selected is displayed separately. When a file name is designated on the screen, a path is entered in the file designation field 246. The file specified by the path input here is the file constituting the product.

  In the link product designation field 247, a product related to the product to be registered is designated as a “link product”. When the link deliverable reference button 2471 is pressed, the deliverable product name stored in the deliverable file information storage area 154 (see FIGS. 9 and 17) of the HDD 15 of the file search server 1 can be selected. A screen (not shown) displayed on is displayed separately. When the product name is designated on this screen, the product name is input to the link product designation field 247.

  When the confirm button 248 is pressed, a product based on information input on the product registration screen 240 is transmitted to the file search server 1 and stored in the registered file storage area 155 in the file search server 1. If the cancel button 249 is pressed, the deliverable is not registered. In the example illustrated in FIG. 7, the product name is the first version of “111-XXa-specification”, and the product template is “XX product Gr”. The common attribute item “Product” is “XX”, “Document type” is “Specification”, “Series” is “111”, “Drawing”, and “Customer” are not set. The “type” of the individual attribute item is “P”, “trajectory” is not set, and “lighting” is “present”. As the file, a file “111XXa specification” in the XX folder of the 2007 document folder of the C drive is designated. Also, the first version of “222XXa specification” is designated as the link product.

  Accordingly, it is possible to register a product in the file search server 1 by designating a file constituting the product. Furthermore, the attribute item and the attribute value can be easily set simply by calling the deliverable template and setting the attribute item value.

  Next, the electrical configuration of the file search server 1 will be described with reference to FIG. FIG. 8 is a schematic diagram showing an electrical configuration of the file search server 1. As shown in FIG. 8, the file search server 1 is provided with a CPU 10 that controls the file search server 1. The CPU 10 includes a RAM 11 that temporarily stores various data, a ROM 12 that stores BIOS, and the like. Also, an I / O interface 14 that mediates data transfer is connected. A hard disk device 15 is connected to the I / O interface 14. In addition, a video controller 18, a key controller 16, a mouse controller 17, and a communication device 19 are connected to the I / O interface 14. A display 181 is connected to the video controller 18, a keyboard 161 is connected to the key controller 16, and a mouse 171 is connected to the mouse controller 17. The communication device 19 can be connected to the network 3.

  Next, various storage areas provided in the HDD 15 of the file search server 1 will be described with reference to FIGS. 9 to 17. 9 is a schematic diagram showing the configuration of the HDD 15, FIG. 10 is a schematic diagram showing the configuration of the common attribute information storage area 1511, and FIG. 11 is a schematic diagram showing the configuration of the individual attribute template storage area 1512. is there. 12 is a schematic diagram showing the configuration of the XX product Gr product template storage area 1521. FIG. 13 is a schematic diagram showing the configuration of the XX product Gr product template storage area 1522. As shown in FIG. 14 is a schematic diagram showing the configuration of the XX product Gr deliverable attribute information storage area 1531. FIG. 15 is a schematic diagram showing the configuration of the XX product Gr deliverable attribute information storage area 1532. FIG. These are schematic diagrams showing the configuration of the ΔΔ product Gr product attribute information storage area 1533. FIG. 17 is a schematic diagram showing the configuration of the deliverable file information storage area 154.

  First, the HDD 15 will be described with reference to FIG. The HDD 15 includes an attribute information storage area 151, a template storage area 152, a product attribute information storage area 153, a product file information storage area 154, a registration file storage area 155, an authority information storage area 156, a search result storage area 157, a program A storage area 158 is provided at least. In the attribute information storage area 151, a common attribute information storage area 1511 (see FIG. 10) and an individual attribute template storage area 1512 (see FIG. 11) are provided. Information regarding common attributes (common attribute information) is stored in the common attribute information storage area 1511, and individual attribute templates are stored in the individual attribute template storage area 1512.

  A product template is stored in the template storage area 152. In the template storage area 152, a storage area is provided for each individual attribute template employed in the product template. In the example illustrated in FIG. 9, “XX product Gr product template” in which “XX product Gr” is adopted as the individual attribute template, XX product Gr product template in which “XX product Gr” is adopted, “ △△ Product Gr product template in which △△ product Gr '' is adopted is stored, XX product Gr product template storage area 1521 (see FIG. 12), XX product Gr product template storage area 1522 ( 13), ΔΔ product Gr deliverable template storage area 1523 is provided.

  In the deliverable attribute information storage area 153, attribute information for the deliverable is stored for each deliverable template. XX product Gr deliverable attribute information, XX product Gr deliverable attribute information, and △△ product Gr deliverable attribute information are stored, XX product Gr deliverable attribute information storage area 1531 (see FIG. 14), x × Product Gr product attribute information storage area 1532 (see FIG. 15) and ΔΔProduct Gr product attribute information storage area 1533 (see FIG. 16) are provided.

  In the deliverable file information storage area 154 (see FIG. 17), information related to the deliverable (deliverable file information) is stored. The registered file storage area 155 stores files registered as deliverables. The authority information storage area 156 stores a user ID of a user (administrator) who can perform a process requiring authority (for example, registration of common attribute items). The search result storage area 157 stores information about the product extracted as the search result. The program storage area 158 stores a file search program for operating the file search server 1 and various information used in the program.

  Next, the common attribute information storage area 1511 will be described with reference to FIG. In the common attribute information storage area 1511, names of common attribute items and common attribute candidate values are stored. Therefore, a common attribute name column and a common attribute candidate value column are provided. In the example illustrated in FIG. 10, the common attribute candidate values of the common attribute name “product” are exemplified as “OO”, “XX”, “ΔΔ”, and “□□”. Examples of common attribute candidate values for the common attribute name “document type” are “specification”, “plan”, “inspection method”, and “estimate”. Examples of common attribute candidate values for the common attribute name “series” are “111”, “222”, “333”, and “444”. Examples of common attribute candidate values for the common attribute name “drawing” are “special A0”, “A0”, “A1”, and “A2”. Examples of common attribute candidate values of the common attribute name “customer” are “Company A”, “Company B”, “Company C”, and “Company D”.

  Next, the individual attribute template storage area 1512 will be described with reference to FIG. In the individual attribute template storage area 1512, names of individual attribute items and individual attribute candidate values set for each individual attribute template are stored. Therefore, an individual attribute template name field and an individual attribute content field are provided, and an individual attribute name field and an individual attribute candidate value field are provided in the individual attribute content field. In the example illustrated in FIG. 11, individual attribute items of individual attribute names “type”, “trajectory”, and “lighting” are registered in the individual attribute template name “XX product Gr”. The individual attribute candidate values for the individual attribute name “type” are “P” and “M”, and the individual attribute candidate values for the individual attribute name “trajectory” are “rotation”, “door”, and “slide”. Yes, the individual attribute candidate values for the individual attribute name “lighting” are “present” and “none”. In the individual attribute template name “xx product Gr”, individual attribute items of individual attribute names “type”, “operation”, “lighting”, and “drive” are registered. The individual attribute candidate values for the individual attribute name “type” are “A” and “M”, and the individual attribute candidate values for the individual attribute name “operation” are “P”, “D”, and “R”. Yes, the individual attribute candidate values for the individual attribute name “lighting” are “present” and “none”, and the individual attribute candidate values for the individual attribute name “drive” are “electricity” and “wire”. In the individual attribute template name “ΔΔ product Gr”, individual attribute items of individual attribute names “type”, “trajectory”, “number”, and “size” are registered. The individual attribute candidate values for the individual attribute name “type” are “P” and “M”, and the individual attribute candidate values for the individual attribute name “trajectory” are “rotation”, “door”, and “slide”. Yes, the individual attribute candidate values for the individual attribute name “number” are “1”, “2”, and “3”, and the individual attribute candidate values for the individual attribute name “size” are “L” and “LL”. is there.

  Next, with reference to FIG. 12 and FIG. 13, a storage area for each product template provided in the template storage area 152 will be described. As shown in FIGS. 12 and 13, each product template storage area includes a product template name column, a common attribute column, and an individual attribute column. In the common attribute column, columns corresponding to common attribute items that are only set in the common attribute information storage area 1511 are provided. In the individual attribute information column, a column corresponding to the individual attribute item registered in the adopted individual attribute template is provided. As shown in FIG. 10, “product”, “document type”, “series”, “drawing”, and “customer” are registered as common attribute items. Therefore, the individual product columns of the XX product Gr deliverable template storage area 1521 and the XX product Gr deliverable template storage area 1522 include a “product” column, a “document type” column, a “series” column, a “drawing” column, A “customer” column is provided.

  A XX product Gr product template storage area 1521 shown in FIG. 12 stores a product template in which “XX product Gr” is adopted as the individual attribute template. As shown in FIG. 11, in the individual attribute template “XX product Gr”, “type”, “trajectory”, and “lighting” are set as individual attribute items. Therefore, in the individual attribute column of the XX product Gr product template storage area 1521, a “type” column, a “trajectory” column, and an “illumination” column are provided. Further, the xx product Gr product template storage area 1522 shown in FIG. 13 stores a product template in which “xx product Gr” is adopted as the individual attribute template. As shown in FIG. 11, in the individual attribute template “xx product Gr”, “type”, “operation”, “lighting”, and “drive” are set as individual attribute items. Therefore, in the individual attribute column of the XX product Gr product template storage area 1522, a “type” column, an “operation” column, an “illumination” column, and a “drive” column are provided.

  For example, in the XX product Gr product template storage area 1521 shown in FIG. 12, the product template name “XX product specification”, “XX product plan”, “XX product inspection method”, “XX product” Deliverable template of “estimate” is registered. For example, in the deliverable template “XX product specification”, the common attribute “product” is fixed value “XX”, “document type” is fixed value “specification”, and “series” Is mandatory, “drawing” is not allowed, and “customer” is optional. The individual attribute “type” is essential, “trajectory” is essential, and “lighting” is essential. In the deliverable template “XX Product Planning Diagram”, the common attribute “Product” has a fixed value “XX”, “Document Type” has a fixed value “Plan Drawing”, and “Series” is mandatory. The “drawing” is essential and the “customer” is optional. The individual attribute “type” is essential, “trajectory” is essential, and “lighting” is essential.

  Next, each product attribute information storage area provided in the product attribute information storage area 153 will be described with reference to FIGS. 14 to 16. As shown in FIGS. 14 to 16, each product attribute information storage area includes a product name column, a version column, a product template name column, a common attribute column, and an individual attribute column. In the common attribute column, columns corresponding to common attribute items that are only set in the common attribute information storage area 1511 are provided. As shown in FIG. 10, “product”, “document type”, “series”, “drawing”, and “customer” are registered as common attribute items. Accordingly, the product attribute field, the “document type” field, the “series” field, the “drawing” field, and the “customer” field are included in the common product attribute fields 1531 to 1533 shown in FIGS. Is provided.

  In the individual attribute information column, a column corresponding to the individual attribute item registered in the individual attribute template adopted in the adopted product template is provided. For example, in the XX product Gr product attribute information storage area 1531 shown in FIG. 14, the product template “XX product specification” is adopted in the first version of the product name “111-XXa-specification”. Has been. As shown in FIG. 12, the product template “XX product specification” is stored in the XX product Gr product template storage area 1521, and the individual attribute template “XX product Gr” is adopted. As shown in FIG. 11, in the individual attribute template “XX product Gr”, “type”, “trajectory”, and “lighting” are set as individual attribute items. Therefore, in the individual attribute column of the XX product Gr product attribute information storage area 1531, a “type” column, a “trajectory” column, and an “illumination” column are provided. The common attribute value of the common attribute item “product” in the common attribute column is set to “XX”, the common attribute value of the common attribute item “document type” is set to “specification”, and the common attribute item “series” The common attribute value of “111” is set, the common attribute value of the common attribute item “drawing” is not set, and the common attribute value of the common attribute item “customer” is not set. The individual attribute value of the individual attribute item “type” in the individual attribute column is set to “P”, the individual attribute value of the individual attribute item “trajectory” is set to “rotation”, and the individual attribute item “lighting” The attribute value is set to “Yes”.

  Next, the product file information storage area 154 will be described with reference to FIG. As shown in FIG. 17, the deliverable file information storage area 154 includes a deliverable name column, a version column, a file name column, a storage location column, and a link deliverable name. The product name field stores the product name input in the product name input field 241 of the product registration screen 240, and the version field stores the version input in the version input field 242 of the product registration screen 240. The file name of the file designated in the file designation field 246 of the deliverable registration screen 240 is stored as the file name constituting the deliverable, and is designated in the storage location field. A path indicating a storage location where the file is stored is stored. This storage location is not a storage medium that can be referred to by the client 2 but a registered file storage area 155 of the HDD 15 of the file search server 1 that stores a file acquired therefrom. In the link product name field, the product name of the link product specified in the link product specification field 247 of the product registration screen 240 is stored.

  Next, search results displayed on the search screen will be described with reference to FIGS. As described with reference to the search screen 100 shown in FIG. 3, in this embodiment, an attribute item and its attribute value are specified as a search condition. The search condition is displayed as a hierarchical folder tree in the virtual folder tree display area 120, and the deliverables belonging to the folder selected in the virtual folder tree display area 120 are displayed in the deliverable tree display area 130. 18 to 19 are schematic diagrams of search screens when search attribute items are designated in an order different from the search conditions on the search screen 100 shown in FIG. FIG. 18 is a schematic diagram of a search screen 101 which is an example of a search screen. FIG. 19 is a schematic diagram of a search screen 102 which is an example of a search screen. FIG. 20 is a schematic diagram of a search screen 103 which is an example of a search screen.

  Comparing the search screen 100 shown in FIG. 3, the search screen 101 shown in FIG. 18, and the search screen 102 shown in FIG. 19, the types of search attribute items are “product”, “document type”, and “series”. The search attribute value of the search attribute item is the same, but the order is different. The search screen 100 shown in FIG. 3 includes the first search attribute item “product”, the second search attribute item “document type”, and the third search attribute item “series”. In the search screen 101 shown in FIG. 18, the first search attribute item “series”, the second search attribute item “document type”, and the third search attribute item “product”. In the search screen 102 shown in FIG. 19, the first search attribute item “document type”, the second search attribute item “series”, and the third search attribute item “product”. In each search screen, the search attribute item values are “XX” and “XX” for the search attribute item “Product”, “Specification” for the search attribute item “Document type”, and “Series” for the search attribute item “Series”. “111” and “222” are designated. Therefore, in any search screen, the attribute value of the attribute item “product” is “XX” or “XX”, the attribute item “document type” is “specification”, and the attribute item “series” “” Is “111” or “222” as a search target.

  However, because the search attribute items are specified in different order on each search screen, the folder display in the virtual folder tree display area 120 is different. As described above, in the search screen 100, the “XX” folder and the “XX” folder are displayed in the first layer. The “specifications” folder is displayed in the lower layer (second layer) of the “XX” folder, and the “111” folder and the “222” folder are displayed in the lower layer (third layer). A “specifications” folder is also displayed below the “XX” folder, and a “111” folder and a “222” folder are further displayed below. In the search screen 101, a “111” folder and a “222” folder are displayed in the first layer. A “specifications” folder is displayed in the lower layer (second layer) of the “111” folder, and a “◯◯” folder and an “xxx” folder are displayed in the lower layer (third layer). The “specifications” folder is also displayed in the lower layer (second layer) of the “222” folder, and the “XX” folder and the “XX” folder are displayed in the lower layer (third layer). In the search screen 102, a “specification” folder is displayed in the first hierarchy, and a “111” folder and a “222” folder are displayed in the second hierarchy. In the lower layer (third layer) of the “111” folder, a “XX” folder and a “XX” folder are displayed. Below the “222” folder (third layer), a “XX” folder and a “XX” folder are displayed.

  In the search screen 100, the “111” folder in the “specifications” folder in the “XX” folder is selected. On the search screen 101, the “XX” folder in the “Specifications” folder in the “111” folder is selected. On the search screen 102, the “XX” folder in the “111” folder in the “Specifications” folder is selected. That is, in any of the search screens, a folder indicating a product in which attribute values of product “XX”, document type “specification”, and series “111” are set is selected. Therefore, the first version of the same product “111-XXa-specification” and the first version of “111-XXb-specification” are displayed in the product tree display area 130. In the search screen 103 shown in FIG. 20, the “xxx” folder in the “111” folder in the “specifications” folder is selected, and the first version of the product “111-xxxa-specifications”, The second edition of “111-xxxa-specification” is displayed. In this way, by changing the folder to be selected, it is possible to know the deliverables belonging to the folder (having its search attribute value set).

  Thus, since the virtual folder tree is displayed based on the designation order of the search attribute items, it is easy to find the desired product by devising the designation order of the search attribute items. For example, when searching for a file that constitutes a deliverable that is a “specification” of a product “XX”, if you want to compare deliverables for each series, “product” as in the search screen 100 It is easy to compare by specifying search attribute items in the order of “document type” and “series”. When comparing specifications of the same series for each product, it is easy to compare by specifying search attribute items in the order of “series”, “document type”, and “product” as in the search screen 101. By setting attribute items according to the user's usage environment, it is possible to display a virtual folder tree that is easier to see in each user's environment.

  Further, not only the attribute items are specified and the virtual folder hierarchy is in the order of the specified search attribute items, but the attribute value is also specified and the folder name of the virtual folder is used as the search attribute value. Therefore, the number of virtual folders is only the number of designated search attribute values. Therefore, even when there are a large number of candidate attribute values for the search attribute item, the virtual folder of the desired attribute value is displayed, so it is not necessary to find the desired attribute value from among the large number. That is, it is possible to easily find a folder having the attribute value to be obtained.

  In addition, since common attribute items and individual attribute items are set according to the usage environment, what individual attribute items are set for which deliverables, what common attribute values and individual attribute values are set. Even if you don't remember what you set, you can easily find it by searching. Further, even a user who is not familiar with the work in the usage environment can easily find out by searching if the characteristics of the desired product are known.

  Next, the operation of the file search server 1 will be described with reference to FIGS. 21 is a flowchart of the common attribute registration process, FIG. 22 is a flowchart of the individual attribute template registration process, FIG. 23 is a flowchart of the deliverable template registration process, and FIG. 24 is a flowchart of the deliverable registration process. FIG. 25 is a flowchart of the search process, and FIG. 26 is a flowchart of the file acquisition process.

  First, the common attribute registration process will be described with reference to FIG. The common attribute registration process is a process for registering the common attribute input on the common attribute information registration screen 210 (see FIG. 4). The process is started when a request for displaying the common attribute information registration screen 210 is received from the client 2.

  First, information for displaying a user ID input screen (not shown) is transmitted to the client 2 (S1). The user ID input screen includes a user ID input field, an OK button, and a cancel button. In the client 2, when the user inputs a user ID and the OK button is pressed, the input ID information is transmitted to the file search server 1. Further, when the user presses the cancel button, information indicating cancellation is transmitted to the file search server 1. The received information is stored in a predetermined storage area (not shown) of the RAM 11. Therefore, in the file search server 1, when information for displaying an input screen for the user ID is transmitted to the client 2, an input reception process is performed (S2). Here, reception of ID information or cancellation information from the client 2 is performed. Although not shown in the figure, if there is no response from the client 2 for a predetermined time (for example, 3 minutes), the connection with the client 2 is cut off, and this processing ends.

  Next, it is determined whether cancel information has been received from the client 2 (S3). If it is cancel information (S3: YES), it is not necessary to display the common attribute information registration screen 210 on the client 2, so this process ends.

  If it is not cancellation information (S3: NO), since the ID information is transmitted, it is determined whether or not the user of the ID has the authority to set the common attribute information (S4). . If the authority information storage area 156 of the HDD 15 is referred to and the received user ID is stored, it is determined that the user is authorized (S4: YES). If the received user ID is not stored in the authority information storage area 156 and has no authority (S4: NO), an error screen indicating "no authority to register common attribute information" is displayed. Information to be transmitted is transmitted to the client 2 (S10), and this process ends.

  If the user has authority (S4: YES), information for displaying the common attribute information registration screen 210 is transmitted to the client 2 (S5). Here, the information stored in the common attribute information storage area 1511 is read, and the information of the common attribute information registration screen 210 set in the common attribute information column 211 is transmitted. Next, an input reception process is performed (S6). In the client 2, when the confirmation button 216 on the common attribute information registration screen 210 is pressed, the common attribute information input in the common attribute information column 211 is transmitted to the file search server 1. When the cancel button 215 is pressed, information indicating cancellation is transmitted to the file search server 1. The received information is stored in a predetermined storage area (not shown) of the RAM 11. In S6, information transmitted by pressing the confirm button 216 or the cancel button 215 is accepted. Although not shown in the figure, if there is no response from the client 2 for a predetermined time (for example, 3 minutes), the connection with the client 2 is cut off, and this processing ends.

  Next, it is determined whether or not cancel information is received in S6 (S7). If cancel information has been received (S7: YES), this process ends. If the cancel information has not been received (S7: NO), the received common attribute information is stored in the common attribute information storage area 1511 (S8). Here, when the number of common attribute items of the received common attribute information is different from the number of common attribute items in the common attribute item column of the common attribute information storage area 1511, that is, common attribute items have been added or deleted. In this case, the common attribute item added to the common attribute column in the template storage area 152 and the common attribute item in the common attribute column in the product attribute information storage area 153 are added, or the deleted common attribute item is deleted. Or Then, information for displaying a registration completion screen indicating that the registration of the common attribute information is completed is transmitted to the client 2 (S9), and this process ends.

  In this way, when the common attribute information registration screen 210 is displayed on the client 2 in response to a request from the client 2 and the common attribute information input by the user in the client 2 is received, it is stored in the common attribute information storage area 1511. Can do.

  First, the individual attribute template registration process will be described with reference to FIG. The individual attribute template registration process is a process of registering the individual attribute template input on the individual attribute template registration screen 220 (see FIG. 5). This process is started when a request for displaying the individual attribute template registration screen 220 is received from the client 2.

  First, information for displaying the individual attribute template registration screen 220 is transmitted to the client 2 (S11). Here, the information stored in the individual attribute template name field of the individual attribute template storage area 1512 is read out to be a list in the individual attribute template name field 221 (list box), and the individual attribute template name field 221 displays the individual attribute template. When the name is selected, information for displaying the individual attribute name and the individual attribute candidate value in the individual attribute information column 222 is transmitted. Next, an input reception process is performed (S12). In the client 2, when the confirmation button 228 on the individual attribute template registration screen 220 is pressed, the information input in the individual attribute template name field 221 and the individual attribute information field 222 is transmitted to the file search server 1. When the cancel button 227 is pressed, information indicating cancellation is transmitted to the file search server 1. The received information is stored in a predetermined storage area (not shown) of the RAM 11. In S12, information transmitted by pressing the confirm button 228 or the cancel button 227 is accepted. Although not shown in the figure, if there is no response from the client 2 for a predetermined time (for example, 3 minutes), the connection with the client 2 is cut off, and the present process ends.

  Next, it is determined whether or not cancel information is received in S12 (S13). If cancel information has been received (S13: YES), this process ends. If the cancel information has not been received (S13: NO), the received information is stored in each column of the individual attribute template storage area 1512 (S14). Specifically, it is searched whether the individual attribute template name is stored in the individual attribute template name column of the individual attribute template storage area 1512. If not stored, a new record is added, the received individual attribute template name is stored in the individual attribute template name column, and the received individual attribute information is stored in the individual attribute content column. If the individual attribute template name has already been stored, the received individual attribute information is overwritten and updated in the individual attribute content column of the record. Next, information for displaying a registration completion screen indicating that the registration of the individual attribute template is completed is transmitted to the client 2 (S15), and this process ends.

  In this way, upon receiving a request from the client 2, the individual attribute template registration screen 220 is displayed on the client 2, and when information on the individual attribute template input by the user in the client 2 is received, the individual attribute template storage area 1512 stores the information. can do.

  First, the deliverable template registration process will be described with reference to FIG. The deliverable template registration process is a process of registering the deliverable template input on the deliverable template registration screen 230 (see FIG. 6). This process is started when a request for displaying the deliverable template registration screen 230 is received from the client 2.

  First, information for displaying the deliverable template registration screen 230 is transmitted to the client 2 (S21). Here, in addition to the form of the deliverable template registration screen 230, the following information is transmitted. The deliverable name stored in the deliverable template name column of each deliverable template storage area in the template storage area 152 is read out to be a list in the deliverable template name column 231 (list box). Further, the common attribute name stored in the common attribute information storage area 1511 is set in the common attribute name column of the common attribute information column 233. The individual attribute template names stored in the individual attribute template name field of the individual attribute template storage area 1512 are used as a list in the individual attribute template selection field 234 (list box). Then, the individual attribute name and individual attribute candidate value of the individual attribute template selected in the individual attribute template selection field 234 are set as information to be displayed in the individual attribute information field 235.

  Next, an input reception process is performed (S22). In the client 2, when the user presses the confirmation button 236 on the product template registration screen 230, the product template name field 231, the common attribute information field 233, the individual attribute template selection field 234, and the individual attribute information field 235 are displayed. Are transmitted to the file search server 1 as product template names, common attribute information, individual attribute templates, and individual attribute information. When the cancel button 237 is pressed, information indicating cancellation is transmitted to the file search server 1. The received information is stored in a predetermined storage area (not shown) of the RAM 11. In S22, information transmitted by pressing the confirm button 236 or the cancel button 237 is accepted. Although not shown in the figure, if there is no response from the client 2 for a predetermined time (for example, 3 minutes), the connection with the client 2 is cut off, and the present process ends.

  Next, it is determined whether or not cancel information is received in S22 (S23). If cancel information has been received (S23: YES), this process ends. If the cancel information is not received (S23: NO), the received information is stored in each column of the template storage area 152 (S24). Specifically, it is searched whether the product template name is stored in the product template name column of each product template storage area of the template storage area 152. If not stored, the product template storage area corresponding to the individual attribute template selected in the individual attribute template selection field 234 of the product template registration screen 230 is first searched, and the product template storage area is searched. A new record is added to Then, the received common attribute information is stored in the common attribute column of the newly added record, and the received individual attribute information is stored in the individual attribute column. If the deliverable template name has already been stored, the received common attribute information is overwritten in the common attribute column of the record, and the received individual attribute information is overwritten in the individual attribute column. Next, information for displaying a registration completion screen indicating that the registration of the deliverable template has been completed is transmitted to the client 2 (S25), and this process ends.

  In this way, the deliverable template registration screen 230 is displayed on the client 2 in response to a request from the client 2, and when the information on the deliverable template input by the user is received in the client 2, it is stored in the template storage area 152. Can do.

  First, the product registration process will be described with reference to FIG. The product registration process is a process of registering the product input on the product registration screen 240 (see FIG. 7). This process is started when a request for displaying the product registration screen 240 is received from the client 2.

  First, information for displaying the product registration screen 240 is transmitted to the client 2 (S31). Here, in addition to the form of the product registration screen 240, the following information is transmitted. Information stored in the deliverable template name field of each deliverable template storage area in the template storage area 152 is read out and used as a list in the deliverable template selection field 243 (list box). Furthermore, the common attribute name stored in the common attribute information storage area 1511 is set in the common attribute name field of the common attribute information field 244 according to the product template selected in the product template selection field 243, and the common attribute The candidate value is a list in the common attribute candidate value column (list box). Only the values specified as fixed values are listed in the common attribute item that is “fixed value” in the deliverable template, and no value is set in the list for the common attribute item that is “impossible”. Further, individual attribute candidate values are also set in the list in the individual attribute value field (list box) of the individual attribute information field 245 according to the individual attribute template adopted by the product template. In this case as well, no value is set in the list for individual attribute items that are set to “impossible” in the deliverable template.

  Next, an input reception process is performed (S32). In the client 2, when the confirm button 248 on the product registration screen 240 is pressed, the product name input field 241, the version input field 242, the product template selection field 243, the common attribute information field 244, the individual attribute information field 245, Information displayed in the link product designation field 247 is transmitted to the file search server 1 as a product name, version, selected product template, common attribute information, individual attribute information, and link product. Further, the file stored in the location indicated by the path displayed in the file designation field 246 is also transmitted to the file search server 1 as the designated file. When the cancel button 249 is pressed, information indicating cancellation is transmitted to the file search server 1. The received information is stored in a predetermined storage area (not shown) of the RAM 11. In S32, the information transmitted by pressing the confirm button 248 or the cancel button 249 is received. Although not shown in the figure, if there is no response from the client 2 for a predetermined time (for example, 3 minutes), the connection with the client 2 is cut off, and the present process ends.

  Next, it is determined whether or not cancel information is received in S32 (S33). If cancel information has been received (S33: YES), this process ends. If cancel information has not been received (S33: NO), the received information is stored in the deliverable file information storage area 154 (S34). Specifically, a new record is added, the received product name is stored in the product name field, the received version is stored in the version field, and the received link product is stored in the link product field. . Further, the file name of the received designated file is stored in the file name column. Next, the received information is stored in the deliverable attribute information storage area 153 (S35). Specifically, a new record is added to the product attribute information storage area corresponding to the selected product template, the received product name is stored in the product name column, and the received version is stored in the version column. Further, the received common attribute information is stored in the common attribute column, and the received individual attribute information is stored in the individual attribute column. Then, the received designated file is stored in the registered file storage area 155, and the stored location (path) is stored in the storage location column of the deliverable file information storage area 154 (S36). Next, information for displaying a registration completion screen indicating that the registration of the deliverable template has been completed is transmitted to the client 2 (S37), and this process ends.

  In this way, when the product registration screen 240 is displayed on the client 2 in response to a request from the client 2 and information on the product input by the user in the client 2 is received, the product attribute information storage area 153, the product is displayed. The file information storage area 154 and the registered file storage area 155 can be stored.

  First, the search process will be described with reference to FIG. The search process is a process of performing a search based on the search condition input as the search condition on the search screen and displaying the result. It is started when a request for displaying a search screen is received from the client 2.

  First, information for displaying a search screen is transmitted to the client 2 (S41). Here, in addition to the search screen form, the following information is transmitted. The common attribute name in the common attribute information storage area 1511 and the individual attribute name in the individual attribute template storage area 1512 are read out and used as a list in the attribute item column (list box) in the search condition display area 110 of the search screen. Further, the common attribute candidate value in the common attribute information storage area 1511 and the individual attribute candidate value in the individual attribute template storage area 1512 are read, and set as attribute values to be selected in the search conditions 1 to 6 corresponding to the attribute name. Is done. Note that “all attribute values” is also set as an option in the search conditions 1 to 6 fields.

  Next, an input reception process is performed (S42). In the client 2, when the search button 150 on the search screen is pressed, the search attribute item name and search attribute candidate value selected in the search condition display area 110 are transmitted to the file search server 1. The received search attribute item name and search attribute candidate value are stored in a predetermined storage area (not shown) of the RAM 11. Although not shown in the figure, if there is no response from the client 2 for a predetermined time (for example, 3 minutes), the connection with the client 2 is cut off, and the present process ends.

  Therefore, the number of search attribute items received is stored in the variable MAX (S43). Then, the initial value “1” is stored in the variable N (S44). Although not shown, the RAM 11 has a storage area for the variables MAX and N. And it has the Nth search attribute item (Nth search attribute item) of the received search attribute item among the deliverables memorize | stored in the deliverable attribute information storage area 153, The attribute value is the 1st. Records of deliverables that are N search attribute candidate values are extracted and stored in the search result storage area 157 (S45). For example, in the example of the search screen 102 shown in FIG. 19, the first search attribute item is “document type” and the first search attribute value is “specification”. Therefore, a deliverable whose common attribute item “document type” is “specification” is extracted. In the example of the deliverable attribute information storage area shown in FIG. 14 to FIG. 16, the first version of the deliverable name “111-XXa-specification” from the XX product Gr deliverable attribute information storage area 1531, 1st edition of “111-XXb-specification”, 1st edition of “222-XXa-specification”, 2nd edition of “222-XXa-specification”, “333-XX The first version of “a-specification” is extracted. From the product Gr product attribute information storage area 1532, the first version of the product name “111-xxxa-specification”, the second version of “111-xxxa-specification”, “222- The first version of “xxa-specification” and the first version of “222-xxxb-specification” are extracted. From the product Gr product attribute information storage area 1533, the first version of “111-ΔΔa-specification”, the first version of “333-ΔΔa-specification”, “333-ΔΔb” The second edition of “Specification” is extracted.

  Next, 1 is added to the variable N to be “2” (S46), and it is determined whether or not the variable N is larger than the variable MAX (S47). If the variable N is larger than the variable MAX, the extraction for all the search attribute items is completed, and the process proceeds to S49. In the example of the search screen 102 shown in FIG. 19, since the variable MAX = 3 and the variable N is “1”, it is determined that the variable N is not larger than the variable MAX (S47: NO). And it has the Nth search attribute item (Nth search attribute item) of the received search attribute item among the deliverables memorize | stored in the search result storage area 157, The attribute value is Nth search. A record of a deliverable that is an attribute candidate value is extracted and left in the search result storage area 157 (S48). In the example of the search screen 102 shown in FIG. 19, the second search attribute item is “series”, and the second search attribute values are “111” and “222”. Therefore, the first version of “111-XXa-specification”, the first version of “111-XXa-specification”, the first version of “222-XXa-specification”, “222- XXa-specification "second edition," 111-xxxa-specification "first edition," 111-xxxa-specification "second edition," 222-xxxa-specification " The first version of “Document”, the first version of “222-xxxb-specification”, and the first version of “111-ΔΔa-specification” are left in the search result storage area 157.

  Then, the process returns to S46, and 1 is added to the variable N to be “3” (S46). And the process of S46-S49 is repeatedly implemented until the variable N becomes larger than the variable MAX (S47: YES). In the example of the search screen 102 shown in FIG. 19, since the variable N = 3 is not larger than the variable MAX = 3 (S47: NO), it has the third search attribute item “product” and the attribute value is “ Records of deliverables that are “OO” or “XX” are extracted and left in the search result storage area 157 (S48). The first edition of “111-XXa-specification”, the first edition of “111-XXa-specification”, the first edition of “222-XXa-specification”, “222-XX” "a-specification" second edition, "111-xxxa-specification" first edition, "111-xxxa-specification" second edition, "222-xxxa-specification" The first version of “222-xxxb-specification” is extracted.

  Then, the process returns to S46, 1 is added to the variable N to be "4" (S46), and the variable MAX is larger than 3 (S47: YES), so that information for updating the search screen is the client 2 (S49), and the process ends. In S49, a virtual folder tree is created based on the search attribute item and its search attribute value, and is set as information to be displayed in the virtual folder tree display area 120. In the example of the search screen 102 shown in FIG. 19, the “specification” folder is displayed in the first hierarchy, and the “111” folder and the “222” folder are displayed in the second hierarchy. The “XX” folder and the “XX” folder are displayed below the “111” folder (third layer). The “XX” folder and the “XX” folder are also displayed below the “222” folder (third layer). Further, the product name and version of the record stored in the search result storage area 157 are stored corresponding to each folder of the virtual folder. In the example of the search screen 102 shown in FIG. 19, the first version of “111-XXa-specification”, “111-XXb-specification” is stored in the “specifications”-“111”-“XX” folder. The first version of “111-xxxa-specification”, “111-xxxa-specification” is placed in the “specification”-“111”-“XX” folder. Are associated with each other. The “specification”-“222”-“XX” folder is associated with the first version of “222-XXa-specification” and the second version of “222-XXa-specification”. The “specification”-“222”-“xxx” folder is associated with the first version of “222-xxxa-specification” and the first version of “222-xxxb-specification”. . Further, the file name of the file constituting the product is read from the product file information storage area 154, and is associated with the product name and the version. As described above, the product name and version associated with the folder and the file name associated with the product name and version are set as information to be displayed in the product tree display area 130. Further, the product name and version attribute items and attribute values associated with the folder are read from the search result storage area 157 and set as information to be displayed in the attribute information display area 140.

  In this way, based on the search condition instructed by the user, a product can be searched and extracted, and the result can be displayed. The search results are displayed as a tree of search conditions, so it is easy to find the desired product. In the attribute information display area 140, the attribute item name and its attribute value can be known. By specifying the attribute item and the attribute item value, the deliverable can be easily searched. Thus, for example, if you want to create a new file with reference to a file used in the past, or if you want to compare and review the same documents for multiple products (for example, estimates for products A, B, and C) Can find out.

  Next, the file acquisition process will be described with reference to FIG. In the search screen, when the search result is displayed in the virtual folder tree display area 120 and the product tree display area 130, the user selects a file by operating the mouse or keyboard and acquires an instruction (for example, double-click) When the ENTER key is pressed and the menu is displayed by right-clicking to select the “acquisition” menu, a file acquisition request is transmitted from the client 2 to the file search server 1. This file acquisition request includes the file name of the selected file, and the product name and version of the product to which the file belongs. Therefore, the file acquisition process is started when this file acquisition request is received.

  First, the file specified in the file acquisition request is acquired (S51). Specifically, the storage location of the specified product name, version, and file name is referenced from the product file information storage area 154. Then, the file is acquired from the storage location and stored in a predetermined storage area (not shown) of the RAM 11. Then, the acquired file is transmitted to the client 2.

  In this way, the user can perform a search using the attribute item on the search screen, and obtain a file to be obtained from the search result.

  The attribute information storage area 151 of the above embodiment corresponds to the “attribute information storage unit” of the present invention, the individual attribute template storage area 1512 corresponds to the “attribute template storage unit” of the present invention, and the template storage area 152. Corresponds to the “file deliverable template storage means” of the present invention, and the common attribute information storage area 1511 corresponds to the “common attribute information storage means” of the present invention. Further, in S42 of the search process (see FIG. 25), the search attribute item and the search attribute item value specified in the search condition display area 110 of the search screen (see FIGS. 3, 18 to 20) are acquired from the client 2. The CPU 10 that performs processing corresponds to “search condition acquisition means”, and extracts a product that satisfies the search attribute item and the search attribute item value in S45 to S48 from the product stored in the product attribute information storage area 153. The CPU 10 that performs the process corresponds to the “extraction process”. The CPU 10 that performs processing for transmitting to the client 2 information for displaying the search screen that displays the search results in the virtual folder tree display area 120 and the deliverable tree display area 130 in S49 corresponds to “search result display means”. .

  In S12 of the individual attribute template registration process (see FIG. 22), the CPU 10 that performs processing for acquiring the individual attribute item input in the individual attribute information field 222 of the individual attribute template registration screen 220 from the client 2 is “attribute template acquisition unit”. The CPU 10 that performs processing for acquiring the individual attribute candidate value input in the individual attribute information column 222 corresponds to “attribute candidate value acquisition means”. In the process of S32 of the product registration process (see FIG. 24) for acquiring the product template selected in the product template selection field 243 of the product registration screen 240 (see FIG. 7) and the selected product template The CPU 10 that performs the process of S34 that performs the process of acquiring the adopted individual attribute template corresponds to the “attribute template acquisition unit”. In S35, by adding a record to the deliverable attribute information storage area corresponding to the individual attribute template in the deliverable attribute information storage area 153, the CPU 10 that performs processing for storing the individual attribute items corresponding to the deliverables “ This corresponds to “first attribute information storage control means”. The CPU 10 that performs the process of acquiring the individual attribute information of the product registration screen 240 in S32 corresponds to “attribute value acquisition means”, and the process of storing the individual attribute value in the individual attribute column of the product attribute information storage area 153 in S35 The CPU 10 that performs the processing corresponds to “first attribute value storage control means”.

  A deliverable template registration process (see FIG. 23) for acquiring setting information specified in the setting information column of the common attribute information column 233 and the setting information column of the individual attribute information column 235 of the deliverable template registration screen 230 (see FIG. 6). The CPU 10 performing the process of S22 corresponds to “setting information acquisition means”. The CPU 10 that performs the process of S2 of the common attribute information registration process (see FIG. 21) that performs the process of acquiring the information input in the common attribute information column 211 of the common attribute information registration screen 210 (see FIG. 4) from the client 2. This corresponds to “common attribute candidate value acquisition means”. In S35, by adding a record in the product attribute information storage area 153, the CPU 10 that performs processing for storing the common attribute in association with the product corresponds to the “second attribute information storage control unit”. The CPU 10 that performs the process of acquiring the common attribute information of the product registration screen 240 in S32 corresponds to “common attribute value acquisition unit”, and stores the common attribute value in the common attribute column of the product attribute information storage area 153 in S35. The CPU 10 that performs processing corresponds to “second attribute value storage control means”.

  Note that the file search apparatus of the present invention is not limited to the above-described embodiment, and various changes can be made without departing from the scope of the present invention. In the above embodiment, the file search server 1 is a file search device, and the client 2 used by the user is another device connected to the file search server 1, but the file search server 1 and the client 2 are the same device. There may be. That is, instead of searching for a file used by a plurality of clients 2 via a network, it may be used to search for a file used in a single device. Further, the number of users using the file search apparatus may be one, not a plurality.

  In the above embodiment, the files constituting the deliverable are stored in the registered file storage area 155 of the HDD 15 of the file search server 1. However, the file may not be stored in the HDD 15 of the file search server 1 as long as the file search server 1 can write and read the file. In other words, it may be an external HDD or an HDD provided in another device connected to another file search server 1. Further, when storing a file in the registered file storage area 155, a physical folder similar to a virtual folder is created, and a file constituting the product is stored in a physical folder corresponding to the virtual folder to which the product belongs. You may make it do.

  Further, in the above embodiment, a product made up of files is handled while performing version management. However, the deliverable managed by the file search apparatus may not have version information. Moreover, you may manage not a product but a single file. In this case, the attribute information is not set for the product, but is set for the file. Therefore, the deliverable template of the above embodiment is treated as a file template. In the product file information storage area 154, the product name column and the version name column are unnecessary, and information indicating the storage location and the link destination file is stored for the file name. In the deliverable attribute information storage area 153, information for specifying a file is stored instead of the deliverable name and version name. Further, although the linked deliverable is set for the deliverable, the linked deliverable does not necessarily have to be set.

  Moreover, in the said embodiment, the common attribute item and the individual attribute item are provided about the attribute item. However, it is not necessary to separately provide common attribute items common to the entire system. In the above embodiment, the individual attribute template and the product template are used to simplify the setting of the attribute item. However, the individual attribute item may be set without using the template. Further, although attribute candidate values are set for attribute items and attribute values are selected from the attribute candidate values, the user may be allowed to input each time registration is performed without setting the attribute candidate values. In the above embodiment, the user authority is checked only when registering the common attribute item. However, when registering the individual attribute template, the authority is checked so that only authorized users can process it. Also good.

  In the above embodiment, when a search attribute item is selected in the search condition display area 110 of the search screen, only the attribute item name is displayed as a list in the list box. However, when this search attribute item is selected, it may be displayed so that it can be identified whether it is a common attribute item or an individual attribute item. A user who does not know what the common attribute item is can easily identify whether it is a common attribute item or an individual attribute item, which helps to specify a search condition. For individual attribute items, the individual attribute template to which the individual attribute item belongs may be displayed in an identifiable manner. Thereby, the confusion by using the individual attribute value of the same name in different individual attribute templates can be avoided.

  In the above embodiment, the tree display is performed in the virtual folder tree display area 120 and the product tree display area 130. However, the search attribute item and the search attribute value are displayed, and the search result product and the files constituting the product are displayed. The display need not be a tree display. For example, the search attribute item and the search attribute value may be displayed in a table format. The search result product and the file constituting the product may display only the product, and the file name may be displayed on another screen in response to a user operation such as a mouse click. Further, the display of the search attribute item and the search attribute value and the display of the search result product and the file constituting the product may not be displayed in different areas. For example, search attribute items and search attribute values are listed as headings, and the product names are displayed along with the headings.

  In the above embodiment, when an option is selected from the list in the list box as in the individual attribute template registration screen 220, the product template registration screen 230, and the product registration screen 240 (individual attribute template name field 221, Product template name field 231, individual attribute template selection field 234, product template selection field 243), when the information to be displayed is changed, the information to be changed is transmitted together when the screen is transmitted, The screen is updated on the client 2 side. For example, when an individual attribute template name is selected in the individual attribute template name field 221 of the individual attribute template registration screen 220, the individual attribute name and the individual attribute candidate value set corresponding to the selected individual attribute template name are displayed as individual attributes. The display of the individual attribute template registration screen 220 is updated so as to be displayed in the information column 222. However, the update of the screen may not be performed on the client 2 side but may be instructed by the file search server 1. In this case, the individual attribute template name selected in the individual attribute template name field 221 is transmitted from the client 2 to the file search server 1. In the file search server 1, the individual attribute information of the transmitted individual attribute template name is acquired from the individual attribute template storage area 1512 and set to be displayed in the individual attribute information column 222 of the individual attribute template registration screen 220. Return to client 2.

2 is a system configuration diagram showing a system configuration of a file search system 5. FIG. It is a schematic diagram which shows the relationship between the file managed by a file search system, and a deliverable. It is a schematic diagram of the search screen 100 which is an example of a search screen. It is a schematic diagram of the common attribute information registration screen. It is a schematic diagram of the individual attribute template registration screen. 6 is a schematic diagram of a deliverable template registration screen 230. FIG. It is a schematic diagram of the product registration screen. 2 is a schematic diagram showing an electrical configuration of a file search server 1. FIG. 2 is a schematic diagram showing a configuration of an HDD 15. FIG. 5 is a schematic diagram showing a configuration of a common attribute information storage area 1511. FIG. 5 is a schematic diagram showing a configuration of an individual attribute template storage area 1512. FIG. OO is a schematic diagram showing a configuration of a product Gr deliverable template storage area 1521. FIG. XX is a schematic diagram showing a configuration of a product Gr deliverable template storage area 1522. FIG. OO is a schematic diagram showing a configuration of a product Gr deliverable attribute information storage area 1531. FIG. XX is a schematic diagram showing a configuration of a product Gr deliverable attribute information storage area 1532. ΔΔ is a schematic diagram showing a configuration of a product Gr product attribute information storage area 1533. 5 is a schematic diagram showing a configuration of a deliverable file information storage area 154. FIG. It is a schematic diagram of the search screen 101 which is an example of a search screen. It is a schematic diagram of the search screen 102 which is an example of a search screen. It is a schematic diagram of the search screen 103 which is an example of a search screen. It is a flowchart of a common attribute information registration process. It is a flowchart of an individual attribute template registration process. It is a flowchart of a deliverable template registration process. It is a flowchart of a product registration process. It is a flowchart of a search process. It is a flowchart of a file acquisition process.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 File search server 2 Client 3 Network 5 File search system 100 Search screen 101 Search screen 102 Search screen 103 Search screen 110 Search condition display area 120 Virtual folder tree display area 130 Deliver tree display area 151 Attribute information storage area 152 Template storage area 153 Deliverable attribute information storage area 154 Deliverable file information storage area 155 Registered file storage area 157 Search result storage area 210 Common attribute information registration screen 220 Individual attribute template registration screen 230 Deliverable template registration screen 240 Deliverable registration screen 1511 Common attribute Information storage area 1512 Individual attribute template storage area

Claims (7)

An attribute information storage unit that stores attribute information associated with an attribute item and an attribute value that is a value of the attribute item in correspondence with a product that is a data file or a group of one or more data files;
A search condition acquisition means for acquiring the attribute item for searching the data file or the deliverable, and a condition of the attribute value of the attribute item;
Based on the attribute information stored in the attribute information storage means, the condition attribute item that is the attribute item acquired by the search condition acquisition means, and the condition value item that matches the condition of the attribute value An extraction means for extracting a data file or the deliverable;
The attribute value of the condition attribute item of the data file or the deliverable extracted by the extracting means is identifiable, and the data file or the deliverable having the same attribute value is displayed in an identifiable manner A file search apparatus comprising search result display means. The search condition acquisition means includes
Obtaining the condition attribute items with priorities obtained by adding priorities to a plurality of the attribute items;
The search result display means includes:
The condition attribute item with the highest priority is the first hierarchy, the priority is lowered and the condition attribute item is the lower hierarchy, and the attribute value of the condition attribute item of each hierarchy is the name of the node of each hierarchy 2. The identification information for identifying the data file or the deliverable that takes the attribute value that is an ancestor of the lowest layer node is displayed in a tree structure and displayed in a lowest layer node. The file search device described in 1. Attribute template acquisition means for acquiring a group of one or more attribute items as an attribute template;
Attribute candidate value acquisition means for acquiring, for each attribute item, an attribute candidate value that is a candidate for the value of the attribute item belonging to the attribute template acquired by the attribute template acquisition means;
Attribute template storage means for storing the attribute candidate value acquired by the attribute candidate value acquisition means corresponding to the attribute item of the attribute template acquired by the attribute template acquisition means;
Attribute template acquisition means for acquiring at least one of the attribute templates from the attribute template stored in the attribute template storage means;
First attribute item storage control means for attaching attribute items belonging to the acquired attribute template that is the attribute template acquired by the attribute template acquiring means to the attribute information storage means to be attached to the data file or the deliverable;
At least one of the attribute candidate values stored in the attribute template storage unit is used as an attribute value of the attribute item that is attached to the data file or the product by the first attribute item storage control unit. An attribute value acquisition means to acquire;
The attribute value acquired by the attribute value acquisition means is stored in the attribute information storage means as the attribute value of the attribute item that is attached to the data file or the deliverable by the first attribute item storage control means. The file search apparatus according to claim 1, further comprising: one attribute value storage control unit. Acquires setting information indicating at least one of whether the attribute value setting for the attribute item belonging to the acquired attribute template is essential, unnecessary, optional, or a fixed value. Setting information acquisition means;
File deliverable template storage means for storing a file deliverable template storing the setting information obtained by the setting information obtaining means for each of the attribute items belonging to the obtained attribute template;
The attribute template acquisition means
Obtaining the attribute template by obtaining at least one of the file deliverable templates stored in the file deliverable template storage means;
The first attribute item storage control means includes:
The attribute item belonging to the acquired attribute template of the file deliverable template is attached to the data file or the deliverable and stored in the attribute information storage means,
The first attribute value storage control means includes
4. The file search apparatus according to claim 3, wherein the attribute value is stored in the attribute information storage unit according to the setting information of the file deliverable template. Common attribute item acquisition means for acquiring common attribute items that are attribute items attached to all the files or the deliverables;
Common attribute candidate value acquisition means for acquiring, for each common attribute item, a common attribute candidate value that is one or more values that are candidates for the value of the common attribute item acquired by the common attribute item acquisition means;
A common attribute information storage unit that stores the common attribute candidate value acquired by the common attribute candidate value acquisition unit in correspondence with the common attribute item acquired by the common attribute item acquisition unit;
Second attribute information storage control means for storing the common attribute items stored in the common attribute information storage means in the attribute information storage means attached to the data file or the product;
At least one of the common attribute candidate values stored in the common attribute information storage unit is added to the data file or the product by the second attribute item storage control unit. A common attribute value acquisition means for acquiring a common attribute value;
The common attribute value acquired by the common attribute value acquisition unit is stored in the attribute information storage unit as the attribute value of the common attribute item that is attached to the data file or the deliverable by the second attribute item storage control unit. 5. The file search apparatus according to claim 1, further comprising second attribute value storage control means for storing. Common setting information acquisition means for acquiring setting information indicating at least one of whether the attribute value setting is essential, unnecessary, optional, or fixed value for the common attribute item With
The file deliverable template storage means includes:
Storing the setting information acquired by the common setting information acquisition means for each common attribute item;
The second attribute item storage control means,
The attribute item belonging to the acquired attribute template of the file deliverable template is attached to the data file or the deliverable and stored in the attribute information storage means,
The second attribute value storage control means includes
6. The file search apparatus according to claim 5, wherein the attribute value is stored in the attribute information storage unit according to the setting information of the file deliverable template.   A file search program for causing a computer to function as various processing means of the file search device according to claim 1.

Images