JP2013077150A - File management program, information processing device, and file management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To support an efficient file search.SOLUTION: Generation means 1b acquires a first file 2 stored in storage means 1a, and generates a second file 3 including tags A and B corresponding to elements 2a and 2b included in the first file 2. Then, the generation means 1b extracts one or more character strings included in the second file 3 on the basis of the tags A and B, and stores the second file 3 and the extracted character string(s) in the storage means 1a in association. When a character string is input, search means 1c refers to the storage means 1a, searches for the second file 3 corresponding to the input character string, and outputs a search result.

Description

  The present invention relates to a file management program, an information processing apparatus, and a file management method.

  A file handled by a plurality of information processing apparatuses may be stored in a server apparatus connected via a network. The server device manages the files in a unified manner to share and make redundant, thereby improving the accessibility and safety of the files. Such a server device may be called a file server.

  The file server stores a large number of files. For this reason, the file server extracts a character string included in each file as an index so that the file can be easily searched. The file server can search a file at high speed using the character string and index input by the user. However, index extraction or character string search cannot be performed on files other than text. Therefore, there is a proposal for uploading a registered document that is difficult to extract a text to a server device by specifying another file for text extraction together with the registered document on the client device (for example, see Patent Document 1).

JP 2008-27214 A

  By the way, various devices can access the file server. In particular, a portable terminal device has a smaller display screen and a smaller amount of information that can be displayed at a time than a desktop / laptop type information processing device. For this reason, when a search request from a mobile terminal device can be received, there is a request to be able to accurately present a file requested by a user as a search result.

  For example, in order to enable a detailed search, it is possible that a user separately prepares additional information for search for a file, and the information can be specified as a search condition in addition to the text in the file. It is done. However, this method creates a work burden on the user for adding information to the file.

Thus, how to manage files to realize a mechanism for supporting efficient file search is a problem.
In one aspect, an object of the present invention is to provide a file management program, an information processing apparatus, and a file management method that support efficient file search.

  According to one embodiment, a file management program is provided. The file management program acquires a first file stored in the storage means, and stores a second file including one or more tags according to one or more elements included in the first file. Generate one or more character strings included in the second file based on one or more tags, and store the second file and the extracted character strings in association with each other in association with each other. When a character string is input, the storage unit is referred to search for a second file corresponding to the input character string, and a process for outputting the search result is executed by the computer.

  According to one embodiment, an information processing apparatus is provided. The information processing apparatus includes a generation unit and a search unit. The generation unit acquires the first file stored in the storage unit, and generates a second file including one or more tags corresponding to one or more elements included in the first file. One or more character strings included in the second file are extracted based on one or more tags, and the second file and the extracted character strings are associated with each other and stored in the storage unit. When the character string is input, the search means refers to the storage means, searches for the second file corresponding to the input character string, and outputs the search result.

  According to one embodiment, a file management method executed by a computer is provided. In this file management method, a first file stored in a storage means is acquired, and a second file including one or more tags corresponding to one or more elements included in the first file is obtained. Generate one or more character strings included in the second file based on one or more tags, and store the second file and the extracted character strings in association with each other in association with each other. . When a character string is input, the second file corresponding to the input character string is searched with reference to the storage means, and the search result is output.

  According to one embodiment, efficient file search can be supported.

It is a figure which shows the information processing apparatus which concerns on 1st Embodiment. It is a figure which shows the information processing system which concerns on 2nd Embodiment. It is a figure which shows the hardware example of a file server. It is a figure which shows the hardware example of a client. FIG. 3 is a diagram illustrating a software example of an information processing system. It is a figure which shows the example of the directory tree of a file server. It is a figure which shows the example of a storage file. It is a figure which shows the example of the file for a display. It is a figure which shows the example of a production | generation of the display file. It is a figure which shows the example of an index table. It is a figure which shows the example of file management data. It is a figure which shows the example of reference log | history data. It is a figure which shows the example of a search screen. It is a flowchart which shows the file production | generation process for a display. It is a flowchart which shows a file search process. It is a figure which shows the example of the client control using the file for a display.

Hereinafter, the present embodiment will be described with reference to the drawings.
[First Embodiment]
FIG. 1 is a diagram illustrating an information processing apparatus according to the first embodiment. The information processing apparatus 1 is an apparatus that manages various files. The information processing apparatus 1 may include a processor such as a CPU (Central Processing Unit) and a memory such as a RAM (Random Access Memory), or may be a computer that executes a program stored in the memory. The information processing apparatus 1 includes a storage unit 1a, a generation unit 1b, and a search unit 1c.

  The storage unit 1 a stores the first file 2 and the second file 3. The first file 2 is an original file stored in the storage unit 1a by the user. The first file 2 includes elements 2a and 2b. The element 2a is, for example, a character string “item X1” in the table. The element 2b is a diagram, for example. For example, the user can access the information processing apparatus 1 from the client apparatus operated by the user via the network, and store the first file 2 in the storage unit 1a.

  The second file 3 is a file generated by the generation unit 1 b based on the first file 2. The second file 3 includes tags A and B corresponding to the elements 2 a and 2 b included in the first file 2. Examples of the format of the second file 3 including the tag include HTML (HyperText Markup Language) and XML (eXtensible Markup Language). In the second file 3, one element may be described using a plurality of tags.

  The storage unit 1a may be implemented by a disk device such as an HDD (Hard Disk Drive). Further, a storage unit different from the storage unit 1a may be provided, and the first file 2 and the second file 3 may be stored in separate storage units.

  The generation unit 1b acquires the first file 2 stored in the storage unit 1a and generates the second file 3. The generation unit 1 b can also set a value for the attribute in the tag based on the positional relationship between the elements in the first file 2. For example, when a character string indicating the title of the figure exists in the vicinity of the element 2b in the figure, the character string is set to “attribute Y” in the tag B. For example, in the case of HTML, it is conceivable to set a character string such as “drawing Z1” in the “title” attribute indicating the title of the figure in the “<image>” tag indicating the figure element.

  As the timing at which the generation unit 1b acquires the first file 2, for example, the timing at which the first file 2 is stored in the storage unit 1a, the timing at which a predetermined time is reached, or the like can be considered.

  The generation unit 1b extracts one or more character strings included in the second file 3 based on the tags A and B. For example, the character string “item X1” indicated by the tag A can be extracted from the second file 3 for the element 2a. Further, for example, the character string “drawing Z1” indicated by the attribute “attribute Y” in the tag B can be extracted from the second file 3 for the element 2b. In the example of HTML, the character string can be extracted by detecting the “title” attribute indicating the title of the figure from the “<image>” tag indicating the element of the figure.

  The generation unit 1b associates the second file 3 with the extracted character string and stores them in the storage unit 1a. For example, the second file 3 and the character string “item X1” are associated with each other and stored in the storage unit 1a. Further, for example, the second file 3 and the character string “drawing Z1” are associated with each other and stored in the storage unit 1a. At this time, based on a tag including the character string of “item X1” and a tag (and attribute) including the character string of “drawing Z1”, attribute information (for example, a figure title) in the document is added to each character string. You may associate.

  When the character string is input, the search unit 1c refers to the storage unit 1a, searches the second file 3 corresponding to the input character string, and outputs the search result. For example, the user can access the information processing apparatus 1 from the client apparatus operated by the user via the network and input a search character string for searching for a file to the information processing apparatus 1. For example, the search means 1c outputs the second file 3 including the character string as a search result for the character string “item X1”. Further, the search unit 1c outputs the second file 3 including the character string as a search result for the character string “drawing Z1”. At this time, when the attribute information “diagram title” is associated with the character string “drawing Z1”, the attribute information can be acquired together with the character string for search to perform the search. For example, it is possible to search for a file including the character string “drawing Z1” as “drawing title” by designating the attribute information.

  According to the information processing apparatus 1, the generation unit 1 b acquires the first file 2 stored in the storage unit 1 a and includes tags A and B corresponding to the elements 2 a and 2 b included in the first file 2. A second file 3 is generated. The generation unit 1b extracts one or more character strings included in the second file 3 based on the tags A and B. The second file 3 and the extracted character string are associated with each other and stored in the storage unit 1a by the generation unit 1b. When a character string is input, the search unit 1c refers to the storage unit 1a, searches the second file 3 corresponding to the input character string, and outputs a search result.

  Thereby, efficient file search can be supported. Specifically, since the second file 3 is generated based on the first file 2 and the character string is extracted based on the tag, the index is more detailed than when the character string is extracted from the first file 2. Can be created. For example, attribute information in the document can be given to the character string by adding the extracted character string to the index in association with the content indicated by the tag or the attribute in the tag. Specifically, attribute information such as a document title, a figure title, and a character string in a table may be given to the character string. If a character string is searched together with attribute information in the document, the search result can be narrowed down more efficiently. Furthermore, by using a tag when creating the detailed index as described above, it is possible to prevent the user from creating additional information. Therefore, labor saving of work by the user can be achieved.

  In addition, since the second file 3 is generated in the HTML format or the like, if the second file 3 searched for is transmitted to the client device, the client device uses the predetermined web browser included in the device to execute the second file 3. 3 contents can be browsed.

  Here, when the client device is a mobile terminal device, it may be difficult to operate an application that can operate on another device (such as a desktop information processing device) on the mobile terminal device. In this case, even if the original file (first file 2) is provided to the mobile terminal device, it is difficult to view the contents of the file, which may be inconvenient. On the other hand, Web browsers are often available even for portable terminal devices. Therefore, if the second file 3 generated in the HTML format or the like as described above is provided to the mobile terminal device, the content of the file can be easily browsed even on the mobile terminal device.

  In addition, although the memory | storage means 1a, the production | generation means 1b, and the search means 1c shall be implement | achieved by the information processing apparatus 1, you may implement | achieve these each means on a separate apparatus. For example, the storage unit 1a may be realized by a storage device, and the generation unit 1b and the search unit 1c may be realized by two different information processing devices.

[Second Embodiment]
FIG. 2 is a diagram illustrating an information processing system according to the second embodiment. The second information processing system is a system that centrally manages the files used by the client device using the server device. The second information processing system includes a file server 100 and clients 200 and 300. The file server 100 and the client 200 are connected via the network 10 and the access point 20. The file server 100 and the client 300 are connected via the network 10. The network 10 may be a LAN (Local Area Network). The network 10 may be a wide area network such as the Internet. Further, the client 200 and the access point 20 are connected wirelessly. The wireless communication may be a wireless LAN. The client 200 may wirelessly communicate with a base station (not shown) and access the file server 100 via a mobile communication network (not shown) and the network 10.

  The file server 100 is a server device that centrally stores files used by the clients 200 and 300. The file server 100 also has a Web server function, and provides a GUI (Graphical User Interface) for supporting file operations to the clients 200 and 300.

  The client 200 is a client device used by a user. The client 200 is a mobile terminal device, and wirelessly communicates with the access point 20. The client 200 includes a web browser and can access the file server 100 via the web. A plurality of clients 200 may be prepared and used by a plurality of users individually.

  The client 300 is a client device used by a user. The client 300 is a laptop computer. The client 300 is connected to the network 10 by wire or wireless and can access the file server 100. The client 300 includes a web browser and can access the file server 100 via the web.

  Here, the client 300 is larger than the client 200, and the performance of the hardware to be mounted is higher than that of the client 200. For this reason, it is possible to use an application that requires high processing capacity for operation.

  On the other hand, the client 200 is smaller than the client 300. For this reason, the client 200 has less information that can be displayed on the display at a time than the client 300. Further, the hardware performance is lower than that of the client 300. For this reason, even an application that can be used by the client 300 may be difficult to use by the client 200. In addition, when the OS (Operating System) executed by the two is different, an application that can be used by the client 300 may not be supported by the OS of the client 200. In that case, it may be difficult for the client 200 to browse the file created by the application of the client 300.

  The file server 100 provides an environment in which files stored by the client 300 can be efficiently searched and viewed from the client 200. Hereinafter, the configuration of an information processing system that performs such file management will be described in detail.

  FIG. 3 is a diagram illustrating a hardware example of the file server. The file server 100 includes a CPU 101, a ROM (Read Only Memory) 102, a RAM 103, an HDD 104, an image signal processing unit 105, an input signal processing unit 106, a disk drive 107, and a communication unit 108. Each unit is connected to the bus of the file server 100. The client 300 can also be implemented using the same hardware as the file server 100.

  The CPU 101 is a processor that controls information processing of the file server 100. The CPU 101 reads out at least a part of the program and data stored in the HDD 104, expands it in the RAM 103, and executes the program. The file server 100 may be provided with a plurality of processors to execute the program in a distributed manner.

  The ROM 102 stores a predetermined program such as a BIOS (Basic Input / Output System) program executed when the file server 100 is activated. The ROM 102 may be a rewritable nonvolatile memory.

  The RAM 103 is a volatile memory that temporarily stores programs executed by the CPU 101 and data used for processing. Note that the file server 100 may include a memory of a type other than the RAM, or may include a plurality of memories.

  The HDD 104 is a nonvolatile storage device that stores programs such as an OS program and application programs and data. The HDD 104 reads / writes data from / to the built-in magnetic disk according to instructions from the CPU 101. The file server 100 may include a nonvolatile storage device of a type other than the HDD (for example, an SSD (Solid State Drive)) or a plurality of storage devices.

  The image signal processing unit 105 outputs an image to the display 11 connected to the file server 100 in accordance with an instruction from the CPU 101. As the display 11, for example, a CRT (Cathode Ray Tube) display or a liquid crystal display can be used.

  The input signal processing unit 106 acquires an input signal from the input device 12 connected to the file server 100 and outputs it to the CPU 101. As the input device 12, for example, a pointing device such as a mouse or a touch panel, a keyboard, or the like can be used.

  The disk drive 107 is a drive device that reads programs and data recorded on the recording medium 13. As the recording medium 13, for example, a magnetic disk such as a flexible disk (FD) or an HDD, an optical disk such as a CD (Compact Disc) or a DVD (Digital Versatile Disc), or a magneto-optical disk (MO) is used. Can be used. For example, the disk drive 107 stores the program and data read from the recording medium 13 in the RAM 103 or the HDD 104 in accordance with an instruction from the CPU 101.

  The communication unit 108 is a communication interface that communicates with the clients 200 and 300 via the network 10. The communication unit 108 may be a wired communication interface or a wireless communication interface.

  FIG. 4 is a diagram illustrating a hardware example of the client. The client 200 includes a CPU 201, ROM 202, RAM 203, recording medium reading unit 204, wireless communication unit 205, antenna 205a, image signal processing unit 206, display 206a, input signal processing unit 207, touch panel 207a, keypad 207b, audio signal processing unit. 208, a microphone 208a, and a speaker 208b. Each unit is connected to the bus of the file server 100.

  The CPU 201 is a processor that controls information processing of the client 200. The CPU 201 reads out at least a part of the program and data stored in the RAM 203, expands it in the RAM 203, and executes the program. The client 200 may be provided with a plurality of processors to execute the program in a distributed manner.

  The ROM 202 stores a predetermined program such as a BIOS (Basic Input / Output System) program executed when the client 200 is activated. The ROM 202 may be a rewritable nonvolatile memory.

  The RAM 203 is a volatile memory that temporarily stores programs executed by the CPU 201 and data used for processing. Note that the client 200 may include a memory of a type other than the RAM, or may include a plurality of memories.

  The recording medium reading unit 204 reads data stored in the recording medium 14 and stores data in the recording medium 14. For example, a semiconductor memory can be used as the recording medium 14.

  The wireless communication unit 205 performs wireless signal processing and realizes wireless communication with the access point 20. The wireless communication unit 205 demodulates and decodes a signal received from the access point 20 via the antenna 205a, and outputs the obtained reception data to the CPU 201. In addition, the wireless communication unit 205 encodes and modulates transmission data acquired from the CPU 201, and transmits the obtained transmission signal to the access point 20 via the antenna 205a.

  The image signal processing unit 206 outputs an image to the display 206a in accordance with an instruction from the CPU 201. For example, a liquid crystal display can be used as the display 206a.

  When the input signal processing unit 207 detects a touch operation on the touch panel 207a or a key press on the keypad 207b, the input signal processing unit 207 acquires an input signal indicating the touch operation or a pressed key and outputs the input signal to the CPU 201.

  The audio signal processing unit 208 acquires an audio analog signal from the microphone 208a, performs predetermined signal conversion processing, and outputs audio data to the CPU 201. The audio signal processing unit 208 acquires audio data from the CPU 201, performs a predetermined signal conversion process, and causes the speaker 208b to reproduce the audio.

  FIG. 5 is a diagram illustrating an example of software of the information processing system. Part or all of the units shown in FIG. 5 may be modules of programs executed by the file server 100 and the client 200. 5 may be an electronic circuit such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit). The client 300 can also be implemented using the same unit as the client 200.

The file server 100 includes a storage unit 110, a Web service providing unit 120, a file management unit 130, and an application 140.
The storage unit 110 stores files used by the clients 200 and 300. In addition, the storage unit 110 stores an index table used for file search. Further, the storage unit 110 stores file management data for managing relevance between files and reference history data for managing the history of referenced files.

  The web service providing unit 120 provides web services to the clients 200 and 300. Specifically, a Web page for uploading a file from the client 200 or 300 to the file server 100 or downloading a file from the file server 100 is transmitted to the client 200 or 300. The clients 200 and 300 can acquire the Web page by accessing a predetermined URL using a Web browser. This Web page also includes a GUI for inputting a character string used for file search.

  The Web service providing unit 120 outputs the input character string to the file management unit 130 and requests a file search. Further, the Web service providing unit 120 acquires a search result from the file management unit 130, generates a screen for outputting the search result, and transmits the screen to the requesting clients 200 and 300. The clients 200 and 300 can select a file from the search results, browse the contents of the file, and download the file.

  In the present embodiment, the case where the file search reception and download functions are implemented by a Web service is illustrated, but this is only an example, and it may be implemented by a predetermined application other than the Web service.

  The file management unit 130 controls file management of the file server 100. The file management unit 130 includes a generation unit 131, an extraction unit 132, a search unit 133, and a history management unit 134.

  The generation unit 131 acquires an original file (hereinafter sometimes referred to as a storage file) stored in the storage unit 110, and an HTML file (hereinafter referred to as a display file) including tags according to elements included in the file. File). Here, the storage file is, for example, a file generated by an application on the clients 200 and 300.

  Here, the application 140 may have a function of generating an HTML file from a file generated by the application on the clients 200 and 300. In that case, the generation unit 131 may request the application 140 to generate an HTML file. For example, the generation unit 131 can select the requested application 140 based on the extension added to the file. For example, it is conceivable to select an application registered in the OS on the file server 100 as a file that can process the file with the extension.

  Further, the generation unit 131 adds a predetermined script to the display file. This is because a predetermined operation by the user can be accepted when the display file is browsed by the Web browser 220.

  The extraction unit 132 extracts an index character string based on the tag included in the HTML file generated by the generation unit 131 and adds it to the index table stored in the storage unit 110.

  The search unit 133 acquires a file search request from the Web service providing unit 120. The search unit 133 searches the display file based on the search character string included in the search request and the index table stored in the storage unit 110 and outputs the search result to the Web service providing unit 120.

  The history management unit 134 manages a file reference history. The history management unit 134 acquires from the Web service providing unit 120 which file has been referred to the search result of the search unit 133 and records it in the reference history data stored in the storage unit 110.

  The application 140 is an application having a function of generating an HTML file from a stored file. Examples of such applications include Microsoft (registered trademark) Word, Excel, and PowerPoint (registered trademark).

The client 200 includes a storage unit 210 and a web browser 220.
The storage unit 210 stores files used by the client 200. For example, a file generated by an application on the client 200 or a file downloaded from the file server 100 is stored.

  The web browser 220 is a browser for performing web access to the web service providing unit 120. In order to access the file server 100, the user may be subjected to user authentication by an authentication server (not shown). The authentication server stores information such as information used for authentication (for example, user ID (Identifier), password, and user affiliation).

  Note that the file server 100 according to the second embodiment is an example of the information processing apparatus 1 according to the first embodiment. The generation unit 131 and the extraction unit 132 are an example of the generation unit 1b. The search unit 133 is an example of the search unit 1c.

  FIG. 6 is a diagram illustrating an example of a directory tree of a file server. The directory tree 50 is an example of a directory and file path structure displayed in a tree format in the storage unit 110.

  A directory 500 is provided on the directory tree 50. The directory 500 is a directory for storing shared files. The directory name of the directory 500 is “/ data”. Files uploaded from the clients 200 and 300 are stored in a directory under the directory 500. Under the directory 500, directories 510, 520, and 530 are arranged. Directories 510 and 520 are directories for storing storage files. The directory 530 is a directory for storing display files.

  The directory name of the directory 510 is “/ system”. For example, a file related to use of the information processing system among the stored files is stored in the directory 510. The directory 510 includes storage files 511 and 512. The storage file 511 describes a manual for using the system, and the file name is “manual.dat”. The storage file 512 describes a plan such as a newly installed system, and the file name is “project.dat”.

  The directory name of the directory 520 is “/ material”. For example, among the stored files, a file for managing material of a company that uses the information processing system is stored in the directory 520. The directory 520 includes a storage file 521. The storage file 521 includes a table for material management, and the file name is “management table.dat”.

  The directory name of the directory 530 is “/ display file”. The directory 530 includes display files 531, 532, and 533. The display file 531 is a display file corresponding to the storage file 511, and the file name is “manual.html”. The display file 532 is a display file corresponding to the storage file 512, and the file name is “project.html”. The display file 533 is a display file corresponding to the storage file 521, and the file name is “management table.html”.

  The directory in which the storage file is stored may be specified by the user at the time of uploading. In addition to allowing the user to directly specify the storage destination directory, the user may specify the storage file classification and determine the storage destination directory based on the classification. However, the directory 530 is normally a directory that cannot be selected by the user as the storage destination of the storage file.

  FIG. 7 is a diagram illustrating an example of a storage file. FIG. 7 illustrates the display contents when the storage file 511 (file name “manual.dat”) is input to a predetermined application. The storage file 511 includes elements 511a, 511b, 511c, 511d, 511e, and 511f.

  Elements 511a and 511c are character strings indicating the names of the drawings. Elements 511b and 511d are diagrams (images). The element 511e is a character string indicating the name of the table. The element 511f is a table.

  The user can view such contents by inputting the storage file 511 to an application on the client 300, for example. On the other hand, when it is difficult to execute the application on the client 200, it is difficult to browse such contents on the client 200. Therefore, the generation unit 131 generates a display file 531 based on the storage file 511.

  FIG. 8 is a diagram illustrating an example of a display file. FIG. 8 illustrates the description content of the display file 531 (file name “manual.html”). The generation unit 131 uses the file name “manual.dat” of the storage file 511 as the file name of the display file 531 instead of “.html”. The display file 531 includes descriptions 531a, 531b, 531c, 531d, 531e, and 531f.

  The description 531 a indicates the title “manual” of the display file 531. For example, the generation unit 131 adds a part “manual” obtained by removing the extension “.dat” from the file name of the storage file 511 to the display file 531 as a “<title>” tag.

  The description 531b is JavaScript (registered trademark) added to the display file 531 by the generation unit 131. For example, a process is described in which the user's flick operation is received on the screen displayed on the display 206a by the Web browser 220 based on the display file 531, and the screen is scrolled according to the operation. Further, for example, it is conceivable to describe a process for controlling an animation when the screen is enlarged or reduced. Further, for example, it is conceivable to describe a process for shaping the display screen of the display file 531 according to the number of pixels of the display 206a of the client 200.

  The description 531c is a description indicating the character string elements included in the storage file 511. For example, for the element 511a, the character string “FIG. 1:” is described in the “<td>” tag. Character strings “setting” and “screen” are described in a “<ruby>” tag surrounded by “<td>” tags. Character strings “SETTING” and “GAMEN” are described in a “<rt>” tag surrounded by “<ruby>” tags. As described above, the generation unit 131 assigns a predetermined tag to each character string element of the text included in the storage file 511 and describes it in the display file 531.

  The description 531d is a description showing the elements of the figure included in the storage file 511. For example, the generation unit 131 describes the “<img>” tag in the display file 531 for the element 511b. In the “<img>” tag, for example, a “title” attribute, a “src” attribute, and the like are further described based on the information of the storage file 511.

  The description 531e is a description showing the elements of the table included in the storage file 511. For example, the generation unit 131 describes a “<table>” tag in the display file 531 for the element 511f. In the “<table>” tag, for example, the title of the table is described including the “<caption>” tag.

  The description 531f is a description added to the display file 531 by the generation unit 131. The description 531f describes an operation that can be accepted by the Web browser 220 that displays the contents of the display file 531 as in the description 531b. For example, a process for describing the path of the storage file 511 corresponding to the display file 531 by the “hidden” attribute and making the storage file 511 downloadable from the file server 100 is described.

  Here, the generation unit 131 can determine the tag and the attribute in the tag as described above by detecting the positional relationship between the elements included in the storage file 511, and describe it in the display file 531. Next, a specific example of the description method will be described.

FIG. 9 is a diagram illustrating a generation example of a display file. FIG. 9A shows a generation example of the description 531d. FIG. 9B shows a generation example of the description 531e.
The description 531d describes the element 511a of the character string included in the storage file 511 as the title of the element 511b in the figure. For example, the generation unit 131 can acquire the element 511a of the character string within the predetermined distance L1 from the element 511b as the title of the element 511b (setting value of “title” attribute). When detecting the distance between the elements, for example, it is conceivable to specify a rectangle that covers the elements 511a and 511b and to detect the distance between the closest sides of each rectangle.

  Further, for example, when the detected character string includes a character string such as “figure” or “figure” and a symbol / alphanumeric combination (for example, “figure 1”), it may be acquired as the title of the figure. . This is because a character string considered to be more relevant to the element 511b in the figure is extracted. FIG. 9A illustrates the case where the element 511a is disposed on the upper side toward the paper surface of the element 511b, but the element 511a is disposed on the left and right or the lower side toward the paper surface of the element 511b. In this case, it can be determined whether the element 511a is the title of the figure based on the distance between the two elements.

  The description 531e describes the character string element 511e included in the storage file 511 as the title of the table element 511f. For example, the generation unit 131 can acquire the element 511e of the character string within the predetermined distance L2 from the element 511f as the title of the element 511f (setting value of the “<caption>” tag) as in FIG. 9A. As a method of detecting the distance between the elements, for example, a rectangle that covers the elements 511e and 511f may be specified and the distance between the closest sides of each rectangle may be detected, as in FIG. 9A.

  Further, for example, when the detected character string includes a character string such as “table” or “table” and a symbol / alphanumeric combination (for example, “table-1”), the title of the table may be used. This is because a character string considered to be more relevant to the table element 511f is extracted. FIG. 9B illustrates the case where the element 511e is disposed on the upper side toward the paper surface of the element 511f, but the element 511e is disposed on the left and right or the lower side toward the paper surface of the element 511f. In this case, it can be determined whether the element 511e is the title of the table based on the distance between the two elements.

  The extraction unit 132 extracts a character string based on the tag of the display file generated by the generation unit 131 in this way, and registers it in the index table. For example, the extraction unit 132 extracts the following character string from the display file 531.

(1) The character string “manual” described in the “<title>” tag is extracted as a document title.
(2) “<td>” tag, “<ruby>” tag, character string “FIG. 1:” described in the “<rt>” tag, “setting”, “setting”, etc. are included in the text of the document Extracted as a character string.

(3) The character string “FIG. 1: Setting screen” described as the “title” attribute in the “<img>” tag is extracted as the title of the figure.
(4) The character string “Table 1: Setting Procedure” described by the “<caption>” tag enclosed by the “<table>” tag is extracted as the title of the table.

  It is also conceivable to extract a character string described in the “<table>” tag (especially a character string in an area surrounded by a ruled line) as a character string (text in the table) included in the table, for example. . The ruled line of the table can be detected by, for example, a “order” attribute in a “<table>” tag.

  In addition to the above-described charts, various elements can be identified by tags. For example, in HTML5, a “<audio>” tag describing an audio element and a “<video>” tag describing a moving image element can be used. In this case, if the storage file includes an audio element, the generation unit 131 describes the audio element by the “<audio>” tag and the audio file name by the “src” attribute in the “<audio>” tag. The extraction unit 132 can extract the character string set in the “src” attribute of the “<audio>” tag as the name of the audio file. When the stored file includes a moving image element, the “<video>” tag can be used as in the case of the audio element.

  The extraction unit 132 registers the extracted character string in the index table in association with attribute information indicating the role of the character string in the file (hereinafter also referred to as an in-document attribute) and a display file.

  FIG. 10 is a diagram illustrating an example of an index table. The index table 111 is stored in the storage unit 110. The index table 111 includes items of character strings, in-document attributes, and display files.

  In the item of the character string, a character string extracted from the display file (one character may be registered) is registered. In the document attribute item, the document attribute indicated by the character string is registered. As the in-document attributes, for example, “document title”, “figure title”, “table title”, “in-table text”, “text”, and the like can be registered. In the item of display file, the file name of the display file of the extraction source is set. Since the display file is previously defined to be stored in the directory 530 (directory name “/ display file”), the prefix is omitted in the setting of the display file item. However, the full path may be set.

  In the index table 111, for example, a storage file item may be provided and a path of the storage file may be set. In this way, it is possible to search the storage file from the character string based on the index table 111.

  FIG. 11 is a diagram illustrating an example of file management data. The file management data 112 is stored in the storage unit 110. The file management data 112 is a file in which information for classifying each directory included in the directory tree 50 (file classification information) and information for associating a storage file with a display file (file association information) are registered. is there. The file management data 112 is described in a csv (Comma Separated Values) format. However, other formats such as XML may be used.

  In the file classification information, for example, a classification “system use” is defined. Then, “... / data / system /” and “... / data / usage rules /” are defined as directories belonging to the classification of “system use”. Similarly, classifications such as “material management”, “gardening”, and “interior” are defined. File classification information is registered in advance by an administrator of the information processing system.

  In the file association information, for example, a display file 531 “manual.html” is associated with a storage file 511 “../data/system/manual.dat”. Here, as described with reference to FIG. 10, the prefix of the display file is omitted, but may be registered with a full path. The file association information is registered when the generation unit 131 generates a display file from the stored file.

  In the file management data 112, the storage file and the display file are associated with each other in the file association information, and the directory of the storage file and the file classification are associated with each other in the file classification information. That is, the file management data 112 indirectly associates the display file with the file classification information through the directory of the stored file. Therefore, the file management data 112 can also be referred to as information that defines the association between the display file and the file classification information.

  FIG. 12 is a diagram illustrating an example of reference history data. The reference history data 113 is stored in the storage unit 110. The reference history data 113 is a record of the number of times the display file is referenced by the user for each day. The history management unit 134 acquires information such as the display file selected by the user, the user ID, and the user's affiliation from the Web service providing unit 120, and records the reference count of each display file. The reference history data 113 is described in the csv format. However, other formats such as XML may be used.

  The reference history data 113 includes, for example, “2011/9/1”, “manual.html”, “30”, “system management section”, “10”, “first system section”, “5”,.・ Is registered. On September 1, 2011, there were 30 references to the display file 531 (file name “manual.html”) from all affiliations, and 10 references from the system management section. This shows that there were five references from the first system section.

  Here, by managing the file management data 112 and the reference history data 113 not by RDB (Relational DataBase) but by csv or XML, it is possible to easily update or refer to each data. Further, for example, the administrator of the file server 100 can easily analyze what kind of file is referred to from what affiliation by referring to the reference history data 113.

  FIG. 13 is a diagram illustrating an example of a search screen. The search screen 600 is generated by the web browser 220 and displayed on the display 206a. The Web browser 220 can acquire the HTML file of the search screen 600 from the Web service providing unit 120 by accessing a predetermined URL (Uniform Resource Locator).

The search screen 600 includes areas 610, 620, and 630.
An area 610 is an area for displaying the directory tree 50. For example, the user can display a list of files arranged in the directory in the area 630 by touching any directory.

  An area 620 is an area for inputting a character string (keyword) to be searched and a search target range. In the area 620, input forms 621, 622, 623 and a search button 624 are provided.

The input form 621 is a text box for inputting a keyword.
The input form 622 is a list box for selecting in-document attributes (such as “document title” and “figure title”) that can include the keyword.

The input form 623 is a list box for selecting a file classification (“system use”, “material management”, etc.) to be searched.
The search button 624 is a button for transmitting a search request to the file server 100 based on information input in the input forms 621, 622, and 623. When there is no input in the input form 622, a search is performed for all the document attributes. When there is no input in the input form 623, a search is performed for all file classifications.

  The user can touch a desired input form to input a character string (or even one character), and to select a document attribute and file classification. The user can make a search request to the file server 100 by touching the search button 624.

  The area 630 is an area for displaying a list of files stored in the directory selected in the area 610. An area 630 is an area for displaying a list of search results when a search result is acquired from the file server 100 after the search button 624 is pressed.

  The search result displayed in the area 630 is a link to each display file. The user can display a display screen 631 that displays the contents of the display file in the area 630 or another window of the Web browser 220 by selecting a link of a desired file from the list of search results. it can. In the example of FIG. 13, the case where the link “manual.html” is selected in the area 630 is illustrated. The Web browser 220 transmits an HTTP request designating the link to the file server 100, and acquires a display file 531 (file name “manual.html”) as a response. Based on the display file 531, the Web browser 220 displays the contents of the file in the display screen 631. The displayed contents are the same as or substantially the same as the contents displayed on the display by executing “manual.dat” by the application on the client 300 (the layout of elements may be slightly different).

  Next, the processing procedure of the file server 100 having the above configuration will be described. First, the procedure of the display file generation process will be described. For example, the file server 100 starts the following processing at a predetermined scheduled time. However, the display file for the stored file may be generated at the timing when the stored file is newly stored (or updated) in the file server 100.

FIG. 14 is a flowchart showing display file generation processing. In the following, the process illustrated in FIG. 14 will be described in order of step number.
(Step S11) The generation unit 131 acquires one unprocessed storage file from the storage unit 110.

  (Step S12) The generation unit 131 determines whether a display file has not been generated for the acquired storage file. If not yet generated, the process proceeds to step S14. If it has been generated, the process proceeds to step S13. For example, the generation unit 131 refers to the file management data 112 stored in the storage unit 110 and can make the determination based on whether or not a display file corresponding to the storage file has been registered in the file association information. If the display file is not registered, the display file has not been generated. If the display file is registered, the display file has already been generated.

  (Step S13) The generation unit 131 determines whether the display file is older than the storage file. If the display file is old, the process proceeds to step S14. If the display file is not old, the process proceeds to step S22. For example, the generation unit 131 can perform the determination by referring to the creation date (or update date) of the display file corresponding to the storage file. If the creation time of the display file is earlier, the display file is older than the storage file. If the creation date of the storage file is in the past, the display file is not old.

  (Step S14) The generation unit 131 reads a storage file and generates a display file. A specific method for generating the display file is as described with reference to FIGS. In other words, the generation unit 131 generates a display file by describing elements included in the storage file and tags according to the positional relationship between the elements. Note that the generation unit 131 may request the application 140 that has a function of converting a file in a predetermined format into an HTML file to generate a display file. The generation unit 131 may generate a display file by adding predetermined tags and attributes to the HTML file generated by the application 140.

  (Step S15) The extraction unit 132 detects a predetermined tag from the display file. For example, the “<title>” tag, the “<table>” tag, the “<caption>” tag, the “<img>” tag, etc., as described above. In addition, attributes such as “title” and “border” included in the tag are detected together with the tag. Further, a “<caption>” tag surrounded by “<table>” tags is detected as a set.

(Step S16) The extraction unit 132 extracts a character string included in the tag detected in step S15 and a keyword included in the attribute in the tag.
(Step S17) The extracting unit 132 registers the extracted character string in the index table 111 in association with the in-document attribute and the display file. The extraction unit 132 determines the in-document attribute according to the tag and the attribute in the tag. For example, in the case of a character string extracted from a “<title>” tag, the in-document attribute is “document title”. For example, in the case of a character string extracted from the “title” attribute in the “<img>” tag, the in-document attribute is set to “figure title”. Which in-document attribute is associated is preset in the extraction unit 132. In addition, when updating the display file, it may be considered that it overlaps with the previously registered index. In that case, only the difference needs to be registered.

  (Step S <b> 18) The generation unit 131 adds a script for executing processing according to the operation in the Web browser 220 to the display file. For example, descriptions 531b and 531f in the display file 531 described with reference to FIG. 8 correspond to the script.

(Step S <b> 19) The generation unit 131 adds a script for shaping the display content on the Web browser 220 to the display file.
(Step S20) The generation unit 131 stores the display file in the storage unit 110.

  (Step S21) The generation unit 131 registers the correspondence between the storage file and the display file in the file management data 112. If already registered, step S21 may be skipped and the process may proceed to step S22.

  (Step S <b> 22) The generation unit 131 determines whether or not all stored files stored in the storage unit 110 have been processed. If all stored files have been processed, the process ends. If there is an unprocessed storage file, the process proceeds to step S11.

  In this way, the generation unit 131 generates a display file from the stored file. The extraction unit 132 extracts a character string from the display file based on the tag included in the display file and registers it in the index table 111.

FIG. 15 is a flowchart showing the file search process. In the following, the process illustrated in FIG. 15 will be described in order of step number.
(Step S <b> 31) The web browser 220 generates a search request based on the content input in the area 620 of the search screen 600 and transmits it to the web service providing unit 120. The web service providing unit 120 receives a search request from the web browser 220. The search request includes information such as user ID, user affiliation, search keyword, document attribute, file classification, and the like. The Web service providing unit 120 outputs the acquired search request to the search unit 133.

  (Step S32) The search unit 133 searches the index table 111 based on the information included in the search request. For example, when the search request includes the search keyword “procedure” and the in-document attribute “table title”, the index table 111 is searched for a record including the character string “procedure” and having the in-document attribute “table title”. Then, the display file “manual.html” included in the record is specified.

  (Step S33) The retrieval unit 133 determines whether any display file has been identified (whether there has been a hit). If there is no hit, the process proceeds to step S34. If there is a hit, the process proceeds to step S36.

(Step S <b> 34) The search unit 133 outputs no hit to the Web service providing unit 120.
(Step S <b> 35) The Web service providing unit 120 transmits a result page for displaying no hit file to the Web browser 220 as a response to the search request. Then, the process ends.

  (Step S36) The search unit 133 determines whether or not the file classification is accepted in the search request. If the file classification is accepted, the process proceeds to step S37. If the file classification has not been received, the process proceeds to step S38.

  (Step S37) The search unit 133 refers to the file management data 112 and narrows down search results by file classification. For example, when the search request includes the file classification “system use”, the display file hit in step S33 is identified as the directory in which the corresponding storage file is stored belongs to the file classification “system use”. To do.

  (Step S38) The search unit 133 refers to the reference history data 113 and sorts the display files included in the search results (results after narrowing down when narrowed down by file classification) by the number of times of reference. For example, display files having the maximum total number of times of reference for the day are arranged in order from the top. Further, for example, the reference count of the user's affiliation unit may be acquired and sorted. For example, the higher the number of references from the affiliation to which the user belongs, the higher the order. Which method is used for sorting is preset in the search unit 133 by the administrator. Further, it is not necessary to perform sorting. In that case, it is only necessary to skip this step and proceed to step S39.

(Step S39) The search unit 133 outputs the result sorted in step S38 to the Web service providing unit 120.
(Step S40) As a response to the search request, the Web service providing unit 120 transmits a result page for displaying the search result of the search unit 133 to the Web browser 220.

  (Step S41) The web browser 220 displays the result page (for example, the contents of the area 630 of the search screen 600) on the display 206a. When the web browser 220 receives a touch operation for selecting one of the display files, the web browser 220 requests the display file from the web service providing unit 120. The web service providing unit 120 receives the selection of the display file by receiving the request.

  (Step S <b> 42) The web service providing unit 120 acquires the display file selected from the storage unit 110 and transmits it to the web browser 220. The web browser 220 displays the content of the display file on the display 206a (for example, the content of the display screen 631).

  (Step S <b> 43) The Web service providing unit 120 outputs information indicating the selected display file, information indicating a user ID, user affiliation, and the like to the history management unit 134. The history management unit 134 updates the reference history data 113 based on the received information. For example, when a user belonging to the system management section selects “Manual.html” on September 1, 2011, 1 is added to the number of references from all positions and the number of references from the system management section.

  In this way, the search unit 133 performs file search. At this time, the search unit 133 accepts in-document attributes and file classifications as search keywords, thereby enabling a detailed file search. The user can efficiently search for a desired display file using the client 200, and can easily browse the contents of the file.

  Here, the client 200 can perform various controls by a script described in the display file. Next, the control of the client 200 that can be realized by a script will be exemplified.

  FIG. 16 is a diagram illustrating an example of client control using a display file. FIG. 16A shows display shaping control in accordance with the display capability of the display 206a of the client 200. FIG. For example, in accordance with the number of pixels of the display 206a, it is possible to control to change definitions (style sheets) such as element size, element color, element layout, and line feed position of text.

  FIG. 16B shows control of animation when the display is changed. For example, it is possible to control screen scrolling animation according to a user's flick operation on the touch panel 207a and screen enlargement / reduction animation according to a pinch out / pinch in operation.

  FIG. 16C shows downloading of the storage file. For example, when a tap operation on a predetermined position of the display file is received by the touch panel 207a, the storage file corresponding to the display file can be downloaded from the file server 100. Thereby, the user can not only browse the display file but also store the original storage file of the display file in the client 200. More specifically, “manual.dat” can be stored in the storage unit 210 while browsing the contents of “manual.html” with the Web browser 220.

  As described above, the file server 100 generates a display file in HTML format based on the stored file. When a tag indicating an element in the storage file is described in the display file, a predetermined tag or attribute is added so that a title related to the element or a character string included in the element can be identified. Then, a character string is extracted based on the tag included in the display file to create an index. For this reason, a detailed index can be created as compared with the case of extracting a character string from a storage file. Specifically, an index is created by adding an in-document attribute to a character string extracted based on a tag or an attribute in the tag. For this reason, the display file can be searched with the set of the keyword and the in-document attribute of the keyword. Therefore, for example, a detailed search such as a title of a figure or a character string included in a table can be efficiently performed.

In addition, by using a tag when creating the index table 111, it is possible to prevent the user from creating additional information. Therefore, labor saving of work by the user can be achieved.
Further, a display file is generated in the HTML format. For this reason, if the display file is transmitted to the client 200, the contents of the display file can be browsed using the Web browser 220.

  Here, since the client 200 is a mobile terminal device, it may be difficult for the client 200 to run an application that can run on the laptop client 300. In this case, even if the original storage file is provided to the client 200, it may be difficult to view the contents of the storage file.

  On the other hand, even a mobile terminal device can often be used with a Web browser. Therefore, the file server 100 provides the display file generated in the HTML format or the like to the client 200, so that the client 200 can easily view the contents of the file. In the second embodiment, the display file is generated in the HTML format, but another format may be used. For example, you may produce | generate with the file of XML format and XSL (eXtensible Stylesheet Language) format.

In this way, the file server 100 can support efficient file search.
As described above, the file management program, the information processing apparatus, and the file management method according to the present invention have been described based on the illustrated embodiments. Can be substituted. Moreover, other arbitrary structures and processes may be added. Further, any two or more configurations (features) of the above-described embodiments may be combined.

DESCRIPTION OF SYMBOLS 1 Information processing apparatus 1a Storage means 1b Generation means 1c Search means 2 First file 2a, 2b Element 3 Second file

Claims (9)

Obtaining a first file stored in a storage means to generate a second file including one or more tags corresponding to one or more elements included in the first file; Alternatively, one or more character strings included in the second file are extracted based on more tags, the second file and the extracted character strings are associated with each other and stored in the storage unit,
When a character string is input, the second file corresponding to the input character string is searched with reference to the storage means, and a search result is output.
A file management program that causes a computer to execute processing. When extracting a character string, a tag including the character string is detected, attribute information corresponding to the tag is determined, and stored in the storage unit in association with the second file and the extracted character string. ,
When attribute information is input together with a character string, the second file corresponding to the input character string and attribute information is searched with reference to the storage means.
The file management program according to claim 1.   The file management program according to claim 2, wherein when determining the attribute information, the attribute information corresponding to a tag including the character string and an attribute in the tag is determined.   The file management program according to any one of claims 1 to 3, wherein when the second file is generated, information indicating a storage location of the first file is added to the second file.   When generating the second file, the second tag is enclosed in a first tag indicating the first element based on the positional relationship between the first element and the second element included in the first file. The file management program according to any one of claims 1 to 4, wherein information on the second element is included in the second tag or a predetermined attribute in the first tag. The storage means stores file classification information that associates the classification to which the second file belongs,
When a character string and a classification are input, the search result is narrowed down by the input classification based on the file classification information stored in the storage means.
The file management program according to any one of claims 1 to 5.   The file management program according to any one of claims 1 to 6, wherein the second file is a file whose contents can be browsed by a web browser. Obtaining a first file stored in a storage means to generate a second file including one or more tags corresponding to one or more elements included in the first file; Alternatively, one or more character strings included in the second file are extracted based on more tags, and the second file and the extracted character strings are associated with each other and stored in the storage unit. Means,
When a character string is input, search means for searching the second file corresponding to the input character string with reference to the storage means, and outputting a search result;
An information processing apparatus. A file management method executed by a computer,
Obtaining a first file stored in a storage means to generate a second file including one or more tags corresponding to one or more elements included in the first file; Alternatively, one or more character strings included in the second file are extracted based on more tags, the second file and the extracted character strings are associated with each other and stored in the storage unit,
When a character string is input, the second file corresponding to the input character string is searched with reference to the storage means, and a search result is output.
File management method.

Images