JP2006155019A - Search folder device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that the retrieval function of a current file system is very hard to use since a retrieval condition is preserved in a file when preserved and the file is performed when performing retrieval again. <P>SOLUTION: Retrieval is performed as data subordinate to the folder, so that a content in opening the folder can be defined as a retrieval result. Thus, a retrieval folder device provides much convenience to a user as a file management device. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a file operation and search function in a file management apparatus.

  A search function in a conventional file system is performed by opening a search window or view, entering a search condition, and pressing a search execution key. As a method for saving the search condition, the search condition is saved as a file and the file is executed.

For example, see Patent Document 1 and Patent Document 2.
JP 2000-003298 A JP 2004-133505 A

  The conventional search method uses the file format to save the search conditions, so you need to open the properties to know the search range and search conditions, and launch the file to perform further searches It was very difficult to use.

  In the present invention, without changing the concept of the folder, a search condition is given to the folder, and items matching the search condition are displayed in the folder. Also, the search range can be selected from a relative range and an absolute range, and operations such as moving the search folder can be easily performed. In addition, it is possible to take conditions and AND conditions by hierarchizing search folders. By this operation, the user can visually recognize the narrowing search, which gives the user great convenience as a file management device.

  In order to achieve the above-described object, the present invention is an information processing apparatus that manages files, and displays a holding unit that holds a file, a search unit that searches for a file held by the holding unit, and a file configuration. And the search condition is handled as subordinate data of the folder. When the folder is opened, a file search is performed according to the search condition, and the search result file is displayed by the display means.

  As described above, according to the present invention, it is possible to have a search condition expression as a folder, and it is possible to visually express the narrowing-down condition, and the file operation of the user is performed efficiently.

  FIG. 1 shows a schematic diagram of a file system for realizing a search folder.

  Reference numeral 101 denotes a normally used file system, such as NTFS (NT File System) or FAT (File Allocation Table).

  Reference numeral 102 denotes a central part of the system, which is an XML file control unit that creates an XSL that is a style sheet by converting the folder and file structure of the file system into XML.

  Reference numeral 103 denotes a database unit that uses the data converted into XML by the XML file control unit 102 as a database.

  An XML display unit 104 performs display based on the XML data and XSL data created by the XML file control unit 102. In the present embodiment, description will be made using an XML browser.

  FIG. 2 shows a system configuration functional block of the present embodiment.

In this embodiment, the file server 200 and the client 201 are configured, and a network function is added to the file system schematic diagram of FIG.
A file system 101 is assumed to be NTFS.

  Reference numeral 102 denotes a central part of the present system, which is a part for creating an XSL which is a style sheet by converting the folder and file structure of the file system into XML.

  Reference numeral 103 denotes a database unit that uses data converted into XML by the XML file control unit 102 as a database. In this embodiment, the database unit is an SQL-compatible database.

  Reference numeral 202 denotes an HTTP server control unit for transferring the XML file and XSL file created by the XML file control unit 102 to the client 201 using HTTP (HyperText Transfer Protocol).

  A browser 203 displays XML data and has an http function for receiving an XML file from the file server 200.

  Reference numeral 204 denotes a LAN (Local Area Network) for connecting the file server 200 and the client PC 201.

  FIG. 3 illustrates an XML basic file management structure created by the XML file control unit 102.

  FIG. 3 shows an example of a hierarchical folder structure that does not include a search folder.

  FIG. 4 is a format block diagram showing the state of FIG. 3, and FIG. 5 is a specific XML description example showing the state of FIG.

  The present invention manages the configuration of folders using an XML (Extentional Markup Language) description.

  The basic configuration is to create a management file that uses a drive letter as the Top description, configure a document called C drive.xml, write a predetermined description in it, and add elements (contents) such as files in the file system. Shown with external link. The link at this time may be either an absolute position or a relative position. In this embodiment, explanation will be made using both a relative link and an absolute link.

  In FIG. 5, <? Xml version = "1.0" encoding = "Shift_JIS"?> Is a description of a declaration made at the head.

  In FIG. 4, a DRIVE section (301) indicates the head of this document. In FIG. 5, the portion surrounded by <DRIVE> to </ DRIVE> is the main body of this document.

  As attribute values of DRIVE, there are GUID (Global Unique ID) information uniquely assigned for management in the database and DRIVE_TYPE indicating drive type information.

  In the embodiment, the hard disk drive is used, and DRIVE_TYPE = “HD_DISK”.

In FIG. 4, a META_BASE part (302) is a part that holds meta information (management information) of the DRIVE part. In FIG. 5, the meta information is held in a portion surrounded by <META_BASE> to </ META_BASE>.
In particular, here, as attribute values, GUID information uniquely assigned for management in the database, NAME information indicating the DRIVE name, and COMENT information indicating the DRIVE comment are retained.

  In this embodiment, NAME is “C drive”, and COMENT is “” because it is not particularly described.

  In FIG. 4, a FILE portion (303) is a portion that holds file information. In FIG. 4, the information is held in a portion surrounded by <FILE> to </ FILE>. As attribute values of FILE, DOC_SRC information indicating the location where the file exists and INDEX information holding the search information of the file are held.

In this embodiment, the DOC_SRC information is “C: domestic product catalog \ domestic product catalog.doc”,
INDEX information is not set.

  In FIG. 4, a META_BASE part (304) is a part that holds meta information (management information) of the FILE part. In FIG. 5, the meta information is held in a portion surrounded by <META_BASE> to </ META_BASE>.

  In particular, here, GUID information uniquely assigned for management in the database, NAME information indicating the FILE name, and COMENT information indicating the FILE comment are held as attribute values.

  In this embodiment, NAME is “domestic product catalog.doc” and COMENT is “”, which is not particularly filled in.

  305 and 306 describe the domestic product catalog.xls shown in FIG.

  In FIG. 4, a FOLDER part (307) is a part for holding folder information. In FIG. 5, the information is held in a portion surrounded by <FOLDER> to </ FOLDER>. As FOLDER attribute values, GUID (Global Unique ID) information uniquely assigned for management in the database and FOLDER_TYPE information indicating folder type information are stored. In the FOLDER section (307), the FOLDER_TYPE information is “STATIC” indicating a normal folder.

  In FIG. 4, a META_BASE part (308) is a part that holds meta information (management information) of the FOLDER part. In FIG. 5, the meta information is held in a portion surrounded by <META_BASE> to </ META_BASE>.

  In particular, here, as attribute values, GUID information uniquely assigned for management in the database, NAME information indicating the FILE name, and COMENT information indicating the FILE comment are retained.

  In this embodiment, NAME is “Vehicle” and COMENT is “4 wheels”.

  Reference numerals 309 and 310 hold the sedan folder information shown in FIG. 3 and are described in XML in the same manner as 307 and 308.

  A description will be given below when the search folder 401 shown in FIG. 6 is created in this file system.

  FIG. 7 is a format block diagram when a search folder is added, and shows a search folder format block added to 402.

  FIG. 8 shows a specific example of the XML description that is additionally written, which is added under the tag of the folder of the domestic product catalog shown in FIG.

  The added folder part (401) is a part for holding information on the search folder.

  Then, search folder information is held in a portion surrounded by <FOLDER> to </ FOLDER> shown in FIG.

  Since the folder here is a search folder, the FOLDER_TYPE information indicating the type information of the folder is “DYNAMIC” indicating the search folder.

  For the SCOPE information, which is an attribute indicating the search range, the search range may be either an absolute path or a relative path, but in this example, “./” is set as the search target under the parent folder.

  QRY_CMD, which is an attribute indicating a search condition, is an attribute indicating a search condition expression, and the server side only needs to be able to understand the SQL search expression or other search expressions. In the present embodiment, since it is a complex condition such as a search for a JPG image and a file of 500 KB or more, it is described as (SIZE => 500 KB) * (NAME = *. JPG).

  Next, an outline of a procedure for creating and using a search folder will be described with reference to FIGS.

  FIG. 9 shows a state in which the file viewer is displayed by the XML browser on the client PC, and the search folder has already been created.

  Reference numeral 501 denotes a folder view showing the hierarchical structure of a folder, 502 denotes a file view that displays a file, and 503 denotes a toolbar that performs operations such as creating a new folder and file, deleting, and changing the name.

  Reference numeral 504 denotes a search folder, and a binocular picture is added to the folder icon in order to identify other folders.

  In FIG. 10, when a search folder is created by operating the toolbar in step S601, a description of the additional part shown in FIG. 8 is added as follows.

<FOLDER
GUID = 1414 // unique ID
FOLDER_TYPE = "DYNAMIC" // folder type
SCOPE = ""
QRY_CMD = ""
>
<META_BASE
GUID = 1600 // unique ID
NAME = "new folder" // FOLDER OR FILE NAME
COMENT = ""
/>
</ FOLDER>
If the name of the search folder is designated as “image” in step S602, NAME = “image” is described in the NAME attribute, and the following results.

<FOLDER // unique ID
FOLDER_TYPE = "DYNAMIC" // folder type
SCOPE = ""
QRY_CMD = ""
>
<META_BASE
GUID = 1600 // unique ID
NAME = “Image” // FOLDER OR FILE NAME
COMENT = ""
/>
</ FOLDER>
In step S603, if the search condition for the search folder is “JPG” and the file size is specified as 500 KB, QRY_CMD = “(SIZE => 500 KB) * (NAME =“. JPG ”)” is described in the QRY_CMD attribute. It will be as follows.

<FOLDER
GUID = 1414 // unique ID
FOLDER_TYPE = "DYNAMIC" // folder type
SCOPE = ""
QRY_CMD = "(SIZE => 500KB) * (NAME =". JPG ")"
>
<META_BASE
GUID = 1600 // unique ID
NAME = “Image” // FOLDER OR FILE NAME
COMENT = ""
/>
</ FOLDER>
If the search range of the search folder is specified as a subordinate folder in step S604, SCOPE = “./” is described in the SCOPE attribute as follows.

<FOLDER
GUID = 1414 // unique ID
FOLDER_TYPE = "DYNAMIC" // folder type
SCOPE = "./"
QRY_CMD = "(SIZE => 500KB) * (NAME =". JPG ")"
>
<META_BASE
GUID = 1600 // unique ID
NAME = “Image” // FOLDER OR FILE NAME
COMENT = ""
/>
</ FOLDER>
When the search folder is opened by double-clicking in step S605, a search is performed according to the conditions set in steps S603 and S604, and the search result is displayed in the file view in S606.

  Next, the internal processing operation when opening the search folder will be described.

  When the search folder is double-clicked from the client, the GUID of the search folder is transmitted to the server by the XML browser 203 of the client.

  The HTTP server control unit 202 of the file server 200 that has received the GUID notifies the XML file control unit 102 that the search folder has been accessed.

  The XML file control unit 102 knows the search conditions for the search folder from the GUID, and queries the database unit.

  The database unit quickly searches and returns the result to the XML file control unit 102.

  The XML file control unit 102 transmits the search result as XML data to the client 201 via the HTTP server control unit 202.

  The client 201 that has received the search result displays the search result by the built-in XML browser 203.

  Next, internal processing when the search folder is moved and copied will be described.

  When the search folder is moved, the format block of the search folder 402 shown in FIG. 7 is moved. As for the description of XML, the description shown in FIG. 8 moves to the tag area of the folder to be moved.

  When the search folder is copied, the description of the move source is not deleted, but is copied to the folder tag area of the copy destination.

  Next, an operation when a search folder is created under the search folder will be described with reference to FIG.

  The athletic meet (701) is a normal folder, and has a search folder under it.

  The image (702) in 2002 is a search folder, the search range is a parent folder, and the search condition is a file whose file creation date is 2002.

  An image (703) of 1M or more is a search folder, the search range is a parent folder, and the search condition is a file whose file capacity is 1 MB or more.

  When the search folder of the image (703) of 1M or more is accessed, the XML file control unit (102) of the file server (200) confirms the file type of the image (703) of 1M or more and recognizes that it is a search folder.

  The search range of 1M or more images (703) is confirmed, and the parent folder is recognized.

  Check the file type of the 2002 image (702) and recognize that it is a search folder.

  The search range of the image (702) in 2002 is confirmed, and the parent folder is recognized.

  Check the file type of the athletic meet (701) folder and recognize that it is a normal folder.

  The search is executed according to the search range and search formula of the image (702) of 2002, and the search result is temporarily stored.

  The search range is temporarily stored as a search result, and a search formula for images (703) of 1M or more is executed.

  The XML file control unit (102) transmits the final search result to the client via the HTTP server control unit (204). Therefore, when a search folder is created under the search folder, the lower search folder is the result of ANDing with the search conditions of the upper search folder, and a narrow search is possible.

It is a system schematic diagram. It is an Example system block diagram. It is a basic folder block diagram. It is a basic format block diagram. This is an example of basic XML description. It is the folder structure figure which added the search folder. It is the format block diagram which added the search folder. This is an example of XML description with a search folder added. It is a display image figure. It is an operation flowchart. It is a search folder hierarchy diagram.

Explanation of symbols

101 File System
102 XML file control section
103 Data Base
104 XML display section
200 file server
201 client PC
202 HTTP server controller
203 XML browser
204 LAN

Claims (4)

An information processing apparatus for managing files,
A holding means for holding a file, a search means for searching for a file held by the holding means, and the search condition are handled as subordinate data of a folder,
A file management apparatus having a search folder, wherein files in the folder indicate search results.   A file management apparatus comprising: means for separately setting a search range and a search condition in the search means.   A file management apparatus having a search folder that treats the search folder condition as an AND condition by hierarchically expressing the search folder that handles the search condition as subordinate data of the folder.   A file management apparatus capable of setting a search range condition of the search folder by both an absolute path and a relative path.

Images