JP2011018192A - Data retrieval server - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide technology of efficiently extracting a desired file without specifying a directory structure.SOLUTION: A directory of accumulated files is determined based on attribute information included in meta information added to the files. The data retrieval server collects, based on a request for displaying the directory given from the outside, the meta information of files included in a directory thereof (S205, S206), and specifies lower directories based on the meta information (S208, S210). It is determined whether the file can be determined or not in reference to the meta information for each of the specified lower directories, and the lower directory that cannot determine the file is excluded from the specified lower directories (S212). The data retrieval server causes a display device to display the remaining directory as a display directory (S213).

Description

  The present invention relates to a method for searching target data from stored data, a computer that realizes such a method, and a search program technique.

  Conventionally, there is a technique for specifying a directory structure in a file system based on meta information added to data to be stored and storing the data to be stored in the file system.

  The data to be stored is stored in a specific part of the file system based on the information derived from the added meta information and the description order of the meta information.

  Non-Patent Document 1 describes a standard for describing such meta information. By using this technique, meta information can be added to data.

  In addition, if the music data, the directory divided for each album is stored in the directory divided for each artist, and a predetermined directory structure is defined so that the music data file is stored in the directory for each album. A technique for managing the above is described in Patent Document 1. In this technique, an artist name and an album name are specified from meta information of music data newly stored in a file system to specify a directory structure.

Japanese Patent Publication No. 2004-227285 Martin Nilsson. "ID3 tag version 2.4.0". [Online]. 1st November 2000. Search on May 26, 2009, Internet <URL: http://www.id3.org/id3v2.4.0-structure>

  In the technique described in Patent Document 1, when searching for already stored data from the file system, the stored directory structure is fixed. Therefore, if the fixed directory structure is not specified, the data is stored. If the directory structure cannot be found and the directory structure is specified incorrectly, the data may be lost.

  Accordingly, an object of the present invention is to provide a technique capable of extracting data to be stored efficiently without leaking without knowing the directory structure.

  In order to solve the above problem, the data search technique according to the present application determines the directory of the accumulated file based on the attribute information included in the meta information added to the file.

  In a preferred aspect of the present invention, the data search server collects meta information having attribute information corresponding to the directory requested to be displayed based on a directory display request given from the outside, and stores the meta information in the meta information. For each of the directory structure part that identifies the lower directory included in the directory requested to be displayed based on the directory structure part, and is included in the directory requested to be displayed with reference to the meta information. Directory read-ahead part that determines whether or not it is possible to narrow down files to be excluded, and excludes subordinate directories that were determined to be unable to narrow down files from the specified subdirectory, and directories that were not excluded by the directory prefetch part Is displayed on the display device as a display directory. And a directory display portion for.

  According to the present invention, a searcher can retrieve data to be stored without knowing the directory structure.

  In addition, since the directory where the file cannot be narrowed is excluded from the directories displayed at the time of the search, it becomes possible to efficiently search for the target file.

It is a block diagram of the data search system in one Embodiment of this invention. It is a table block diagram which shows the data structure of a type | mold table. It is a table block diagram which shows the data structure of a value table. It is a table block diagram which shows the data structure of a file attribute table. It is a table structure figure which shows the data structure of a directory structure table. It is a table block diagram which shows the data structure of a server structure table. It is a data structure figure which shows the data structure of a file and meta information. It is a block diagram which shows the outline of the hardware constitutions of a data search system. It is a flowchart which shows the processing flow of a root directory display process. It is a screen block diagram which shows an example of a directory display screen. It is a flowchart which shows the processing flow of a low-order directory display process. It is a screen block diagram which shows an example of a low-order directory display screen. It is a screen block diagram which shows an example of a low-order directory display screen. It is a screen block diagram which shows an example of a low-order directory display screen. It is a screen block diagram which shows an example of a low-order directory display screen. It is a flowchart which shows the processing flow of a high-order directory display process. It is a flowchart which shows the processing flow of a file information search process.

  FIG. 1 is a configuration diagram showing a data search system according to an embodiment of the present invention.

  The data search system in the present embodiment includes a data search server A100, a data search server B180, a client terminal 170, and a network 150 that connects these devices. The data search server A100 and the data search server B180, and the data search server A100 and the client terminal 170 can communicate via the network 150.

  In FIG. 1, only one client terminal 170 is shown, but a plurality of client terminals 170 may be provided.

  Specifically, the client terminal 170 is realized as a terminal device such as a client PC (personal computer), a workstation, various mobile phone terminals, a PDA (Personal Digital Assistant), or a television receiver.

  The client terminal 170 includes a control unit 171 including a file browsing unit 172, an input receiving unit 173, and a display unit 174, and a transmission / reception unit 175.

  The file browsing unit 172 instructs the display unit 174 to display information such as a directory structure and a file, and receives an instruction from the user for information such as the directory structure and the file displayed from the input receiving unit 173. Then, the file browsing unit 172 transmits information for displaying the directory to the designated data search server. If the instruction from the user is directed to a file, a file acquisition request is transmitted to the designated data search server.

  For example, the input receiving unit 173 receives an input operation performed by the user via an input device such as a keyboard or a mouse, and transmits information input from the input device to the control unit 171.

  The display unit 174 receives a display instruction from the control unit 171 and displays it on an output device such as a display.

  The transmission / reception unit 175 is connected to the network 150 and transmits information to other devices connected to the network 150 or receives information from other devices.

  The data search server A100 includes a storage unit 120, a control unit 130, and a transmission / reception unit 140, as shown in FIG. Although not shown, the data search server B 180 also includes a storage unit 120, a control unit 130, and a transmission / reception unit 140, similar to the data search server A 100.

  The storage unit 120 includes, as storage areas, an attribute type storage area 121 that stores the attribute type table 200, an attribute value storage area 122 that stores the attribute value table 300, and a file attribute storage area 123 that stores the file attribute table 400. A directory configuration storage area 124 for storing the directory configuration table 500, a server configuration storage area 125 for storing the server configuration table 600, and a storage target file storage area 126 for storing storage target files.

  Here, the meta information is information added to the file, as will be described later, and includes information indicating the attribute of the file. The attribute of the file includes a plurality of pairs of an attribute type that is a major classification and an attribute value that indicates a specific minor classification corresponding to the attribute type. That is, the attribute type and attribute value are information for classifying files, and have a relationship in which a plurality of attribute values are collected to form one attribute type. In addition, when handling a category that further subdivides an attribute value that is a subcategory, that is, when increasing the category hierarchically, an attribute value that is a subcategory is set as an attribute type, and a more specific category is used as an attribute value It may be set.

  A set of attribute types included in the meta information is stored in the attribute type table 200 in advance, and a set of values included in the meta information is stored in the attribute value table 300 in advance.

  FIG. 2 is a table configuration diagram illustrating a configuration example of the attribute type table 200 that stores a set of attribute types included in the meta information.

  The attribute type table 200 is a table that stores definitions of attribute types that are major classifications, and specifically includes a type identification number column 201 and an attribute type name column 202.

  The attribute type identification number column 201 stores an attribute type identification number that is information for identifying the attribute type of the attribute of the meta information. In the present embodiment, for example, information such as “T0” and “T1” is used as the attribute type identification number. The attribute type name column 202 stores attribute type names such as “work name” and “artist name”.

  FIG. 3 is a table configuration diagram illustrating a configuration example of the attribute value table 300 that stores a set of attribute values included in the meta information.

  The attribute value table 300 is a table that stores definitions of attribute values that are small classifications, and includes an attribute value identification number column 301 and an attribute value name column 302.

  The attribute value identification number column 301 stores an attribute value identification number that is information for identifying the attribute value of the meta information. In the present embodiment, for example, information such as “V0” and “V1” is used as the attribute value identification number. The attribute value column name 302 stores, for example, attribute values such as “Alternative” and “Classical” as information indicating the attribute value of the meta information.

  FIG. 4 is a table configuration diagram illustrating a configuration example of a file attribute table 400 that stores meta information for each file.

  The file attribute table 400 is a table that stores a correspondence between a file identifier and meta information from meta information added to a file.

  Specifically, the file attribute table 400 includes a file identifier column 401, an attribute type identification number column 402, and an attribute value identification number column 403.

  The file identifier column 401 stores a file identifier for identifying a file to be stored. Here, for example, information such as “A program”, “B movie”, and “C program” is used as the file identifier. The attribute type identification number column 402 stores an attribute type identification number for identifying the type of attribute assigned as meta information to the file to be stored. In the present embodiment, for example, “T1”, “T4”, or the like is used as the attribute type identification number. The attribute value identification number column 403 stores an attribute value identification number for identifying an attribute value assigned as meta information of a file that is data to be stored. In the present embodiment, for example, “V22”, “V3”, or the like is used as the attribute value identification number.

  FIG. 5 is a table configuration diagram illustrating a configuration example of a directory configuration table 500 that stores information for specifying a directory displayed by the file browsing unit 172 of the client terminal 170.

  In general, in order to specify the directory displayed by the file browsing unit 172 of the client terminal 170, it is necessary to specify the client terminal 170 and the file browsing unit 172 of the client terminal 170. In the present embodiment, a client identifier is used for specifying the client terminal 170, and a session identifier is used for specifying the file browsing unit 172. However, the present invention is not limited thereto, and other information may be used as long as the information can identify the client terminal 170 and the file browsing unit 172.

  The directory configuration table 500 includes a client identifier column 501, a session identifier column 502, a directory display condition column 503, and a directory display time column 504.

  The client identifier column 501 stores the client identifier as information for identifying the client terminal 170 that has requested the data search server A 100 to search for data. Here, an IP address assigned to the client terminal 170 such as “192.168.0.90” or “192.168.0.196” is used as the client identifier. The session identifier field 502 stores information for identifying the file browsing unit 172 operating on the client terminal 170 that has requested the data search server A100 to search for data. Here, session identifiers such as “SES94720” and “SES85720” are used. In the directory display condition column 503, a designation condition for specifying the displayed directory is stored for each combination of the client identifier and the session identifier. The directory display condition is information including at least one of an attribute type and an attribute value such as “T1, V22”, “T4, V3, T1, V22”. The directory display time column 504 stores information on the time when directory display is performed on the client terminal 170.

  FIG. 6 is a table configuration diagram showing a data structure of a server configuration table that holds a connection availability state with other data search servers connected via the network 150.

  The server configuration table 600 includes an identifier of another data search server that can be connected via the network 150, for example, a server identifier column 601 that stores information such as “server B” and “server C”, and the connection with the data search server. As information indicating the availability status, for example, a connection availability column 602 for storing information such as “OK” and “NG” is provided.

  FIG. 7 is a data structure diagram showing the data structure of the storage target file.

  The storage target file 800 includes a file identifier area 801, a content area 802 created as a series of playback units, and a set of one or a plurality of attribute type identification number areas 803 and attribute value identification number areas 804. Is done.

  The file identifier area 801 is an area for storing an identifier for identifying a storage target file, and is composed of text data. The content area 802 is an area for storing content that can be said to be the main body of a storage target file, and stores content data such as music and video, for example. The attribute type identification number area 803 is an area for storing the attribute type identification number of the storage target file. The attribute value identification number area 804 is an area for storing the attribute value identification number of the storage target file.

  Returning to FIG. 1, the control unit 130 includes a file attribute acquisition unit 131, a file attribute change unit 132, a display reception unit 133, a directory configuration unit 134, a directory display unit 135, a directory prefetch unit 136, and a server configuration. And a management unit 137.

  The file attribute acquisition unit 131 stores the storage target file instructed to be stored from the client terminal 170 in the storage target file storage area 126 of the storage unit 120. When the storage target file is stored in the storage target file storage area 126, the file attribute acquisition unit 131 acquires the meta information added to the storage target file and holds the file attribute table 400 held in the file attribute storage area 123. The value set in the file identifier field 801 in the file identifier field 401, the value set in the attribute type identification number field 803 in the attribute type identification number field 402, and the value identified in the attribute value identification number field 403 Each value set in the number area 804 is stored.

  The file attribute changing unit 132 changes the attribute values stored in the file identifier column 401, the attribute type identification number column 402, and the attribute value identification number column 403 of the file attribute table 400 with respect to the data stored in the storage unit 120. Are received, and each is changed to the accepted attribute value.

  When the client terminal 170 is requested to display the data stored in the storage unit 120, the display receiving unit 133 receives the display request as a display request, specifies the identifier and session identifier of the client terminal 170, and the directory configuration unit 134. Then, the processing is transferred to the directory display unit 135. Further, when receiving a file acquisition request specifying a file name from the client terminal 170, the display receiving unit 133 adds the received file name to the directory display condition displayed on the client terminal 170 and stores the file. Identify from the target file. The display reception unit 133 transmits the identified file to the client terminal 170 via the transmission / reception unit 140.

  The directory configuration unit 134 searches the storage unit 120 of its own server based on the display request received by the display reception unit 133, and requests another data search server B180 to perform the search. Then, the directory configuration unit 134 integrates these search results, identifies the directory configuration and files to be displayed, and instructs the directory display unit 135 to display them.

  Upon receiving a directory configuration or file display instruction from the directory configuration unit 134, the directory display unit 135 creates information for displaying them on a predetermined display screen, and transmits the information to the client terminal 170.

  The directory prefetching unit 136 determines whether the directory included in the directory configuration specified by the directory configuration unit 134 can further narrow down the file set specified by the directory configuration unit 134.

  The server configuration management unit 137 monitors whether or not other servers can be connected, detects that a server has been added or deleted, or has become unable to communicate, and stores it in the server configuration table 600.

  The transmission / reception unit 140 is connected to the network 150 and transmits / receives information to / from other devices that are also connected to the network 150.

  FIG. 8 is a block diagram showing an outline of the hardware configuration of the data search system. FIG. 8 shows only the client terminal 700 and the data search server A100 among the devices connected to the network 150.

  The data search server A100 includes a communication device 113, an arithmetic device 114, a main storage device 115, an auxiliary storage device 116, and a bus 117 that connects each of them.

  The communication device 113 is a device that communicates with other devices via a network such as the network 150. The arithmetic device 114 is an arithmetic device such as a CPU (Central Processing Unit). The main storage device 115 is a memory device such as a RAM (Random Access Memory). The auxiliary storage device 116 is a nonvolatile storage device such as a hard disk device or a flash memory.

  The client terminal 170 includes an input device 181, an output device 182, an arithmetic device 183, a main storage device 184, an auxiliary storage device 185, a communication device 186, and a bus 187 that connects them to each other.

  Here, the input device 181 is a device that receives input from a keyboard, a mouse, a touch pen, and other pointing devices, and the output device 182 is a device that displays information, such as a display. The arithmetic device 183 is an arithmetic device such as a CPU, the main storage device 184 is a memory device such as a RAM, the auxiliary storage device 185 is a non-volatile storage device such as a hard disk device or a flash memory, and the communication device 186 is a network. A device that communicates with other devices via a network such as 150.

  The communication device 186 of the client terminal 170 can communicate with the communication device 113 of the data search server A 100 via the network 150.

  Here, the network 150 is a communication network such as a LAN or a wireless LAN, but may be a public network such as the Internet or a public wireless LAN, or other network such as a cable TV network or a mobile phone network, or It may be a power line network or the like.

  Each functional unit included in the control unit 130 of the data search server A100, that is, a file attribute acquisition unit 131, a file attribute change unit 132, a display reception unit 133, a directory configuration unit 134, a directory display unit 135, a directory prefetching unit 136, and The server configuration management unit 137 is realized by a program stored in the main storage device 115 or the auxiliary storage device 116. Specifically, this program is loaded from the main storage device 115 or the auxiliary storage device 116 onto the main storage device 115, and the arithmetic device 114 executes it to realize the functions of these functional units.

  The storage unit 120 of the data search server A 100 is realized by the main storage device 115 or the auxiliary storage device 116, and the transmission / reception unit 140 is realized by the communication device 113.

  Each functional unit included in the control unit 171 of the client terminal 170, that is, the file browsing unit 172, the input receiving unit 173, and the display unit 174 is the main storage device 184 or the auxiliary storage similarly to the functional units of the data search server A. This is realized by a program stored in the device 185. Specifically, this program is loaded onto the main storage device 184 for execution, and the functions of these functional units are realized by the arithmetic device 183 executing this program.

  The transmission / reception unit 175 of the client terminal 170 is realized by the communication device 186.

  Hereinafter, the flow of processing relating to data search in the present embodiment will be described with reference to the drawings.

  FIG. 9 is a flowchart showing the root directory display process.

  The root directory display process is performed when a root directory display request is received from the client terminal 170. A request for displaying a root directory from the client terminal 170 is received by the display receiving unit 133.

  Specifically, the root directory display request includes a client identifier, a session identifier, and root directory display request information. Information such as the IP address of the client terminal 170 is stored in the client identifier, and a session identifier that identifies an instance of the directory browser program of the client terminal 170 is stored in the session identifier (step S101).

  When receiving the root directory display request, the display receiving unit 133 acquires a client identifier and a session identifier from the received root directory display request, and passes these identifiers to the directory configuration unit (step S102).

  The directory configuration unit 134 requests other data search servers determined to be valid as described later to transmit file information. In addition, the directory configuration unit 134 stores the client identifier received from the display reception unit 133 in the client identifier column 501 and the session identifier in the session identifier column 502 for the directory configuration table 500.

  Specifically, the directory configuration unit 134 refers to the server configuration table 600 and identifies an entry whose connection permission / inhibition column 602 is “OK”. Then, it is determined that the data search server identified by the identifier stored in the server identifier column 601 of the specified entry is valid. The directory configuration unit 134 requests the data search server determined to be valid to search for the root directory, that is, instructs the data search server to search without specifying directory display conditions (step S103).

  Next, the directory configuration unit 134 receives information related to files held by the server from the data search server that requested the root directory search in step S103. Specifically, the directory configuration unit 134 receives the file identifier and the attribute type identification number and attribute value identification number associated with the file from all the data search servers that have requested the root directory search (step S104). .

  In addition, the directory configuration unit 134 acquires information on the file of the local server (local) by the file information search process. Specifically, the file identifier stored in the file identifier column 401, the attribute type identification number stored in the attribute type identification number column 402, and the attribute value identification number column 403 are stored from the file attribute table 400 of the own server. All the attribute value identification numbers are acquired (step S105).

  Thereafter, the directory configuration unit 134 collects the information on the local file acquired in step S105 and the information on the file of the other data search server received in step S104, and eliminates duplication of the attribute type identification number. Then, the directory configuration unit 134 searches the attribute type table 200 for each of the attribute type identification numbers from which duplication is eliminated, and the attribute type corresponding to the attribute number whose attribute type identification number matches the value in the attribute type identification number column 201. The value in the type name column 202 is stored as a display directory.

  Specifically, the directory configuration unit 134 extracts and sorts all attribute type identification numbers from the information regarding the local file acquired in step S105, and creates a list from which duplicate attribute type identification numbers are excluded. Then, the directory configuration unit 134 extracts attribute type identification numbers that are not included in the created list from the information related to files from the other data search servers received in step S104 and adds them to the list. Further, each attribute type identification number included in the list is compared with the value of the attribute type identification number column 201 of the attribute type table 200, and the value of the attribute type name column 202 corresponding to the matching attribute type identification number is listed. And stored as display directory information (step S106).

  The directory configuration unit 134 calculates the number of file identifiers from the information regarding the local file acquired in step S105. Then, the directory configuration unit 134 calculates the number of file identifiers from the information regarding the files received from the other data search servers received in step S104, and stores it as the total number of files in addition to the calculated number of local file identifiers. (Step S107).

  Next, the directory configuration unit 134 lists the file identifiers of all files as file names and stores them as display files. Specifically, the directory configuration unit 134 extracts all the file identifiers from the information regarding the local file acquired in step S105, and creates a list of file identifiers. Further, the directory configuration unit 134 stores the list as display file information in addition to the created list of file identifiers extracted from the information related to files from other data search servers received in step S104 (step S108).

  The directory prefetch unit 135 excludes the attribute type and attribute value pairs that are commonly held by all the display files acquired in step S108 in the display directory acquired by the directory configuration unit 134 in step S106. Specifically, for all the attribute types included in the display directory acquired in step S106, a set of attribute values included in the attribute type is created. Then, for each pair of attribute type and attribute value, information on a file including the pair as attribute information is searched from information on the display file. The number of files obtained as a result is compared with the number of files obtained in step S107 to check whether the number of files has decreased. If the number of files has not decreased, the attribute value is excluded from the set of attribute values for the attribute type. As a result of eliminating the attribute values in this way, the attribute type in which the attribute value set is an empty set is excluded from the display target directory. As a result, only directories that can further narrow down the file set are left in the display directory (step S109).

  Thereafter, the directory prefetch unit 135 instructs the directory display unit 135 to display the display directory checked in step S109, the total number of files stored in step S107, and the display file stored in step S108. In response to this instruction, the directory display unit 135 configures a root directory display screen 700 as shown in FIG. 10 and displays it on the client terminal 170.

  When configuring the root directory display screen 700, the directory display unit 135 displays the display directory (attribute type name) stored in step S106 as a directory name as a directory icon 705, and displays the total number of files stored in step S107. The file number 704 is displayed, and the display file stored in step S108 is displayed as a file icon 706 as a file name (step S110).

  FIG. 10 is a screen configuration diagram showing an example of a directory display screen displaying a root directory.

  The directory display screen 700 includes a window 701, a scroll bar 702, a display directory name 703, the number of files 704, a directory icon 705, and a file icon 706.

  The scroll bar 702 receives a scroll operation and displays a directory icon 705 and a file icon 706 that cannot be displayed at one time by the window 701.

  The directory icon 705 is selected by a selection operation on the client terminal 170 by the user when displaying files and directories included in the directory specified by the directory name. This selection operation is received by the input receiving unit 173 and notified to the file browsing unit 172. For example, when receiving an instruction for selection such as double-clicking, the input receiving unit 173 designates the directory name of the directory icon 705 that has been double-clicked as the directory name of the destination directory and issues a request to display the destination directory as a file. Notify the browsing unit 172.

  The file icon 706 is selected by a selection operation on the client terminal 170 by the user when the file specified by the file file name is acquired. This selection operation is received by the input receiving unit 173 and notified to the file browsing unit 172. For example, when receiving an instruction to open a file by double-clicking or the like, the input receiving unit 173 designates the file name of the file icon 706 that has been double-clicked as the file name of the file to be acquired, and requests to acquire the file. The file browsing unit 172 is notified.

  When the file browsing unit 172 receives a request to display a destination directory or a request to acquire a file, the file browsing unit 172 requests the data search server A to display a destination directory display, or Send file acquisition request.

  As described above, the directory display screen 700 is a screen for displaying files and directories under the root directory, and is also a screen for accepting an instruction to move between directories and an instruction to acquire a file.

  FIG. 11 is a flowchart showing the process flow of the lower directory display process.

  In the lower directory display process, first, the display receiving unit 133 receives a move destination directory display request. The destination directory display request includes a client identifier, a session identifier, and a destination directory name. Information such as the IP address of the client terminal 170 is stored in the client identifier, and a session identifier for identifying the file browsing unit 172 of the client terminal 170 is stored in the session identifier (step S201).

  When receiving the destination directory display request, the display receiving unit 133 acquires a client identifier, a session identifier, and a destination directory name from the received destination directory display request. Then, the acquired information is sent to the directory configuration unit 134 (step S202).

  The directory configuration unit 134 refers to the directory configuration table 500 and searches for a record in which the client identifier field 501 matches the received client identifier, and the session identifier field 502 matches the received session identifier, and the directory display condition The value in the field 503 (directory display condition) is acquired. Then, the directory configuration unit 134 adds the attribute type identification number or attribute value identification number corresponding to the destination directory name received from the display reception unit 133 to the acquired directory display condition, and sets the directory as a new directory display condition. The information is stored in the display condition column 503 (step S203).

  Next, the directory configuration unit 134 specifies another valid data search server in the same manner as in step S103, and specifies the new directory display condition stored in step S203 for the specified data search server as a file. A request is made to send information (step S204).

  The directory configuration unit 134 receives information about the file from the other data search server requested in step S204. The received information regarding the file includes a file identifier and an attribute type identification number and an attribute value identification number associated with the file (step S205).

  In addition, the directory configuration unit 134 acquires, by file information search processing, information that matches the directory display conditions among the information related to the file of the local server (local). Specifically, the directory configuration unit 134 searches the file attribute table 400 of its own server for records including all of the attribute type identification number and attribute value identification number specified in the directory display condition regardless of the designation order, The file identifier stored in the file identifier column 401 of the record obtained as a result of the search, the attribute type identification number stored in the attribute type identification number column 402, and the attribute value identification number stored in the attribute value identification number column 403 All the information is acquired (step S206).

  Then, the directory configuration unit 134 determines whether or not the destination directory name is a name that specifies an attribute type. Specifically, the directory configuration unit 134 searches the attribute type name column 202 of the attribute type table 200 using the destination directory name as a key, and if there is a matching attribute type name, the destination directory name specifies the attribute type. If not, it is determined that the name is not the name that designates the attribute type (step S207).

  If the destination directory name is a name that designates an attribute type (the determination result in step S207 is “Yes”), the directory configuration unit 134 receives information on the local file acquired in step S206 and the information received in step S205. The information on the files from the data search server is collected and stored as a display directory by eliminating duplication of attribute value identification numbers. Specifically, the directory configuration unit 134 extracts and sorts all attribute value identification numbers from the information regarding the local file acquired in step S206, and creates a list from which duplicate numbers are excluded. Then, the directory configuration unit 134 extracts attribute value identification numbers not included in the created list from the information regarding the file from the other data search server received in step S205, and adds the list to the display directory information. Remember as. Thereafter, the processing proceeds to step S211 described later (step S208).

  On the other hand, if the destination directory name is not a name designating the attribute type (the determination result in step S207 is “No”), the directory configuration unit 134 receives the information on the local file acquired in step S206 and the information in step S205. The information on the files from the other data search servers is collected and stored as a display file by eliminating duplication of file identifiers. Specifically, the directory configuration unit 134 extracts and sorts all the file identifiers from the information about the local file acquired in step S206, and creates a list that excludes duplicate file identifiers. Then, the directory configuration unit 134 extracts the file identifier not included in the created list from the information regarding the file from the other data search server received in step S205, adds the file identifier to the list, and uses the list as display file information. Store (step S209).

  Subsequently, the directory configuration unit 134 collects the information on the local file acquired in step S206 and the information on the file from the other data search server received in step S205, and eliminates duplication of the attribute type identification number. The attribute type identification number after de-duplication is excluded from the directory display condition and stored as a display directory.

  Specifically, the directory configuration unit 134 extracts and sorts all the attribute type identification numbers from the information on the local file acquired in step S206, and creates a list that excludes duplicate attribute type identification numbers. Then, the directory configuration unit 134 extracts attribute type identification numbers that are not included in the created list from the information related to files from the other data search servers received in step S205 and adds them to the list. Then, the directory configuration unit 134 refers to the directory configuration table 500 and searches for a record in which the client identifier column 501 matches the client identifier acquired in step S202 and the session identifier column 502 matches the session identifier. The value of the display condition column 503 is acquired, the attribute type identification number included in the directory display condition column 503 is deleted from the created list, and the list is stored as display directory information (step S210).

  After the processing of step S208 or S210, the directory configuration unit 134 calculates the number of file identifiers while excluding duplicate file identifiers from the information regarding the local files acquired in steps S205 and S206. Then, the number of obtained file identifiers is stored as the number of files to be displayed. (Step S211).

  The directory prefetching unit 135 excludes a directory that cannot further narrow down the file set from the display directory acquired by the directory configuration unit 134 in step S208 or S210.

  Specifically, if the destination directory is attribute type designation in step S207, the directory prefetching unit 135 acquires information about the file with the directory display condition before adding the destination directory name in step S203, and For each of the display directories acquired in step S208, it is checked whether the destination directory (attribute type) and display directory (attribute value) pair is included in all of the information related to the file acquired here. . When this pair is included in the information regarding all files, the display directory is excluded.

  If the destination directory is not specified as an attribute type in step S207, the directory prefetching unit 135 sets a set of attribute values included in the attribute type for all attribute types included in the display directory acquired in step S210. Create Then, for each pair of attribute type and attribute value, information relating to the file including the pair as attribute information is searched from the information relating to the file regarding the display file acquired in S209. The directory prefetching unit 135 compares the number of files obtained as a result with the number of files obtained in step S211, and checks whether the number of files has decreased. If the number of files has not decreased, the attribute value is excluded from the set of attribute values for that attribute type. As a result of eliminating the attribute values in this way, the directory prefetching unit 135 excludes the attribute type in which the attribute value set is an empty set from the display target directory.

  As a result of these processes, only directories that can further narrow down the file set are left in the display directory. (Step S212).

  Then, the directory configuration unit 134 instructs the directory display unit 135 to display the display directory stored in step S208 or step S210, the total number of files calculated in step S211 and the display file stored in step S209. The directory display unit 135 configures the lower directory display screen shown in FIGS. 12 to 15 and displays it on the client terminal 170. At that time, the directory display unit 135 stores the processing time in the directory display time column 504 of the directory configuration table 500 (step S213).

  FIG. 12 is a screen configuration diagram showing an example of a lower directory display screen. The lower directory display screen shown in FIG. 12 is a screen that is displayed when it is determined in step S207 that the destination directory is a name that designates an attribute type.

  When the directory display screen shown in FIG. 12 is configured, the directory display unit 135 displays the display directory stored in step S208 as the directory icon 705. The lower display screen is configured to display the number of files calculated in step S211 as the number of files 704 and the information stored in the directory display condition field 503 as the directory name 703, respectively.

  FIG. 13 is a screen configuration diagram illustrating another example of the lower directory display screen. The lower directory display screen shown in FIG. 13 is a screen that is displayed when it is determined in step S207 that the destination directory is not a name that designates an attribute type. Such a lower directory display screen is displayed, for example, when the directory display screen shown in FIG. 12 is designated to move to the “Jazz” directory.

  When the lower directory display screen shown in FIG. 13 is configured, the directory display unit 135 displays the display file stored in step S209 as the file icon 706, and displays the display directory stored in step S210 as the directory icon 705. Configure the lower directory display screen to Further, as the number of files 704, the number of files calculated in step S211 is displayed.

  FIG. 14 is a screen configuration diagram showing still another example of the lower directory display screen. The directory display screen shown in FIG. 14 is the same as the directory display screen shown in FIG. 12, and is displayed when it is designated to move to the “Artist name” directory on the directory display screen shown in FIG. This is the screen to be displayed.

  FIG. 15 is a screen configuration diagram showing still another example of the lower directory display screen. The directory display screen shown in FIG. 15 is the same as the directory display screen shown in FIG. 13, and is displayed when the directory display screen shown in FIG. 14 is designated to move to the “Artist B” directory. It is.

  FIG. 16 is a flowchart showing the process flow of the upper directory display process.

  In the upper directory display process, first, the display receiving unit 133 receives a request to display the upper directory. The request to display the upper directory includes a client identifier and a session identifier. Information such as the IP address of the client terminal 170 is stored in the client identifier, and a session identifier for identifying an instance of the directory browser program of the client terminal 170 is stored in the session identifier. (Step S301).

  When receiving the request to display the upper directory, the display receiving unit 133 acquires the client identifier and the session identifier from the request to display the upper directory received in step S301, and passes them to the directory configuration unit (step S302). ).

  The directory configuration unit 134 obtains the directory display condition used when displaying a screen one higher than the screen displayed by the screen determined based on the client identifier and the session identifier acquired in step S302. Specifically, the directory configuration unit 134 refers to the directory configuration table 500, the client identifier in the client identifier column 501 matches the client identifier acquired in step S302, and the session identifier in the session identifier column 502 matches in step S302. Search for information that matches the acquired session identifier. The directory configuration unit 134 acquires the value of the directory display condition column 503 and the value of the directory display time column 504 among the information that matches as a result of the search.

  After that, the directory configuration unit 134 deletes the last directory name (attribute type identifier) from the acquired value of the directory display condition field 503 as a new directory display condition, and uses this new directory display condition as the directory display condition. It is stored in the column 503 (step S303).

  Next, the directory configuration unit 134 transmits the new directory display condition stored in the directory display condition field 503 in step S303 to another valid data search server and requests to transmit file information (step S303). Step S304).

  Thereafter, the directory configuration unit 134 receives information about the file from the other data search server requested in step S304. The information regarding the file from the other data search server received here includes the file identifier and the attribute type identification number and value identification number associated with the file (step S305).

  In addition, the directory configuration unit 134 acquires, by file information search processing, information that matches the directory display conditions among the information related to the file of the local server (local). Specifically, the directory configuration unit 134 searches the file attribute table 400 of its own server for records including all of the attribute type identification number and attribute value identification number specified in the directory display condition, regardless of the designation order. The information stored in the file identifier column 401, the information stored in the attribute type identification number column 402, and the information stored in the attribute value identification number column 403 are acquired (step S306). .

  Next, the directory configuration unit 134 compares the information regarding the file received in step S305 with the information regarding the file from the other data search server used when the upper directory is displayed, and determines whether there is a difference. Determine whether. In addition, the directory configuration unit 134 compares the information acquired in step S306 with the information about the file used when the upper directory is displayed, and determines whether there is a difference. As a result of the determination, if there is no difference in any information (the determination result is “No”), the directory configuration unit 134 advances the process to step S313 described later (step S307).

  As a result of the determination in step 307, if any of the information is different (the determination result in step S307 is “Yes”), the directory configuration unit 134 specifies that the destination directory name (upper directory name) specifies the attribute type. It is determined whether or not. Specifically, the directory configuration unit 134 searches the attribute type name column 202 of the attribute type table 200 using the destination directory name as a key, and if there is a matching attribute type name, the destination directory name specifies the attribute type. It is determined that it is a name, and if not, it is determined that the name is not a name that designates an attribute type (step S308).

  If the destination directory name is a name that designates an attribute type (the determination result in step S308 is “Yes”), the directory configuration unit 134 receives information on the local file acquired in step S306 and the valid information received in step S305. Information about files from various servers is collected, and duplication of attribute value identification numbers is eliminated and stored as a display directory. Specifically, the directory configuration unit 134 extracts and sorts the attribute value identification numbers from the information regarding the local file acquired in step S306, and creates a list that excludes duplicate attribute value identification numbers. Then, the directory configuration unit 134 extracts the attribute value identification number not included in the created list from the information regarding the file from the other data search server received in step S305, and adds the list to the display directory. Store as information. Then, the directory structure part 134 advances a process to step S313 mentioned later. (Step S309).

  When the destination directory name is not a name that designates the attribute type (the determination result in step S308 is “No”), the directory configuration unit 134 receives information on the local file acquired in step S306 and the other information received in step S305. The information about the files from the data retrieval server is collected and stored as a display file by eliminating duplication of file identifiers. Specifically, the directory configuration unit 134 extracts and sorts all the file identifiers from the information about the local file acquired in step S306, and creates a list that excludes duplicate file identifiers. Then, the directory configuration unit 134 extracts the file identifier not included in the created list from the information regarding the file from the valid server received in step S305, adds the file identifier to the list, and stores the list as display file information. (Step S311).

  Subsequently, the directory configuration unit 134 combines the information on the local file acquired in step S306 and the information on the file from the other data search server received in step S305 to eliminate duplication of the attribute type identification number, Items included in the directory display condition are excluded from the attribute type identification numbers from which duplication has been eliminated, and stored as a display directory. Specifically, the directory configuration unit 134 extracts and sorts all the attribute type identification numbers from the information regarding the local file acquired in step S306, and creates a list excluding duplicate attribute type identification numbers. Then, the directory configuration unit 134 extracts attribute type identification numbers that are not included in the created list from the information about the files received from other data search servers received in step S305 and adds them to the list (step S312).

  Next, the directory configuration unit 134 calculates the number of file identifiers by excluding those with duplicate file identifiers from the information regarding the files acquired in steps S306 and S307. Then, the obtained number of file identifiers is stored as the number of files to be displayed (step S312).

  The directory prefetch unit 135 excludes a directory in which a file set cannot be narrowed down from the display directory acquired by the directory configuration unit 134 in steps S309 and S311.

  Specifically, if the destination directory is attribute type designation in step S308, the directory prefetching unit 135 displays information on the files included in the directory higher than the destination directory, that is, the directory display updated in step S303. Information on the file is acquired under the directory display condition in which the last directory name is further deleted from the conditions, and the destination directory (attribute type) and display directory (attribute value) pair for each of the display directories acquired in step S310. Is included in all of the information on the file acquired here. When this pair is included in the information regarding all files, the display directory is excluded.

  If the destination directory is not specified as an attribute type in step S308, the directory prefetching unit 135 sets a set of attribute values included in the attribute type for all attribute types included in the display directory acquired in step S311. Create Then, for each pair of attribute type and attribute value, information relating to the file including the pair as attribute information is searched from the information relating to the file regarding the display file acquired in S310. The directory prefetching unit 135 compares the number of files obtained as a result with the number of files obtained in step S312, and checks whether the number of files has decreased. If the number of files has not decreased, the attribute value is excluded from the set of attribute values for that attribute type. As a result of eliminating the attribute values in this way, the directory prefetching unit 135 excludes the attribute type in which the attribute value set is an empty set from the display target directory (step S313).

  Next, the directory configuration unit 134 displays the display directory when the display directory or the upper directory stored in step S313 is displayed, the total number of files calculated in step S312 or the total number of files when the upper directory is displayed, The directory display unit 135 is instructed to display the display file stored in S310 or the display file when the upper directory is displayed. The directory display unit 135 configures a lower directory display screen as shown in FIGS. 12 to 15 and displays it on the client terminal 170. At that time, the directory display unit 135 stores the processing time in the directory display time column 504 of the directory configuration table 500 (step S314).

  In this way, in the upper directory display processing, the directory display once displayed is reused. However, if the configuration of the data search server is changed or the searched data is changed, the search is performed again. . In this way, the latest state of the directory can be displayed.

  When searching for files with meta information that satisfies the conditions specified by the user through the root directory display processing, lower directory display processing, and upper directory display processing described above, the search is narrowed down regardless of the order. This makes it possible to prevent losing data without searching for a file.

  FIG. 17 is a flowchart showing a process flow of the file information search process performed in each process described above. This process is also performed in order to transmit the requested information in another data search server that has been requested to transmit information about the file.

  In the file information search process, the directory configuration unit 134 receives directory display conditions (step S401).

  The directory configuration unit 134 acquires information about all files stored in the file attribute table 400 (step S402).

  Next, the directory configuration unit 134 divides and lists the directory display conditions received in step S401. Specifically, the directory structure unit 134 divides the directory display condition into predetermined delimiter symbols such as commas, and stores the divided values as a serially accessible list structure (step S403).

  Subsequently, the directory configuration unit 134 acquires the first value of the list created in step S403 and stores it in the variable A (step S404).

  The directory configuration unit 134 determines whether or not the value stored in the variable A is an attribute type identification number. Specifically, the directory configuration unit 134 searches the information in the attribute type identification number column 201 of the attribute type table 200 using the variable A as a key, and determines that the attribute type identification number is an attribute type identification number if a matching attribute type identification number exists. Otherwise, it is determined that it is not an attribute type identification number. If the value of the variable A is not the attribute type identification number (the determination result is “No”), the directory configuration unit 134 proceeds to step S410 to be described later (step S405).

  If the value of the variable A is the attribute type identification number (the determination result in step S405 is “Yes”), the directory configuration unit 134 determines that the attribute type identification number is the variable A from the information about all the files acquired in step S402. The file information that matches the value is selected (step S406).

  Next, the directory configuration unit 134 acquires the next value of the list created in step S403 and stores it in the variable B (step S407).

  Subsequently, the directory configuration unit 134 determines whether or not the value stored in the variable B is an attribute value identification number. Specifically, the directory configuration unit 134 searches for information in the attribute value identification number column 301 of the attribute value table 200 using the variable B as a key. If there is an attribute value identification number that matches the attribute value identification number column 301, it is determined that the value of the variable B is an attribute value identification number. Otherwise, it is determined that the value of the variable B is not an attribute value identification number. . If the value of the variable B is not the attribute value identification number (the determination result is “No”), the directory configuration unit 134 proceeds to step S410 to be described later (step S408).

  If the value of the variable B is a value identification number (the determination result in step S408 is “Yes”), the directory configuration unit 134 matches the value identification number with the value of the variable B from the information about the file selected in step S406. A file to be selected is selected (step S409).

  Then, the directory structure unit 134 acquires the next value of the list created in step S403, stores it in the variable A, and returns to the process of step S405 (step S410). In step S406, which is performed thereafter, a file is selected based on information about the file selected in step S409.

  When the determination result in step S405 or step S408 is “No”, the directory configuration unit 134 sets the file identifier, the attribute type identification number, the attribute value identification number, and the like for all the files acquired in step S402. Is sent to the process requester as information about the file. Alternatively, the directory configuration unit 134 applies a file identifier, an attribute type identification number, and an attribute value identification number to the file selected by the processing in steps S406 and S409 from all the files acquired in step S402. Information is transmitted to the requester of the process, and the process ends (step S410).

  With this file information search process, when searching for a file having meta information that satisfies a specified condition, data can be narrowed down and searched regardless of the order.

  Although not shown, the server configuration management unit 137 performs service life / death determination on other data search servers connected to the network 150 every predetermined period (for example, 10 seconds), and the service is provided. In other words, a data search server that cannot perform data search is detected, and the connectability column 602 of the server configuration table 600 is stored as “NG”. At this time, the data search server that can provide the service is determined to be a valid data search server, and “OK” is set in the connectability column 602 of the server configuration table 600.

  In the present embodiment, the server for which the server configuration management unit 137 performs the service life / death determination is a data search server stored in the server identifier field 601 of the server configuration table 600. This data search server is registered in advance. Alternatively, the server configuration management unit may be implemented for a data search server whose existence has been confirmed using a method such as broadcast prior to life / death determination.

  In addition, the file attribute changing unit 132 receives the information regarding the change of the file attribute information transmitted from the file browsing unit 172 installed in the control unit 171 of the client terminal 170, and the file identifier column 401 of the file attribute table 400, The values in the attribute type identification number column 402 and the attribute value identification number column 403 are changed. Specifically, when the information regarding the change of the file attribute information is to add an attribute type identification number and an attribute value identification number to a file identified by a certain file identifier, the file attribute change unit 132 Stores the attribute type identification number in the attribute type identification number column 402 and the attribute value identification number in the attribute value identification number column 403 for storing the file information that matches the file identifier.

  Although the present invention has been specifically described above based on the embodiment, the present invention is not limited to this, and various modifications can be made without departing from the scope of the present invention.

  For example, the directory display unit 135 is mounted on the control unit 130 of the data search server 100 in the above-described embodiment, but is not limited thereto, and may be mounted on the control unit 171 of the client terminal 170, for example. In this case, the directory configuration unit 134 instructs the directory display unit 135 existing on the client terminal 170 via the network 150 when displaying the results of step S109, step S212, step S314, and the like. For example, various data sharing modes can be provided by instructing according to a file sharing protocol such as NFS (Network File System), CIFS (Common Internet File System), or SMB (Server Message Block), which shares files over a network. Can be realized.

  Further, other functional units may be mounted on the client terminal 170 or may be mounted on both the client terminal 170 and the data search server 100.

  In addition, the data search server 100 may include a file browsing unit similar to the client terminal 170. By doing in this way, it becomes possible to operate the data search server 100 also as the client terminal 170, and the freedom degree of an apparatus structure can be increased.

  In the above data search system, the data search server B180 has the same configuration as the data search server A100. However, the present invention is not limited to this, and the above-described root directory display process, lower directory display process, and upper directory display Among the processes and the file information search process, at least the file method search process may be performed. With this configuration, the data search server A100 functions as a server that provides a search service to the client terminal 170, and the data search server B180 performs a search in accordance with a search instruction from the data search server A100 and provides data. As a system can be constructed.

  Further, as described above, the attribute value is stored in the attribute value name column 302 of the attribute value table 300 and is stored in the attribute type name column 202 of the attribute type table 200. 11 is displayed, the directory structure unit 134 determines that the destination directory is the attribute type in step S207 of the lower directory display process of FIG. 11, and the screen shown in FIG. 12 is displayed. Will be. As a result, it can be displayed as a directory having a deeper hierarchy. That is, it is possible to realize not only two-level classification by major classification and small classification, but also multi-level classification.

  Note that the data search system 1 described above is not only a transaction target as a system, but can also be a transaction target for each device or for each program component that realizes the operation of the device.

100: data search server A, 120: storage unit, 121: type storage area, 122: value storage area, 123: file attribute storage area, 124: directory configuration storage area, 125: server configuration storage area, 130: control unit, 131: File attribute acquisition unit, 132: File attribute change unit, 133: Display reception unit, 134: Directory configuration unit, 135: Directory display unit, 136: Directory prefetching unit, 137: Server configuration management unit, 140: Transmission / reception unit , 150: network, 170: client terminal, 171: control unit, 180: data search server B, 200: type table, 300: value table, 400: file attribute table, 500: directory configuration table, 600: server configuration table

Claims (4)

A directory of stored files is used in a file system determined based on attribute information included in meta information added to a file, and is a data search server for searching for the stored file,
Collect meta information having attribute information corresponding to the directory requested to be displayed based on the directory display request given from the outside, and subordinates included in the directory requested to be displayed based on the meta information. A directory component that identifies the directory;
Whether or not it is possible to narrow down the files included in the directory requested to be displayed with reference to the meta information collected by the directory configuration unit for each of the subordinate directories specified by the directory configuration unit A directory prefetching unit that determines and excludes the subordinate directory determined to be unable to narrow down the files from the specified subordinate directory;
A data search server, comprising: a directory display unit for causing a display device to display, as a display directory, a directory that is not excluded by the directory prefetching unit among the specified directories.   The attribute information includes at least one pair of an attribute type and an attribute value that is a lower attribute of the attribute type, and the directory configuration unit is such that the directory requested to be displayed corresponds to the attribute type. If there is, the directory corresponding to the attribute value is specified as the lower directory, and if the directory requested to be displayed corresponds to the attribute value, the lower directory corresponds to the attribute type. The directory is specified, and the display unit displays the display directory when the directory requested for display corresponds to an attribute type, and the directory requested for display corresponds to an attribute value. 2. The data search server according to claim 1, wherein the display directory is displayed together with information representing a file.   The directory prefetching unit searches the meta information collected by the directory configuration unit for a pair of the attribute type and the attribute value, and obtains meta information obtained as a result of the search for all the attribute values paired. 3. The data search server according to claim 2, wherein a directory corresponding to an attribute type whose number of information does not decrease below the number of the meta information collected by the directory configuration unit is excluded.   When the directory requested to be displayed corresponds to the attribute type, the directory prefetching unit is assigned to the attribute type corresponding to the directory requested to be displayed and the lower level specified by the directory configuration unit. The meta information collected by the directory configuration unit is searched for a pair with an attribute value corresponding to a directory, and the number of files having the meta information obtained as a result of the search is higher than the directory requested to be displayed. 4. The data search server according to claim 3, wherein a directory corresponding to the attribute value is excluded from the specified directory when the number does not decrease from the number of files included in the directory.

Images