JP2009104392A - File management system, file management method and file management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a file management system and the like by which relevant file candidates are list-displayed in the case of performing file processing and also access addresses to associated information in other systems are list-displayed. <P>SOLUTION: The file management system 1 provided with a file management server 10 and a client terminal 20 is provided with: also an access log information database 130 for storing information concerned with history that a user accesses a file 120 managed by the file management server 10 from the client terminal 20; an association information creation processing part 170 for associating other files updated by the same user within a prescribed period from a file updating date as associated files and generating association information among the files; an association information database 140 for storing the association information; and an association information management part 160 for outputting the association information to the client terminal 20. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a file management system that manages files via a network, and more particularly to a file management system that performs file management using file association.

  A file management system including a server for managing files and a client connected via a network is generally known. The client and server communicate with each other using HTTP (HyperText Transfer Protocol). When a specific URL (Uniform Resource Locator) is specified by the client, a copy of the corresponding file in the server is sent to the client, and the client side Work such as editing can be performed. When editing on the client is completed, a copy of the updated file is sent to the server and stored in the storage location of the server. When accessing a file, a history including the worker and operation time is left as access log information, and it is possible to confirm when and who edited which file. With such a system, a common file can be centrally managed by a plurality of clients, and efficient file management can be performed. However, for example, when it is desired to simultaneously edit a related file when editing a certain arbitrary file, if the number of files being managed is enormous, it will be a difficult task.

  Therefore, as a technique for solving the above problems, a technique disclosed in Patent Document 1 is disclosed. The technique shown in Patent Document 1 is a technique related to file transfer. At the time when it is desired to transfer the file, it is determined whether or not the recently used file can be edited by an application existing in the computer, and the file is edited. The transfer candidate file is determined as necessary or when the user determines that it is necessary. Further, it is a technique for reading a directory structure on a file system in which transfer candidate files are stored, searching for a file having an update date or access date close to the transfer candidate file, and setting the file as a transfer candidate file.

The technique of Patent Document 2 uses a WEB access history on the client side. When a “link list” is requested by a user's input operation using an input device in a client computer, display management is performed. When the link list setting dialog is displayed on the display device by the unit, and a URL indicating an arbitrary HTML file is set in the link display file setting field in the dialog, the list management unit in the processing unit displays the HTML file indicated by the URL Are acquired by the network management unit or the document management unit, and the file is analyzed by the HTML analysis unit to be combined into one structure indicating the link list. The display management unit is a technique for displaying a link list that shows the link relation of the corresponding file in a hierarchical structure based on the link list structure.
Japanese Patent No. 3457502 JP-A-9-185634

  However, the technique disclosed in Patent Document 1 transfers a file to be updated to the latest information (file accessed after the date and time specified by the user) from the information of the access history to the file, and between files. Since this is not a technique for selecting only the necessary files as candidates, it has a problem that it cannot cope with the case where it is necessary to consider the relationship between files.

  In addition, since a file existing in the entire directory tree under the N number of parent directories is a candidate file, there is a problem that file association in another system cannot be performed. In other words, for example, work performed in the business flow may be work on a data management tool constructed by a Web application or the like instead of file correction. In such work, association is performed to improve processing efficiency. I can't.

  The technique shown in Patent Document 2 has a problem that since the HTML file is analyzed from the information of the WEB access history to structure the relevance, it is necessary to analyze the contents of the file, and the processing becomes complicated.

  Therefore, the present invention has been made to solve the above-described problem, and when a user performs a predetermined process on an arbitrary file, a list of related file candidates is displayed in addition to other candidates. It is an object of the present invention to provide a file management system, a file management method, and a file management program that display a list of access destinations of related information in the system.

(1. Display of related file information)
A file management system according to the present invention is a file management system comprising a server that manages a plurality of files, and a client terminal that accesses and processes a plurality of files managed by the server via a network. An access log information database for storing access log information related to a history of access to a plurality of files managed by the server from the client terminal, and any user updated based on the access log information Result of extracting another file updated by the same user within a predetermined period starting from the update date and time of one file and associating the other file as a related file of the arbitrary one file related to the user As the association information between the files The associated information creating means, the associated information database storing the associated information generated by the associated information creating means, and the user updating the one arbitrary file in response to a request from the client terminal. The association information management means for outputting the association information related to the arbitrary one file stored in the association information database to the client terminal.

  As described above, in the present invention, when a user updates an arbitrary file, another file that is being accessed at the time of updating the file is extracted based on the access log information, and the related file is extracted. Since it can be displayed and presented to the user, it is possible to prevent the user from forgetting to process another file due to lack of skill or misunderstanding of the user.

  In addition, depending on the user, other files that are considered to be related to any one file are displayed as related files, so only the files that are considered necessary for the user are displayed. Efficiency can be improved.

  Furthermore, regardless of the management method of a plurality of files managed by the server, files related to any one file can be easily extracted and displayed according to the user. Any file can be associated without limitation.

  Furthermore, by displaying the storage location of the file related to any one file, the user can easily access the related file, so the work can be performed efficiently.

  Furthermore, since the association between files is based on the access log information, there is no need to analyze or analyze the contents of the file, and only the access log information needs to be analyzed. Processing efficiency can be increased.

(2. Display of related file information based on schedule information)
In the file management system according to the present invention, when the update date / time of the arbitrary file is biased to a specific date / time or when the date / time is based on a predetermined regularity, A schedule information database for storing schedule information for management, wherein the association information creating means generates an update schedule of the arbitrary one file as schedule information, and the association information management means is controlled by the user; Association information stored in the association information database and / or the schedule information when the arbitrary file is updated by a request from the client terminal or when authentication to the server is performed. Output the schedule information stored in the database to the client terminal And wherein the door.

  Thus, in the present invention, when the user updates a specific file at a specific date and time based on the access log information, the user can be prompted to update the file at the specific date and time. It has the effect of preventing forgetting.

(3. Display of related information in other systems)
The file management system according to the present invention stores URL history information accessed from the client terminal in synchronization with the update operation of the arbitrary one file based on the update date and time of the arbitrary one file. Related display information generation means for generating related display information by merging history database, history information stored in URL history database, association information output by said association information management means, and / or schedule information And associated information display means for displaying the associated display information generated by the associated display information generating means.

  As described above, in the present invention, a related file related to an arbitrary file can be displayed, and related information in another system can also be displayed from the history information of the URL accessed by the client terminal. This has the effect of preventing the user from forgetting the work when the work needs to be performed across different systems.

  In some cases, it is difficult to link different systems, but by using URL history information, work between different systems can be easily realized, and work efficiency can be improved.

  Note that the history information stored in the URL history database may be separately provided with a dedicated display processing unit, and may be displayed separately from the associated information and schedule information. In this case, the related display information generating means generates related display information by merging only the association information and / or schedule information.

(4. Editing related information)
The file management system according to the present invention is such that the user can edit association information stored in the association information database and / or schedule information stored in the schedule information database. Features.

  As described above, in the present invention, since the user can edit the association information and / or schedule information, the user determines whether or not there is relevance, and the database stores each information. Information can be deleted or added. Therefore, the user can improve the work efficiency by editing the system so that the user can easily use it, and also has an effect that the work can be eliminated and the work can be executed reliably.

  So far, the present invention has been shown as a system. However, as will be apparent to those skilled in the art, the present invention can be understood as an apparatus, method, and program. These outlines of the invention do not enumerate the features essential to the present invention, and a sub-combination of these features can also be an invention.

  Embodiments of the present invention will be described below. The present invention can be implemented in many different forms. Therefore, the present invention should not be construed based only on the description of the present embodiment. Also, the same reference numerals are given to the same elements throughout the present embodiment.

  In the following embodiments, the system will be mainly described. However, as will be apparent to those skilled in the art, the present invention can also be implemented as an apparatus, a method, and a program for operating a computer. In addition, the present invention can be implemented in hardware, software, or hardware and software embodiments. The program can be recorded on any computer-readable medium such as a hard disk, CD-ROM, DVD-ROM, optical storage device, or magnetic storage device. Furthermore, the program can be recorded on another computer via a network.

(First embodiment of the present invention)
(1. Configuration and function)
(1-1 System configuration and function of file management system)
FIG. 1 is a system configuration diagram of a file management system according to the present embodiment. The file management system 1 includes a file management server 10 and a client terminal 20, and each computer is connected via a network 40 and can communicate with each other.
The file management server 10 performs processing for managing a plurality of files shared by a plurality of clients.
The client terminal 20 is a terminal used by each user, and can access, refer to, and update a file managed by the file management server 10.

(1-2 File management system module configuration and functions)
FIG. 2 is a module configuration diagram of the file management system according to the present embodiment. The file management server 10 includes a Web server 30, a server program 110, a file 120, an access log information database 130, an association information database 140, a schedule information database 150, an association information management unit 160, and an association And an information creation unit 170. The client terminal 20 includes a browser 210, a browser engine 220, a client program 230, an associated information display unit 250, and a file editing tool 260.

  The Web server 30 determines the storage location of the corresponding file 120 based on the URL requested from the client terminal 20, acquires it from the file management server 10, and transmits it to the client terminal 20 using HTTP.

As shown in FIG. 2, the file management server 10 and the Web server 30 can be provided by the same physical server.
The server program 110 is a program that performs processing for writing information related to access to the file 120 into the access log information database 130.

  The file 120 is a file managed by the file management server 10 and is shared by a plurality of clients. If the file 120 is formally authenticated as a user, anyone can access it.

  The access log information database 130 is a database in which information related to access to the file 120 is stored. Specifically, the authenticated user, the time and date of operation, and information (operation, file path, etc.) regarding the accessed file 120 are stored.

Here, the access log information will be described in detail. FIG. 3 is a diagram illustrating an example of access log information. From the left column, it consists of the access date, access user, operation, file path, and remarks. The access date and time is the date and time when the file 120 was accessed, the access user is the name of the user who accessed the file 120 (or user ID), and the operation is the content of the operation performed on the accessed file 120 by the user. Yes, the file path is the path and file name of the file 120 accessed by the user, and the remarks are additional information regarding the file 120 accessed by the user. These pieces of information are stored in the access log information database 130 by the server program 110.
Note that FIG. 3 is merely an example, and it is naturally possible to add, change, and delete items as necessary to have different configurations.

  Referring back to FIG. 2, the association information database 140 is an arbitrary one file that is processed by the user among the plurality of files 120, the arbitrary one file, and other files related to the arbitrary one file. This is a database in which information such as a URL indicating the storage location is stored. The association information has information for each arbitrary file in the user.

Here, the association information will be described in detail. FIG. 4 is a diagram illustrating an example of association information. From the left column, the related No. , Related file name and URL. Related No. Is an item number of the related information, and the item number is assigned with a series of related information as one item. The related file name is a name of a related file, and the URL is a URL indicating a storage location of the related file. For example, if the user When processing is performed by accessing txt, any file 1. Other files related to txt are file 2. txt and file 3. It shows that it is txt.
Note that FIG. 4 is merely an example, and it is naturally possible to add, change, and delete items as necessary to have different configurations.

Returning to FIG. 2, the schedule information database 150 is a database that stores, as schedule information, processing that the user seems to perform at a specific date and time.
Here, the schedule information will be described in detail. FIG. 5 is a diagram illustrating an example of schedule information. From the left column, access user, schedule date, related No. It consists of The access user is a user name (or user ID) that accesses the file, and the schedule date is the date on which the process is performed. Is related No. in FIG. It is. From the access log information in FIG. 3, the user 1 has a \ folder 1 \ folder 2 \ file 1. It can be seen that txt is updated. This information is stored in the schedule information database 150 as schedule information. That is, FIG. 5 shows that the user No. That is, the file group included in 1 is processed.

  Note that FIG. 4 is merely an example, and it is naturally possible to add, change, and delete items as necessary to have different configurations. For example, the schedule date item may be a schedule time or a schedule month. Moreover, the end of the month and the day of the week can be set in the schedule date item. Furthermore, related No. The item may be a file path.

  Returning to FIG. 2, the association information management unit 160 receives a request for related information from the client terminal based on the file 120, the access log information database 130, the association information database 140, and the schedule information database 150. In addition, it is a processing unit that acquires association information and outputs it to a client terminal, or performs management such as determination of whether the acquired information is a target of association.

  Based on the access log information database 130, the associated information creation unit 170 performs a process of creating the associated information database 140 and the schedule information database 150 from regularity such as file update timing, update timing, and user.

The browser 210 cooperates with the browser engine 220 to perform processing for extracting and displaying information stored in the location indicated by the specified URL of the file management server 10.
The client program 230 performs processing for displaying association information and starting the file editing tool 260 to open the file 120 acquired from the file management server 10.

The association information display unit 250 performs processing for displaying association information and / or schedule information. When the user saves the updated file 120 and ends the file editing tool 220, the client program 230 detects it. In response to the detection, processing for displaying associated information and / or schedule information is performed.
The file editing tool 260 is a tool used for editing the file 120.

(1-3 Hardware configuration of computer used in file management system)
FIG. 6 is a hardware configuration diagram of a computer used in the file management system according to the present embodiment. A computer 2 used in the file management system 1 includes a CPU (Central Processing Unit) 601, a RAM (Random Access Memory) 602, a ROM (Read Only Memory) 603, a flash memory (Flash memory) 604, and an HD (external storage device) Hard disk) 605, LAN (Local Area Network) card 606, mouse 607, keyboard 608, video card 609, display 609a which is a display device electrically connected to the video card 609, sound card 610, and sound card 610 It comprises a speaker 610a, which is an electrically connected sound output device, and a drive 611 that reads and writes a storage medium such as a flexible disk, CD-ROM, and DVD-ROM.

Of course, the hardware components can be changed, and in particular, the file management server 10 is composed of high-spec components in order to enable simultaneous access from a large number of client terminals 20. It is common to use a high performance computer.
The file management server 10 can also be constructed by a plurality of computers.

(2. Operation)
The operation of the file management system 1 according to this embodiment will be described below.

(2-1 Write access log information)
FIG. 7 is a flowchart showing a process of writing access log information. First, of the files 120, an arbitrary file requested by the user (hereinafter referred to as user 1) (hereinafter referred to as file A) is transmitted to the client terminal 20 via the Web server 30 (step S1). S701). In the client terminal 20, the user 1 performs an update process on the file A and ends the file editing tool 260. At this time, the file A is transmitted from the client terminal 20 to the file management server 10, and the Web management server 30 receives the file A (step S702). The received file A is stored in the storage location of the file 120 on the file management server 10, information that the user 1 has accessed the file A is written in the access log information database 130 (step S703), and the access log information The writing process is terminated.

(2-2 Generation of related information)
FIG. 8 is a flowchart showing processing for generating association information. First, in order to write association information, the association information database 140 is read (step S801). Next, the access log information database 130 is read (step S802). Starting from the date and time when the user 1 updated the file A in the past, it is determined whether there is information in the access log information database 130 that accessed another file for a certain period (step S803). The attached information generation process is terminated. If there is, the association information is written in the association information database 140 read in step S801 (step S804), and the association information generation process is terminated.

(2-3 Generation of schedule information)
FIG. 9 is a flowchart showing processing for generating schedule information. First, in order to write schedule information, the schedule information database 150 is read (step S901). Next, the access log information database 130 is read (step S902). It is determined whether information on an arbitrary file whose access date / time is biased to a specific date / time or information accessed at a date / time based on a predetermined regularity is in the access log information database 130 (step S803). If not, the schedule information generation process ends. If there is, the schedule information is written into the schedule information database 150 read in step S901 (step S904), and the schedule information generation process is terminated.

(2-4 Display of related information and / or schedule information)
FIG. 10 is a flowchart showing processing for displaying association information and / or schedule information. First, the association information database 140 is read (step S1001), and the schedule information database 150 is read (step S1002). It is determined whether or not there is information related to the updated file A in the association information database 140 and / or the schedule information database 150 (step S1003). If there is information related to the file A, URL list information indicating the storage location of other related files is transmitted to the client terminal 20 (step S1004). The client terminal 20 receives the URL list information transmitted from the file management server 10 (step S1005), calls the association information display unit 250, displays the URL list (step S1006), and ends the processing. To do.

(2-5 Specific examples of displaying related information and / or schedule information)
FIG. 11 is an example of a display screen for related information. As shown in the figure, when the user 1 updates an arbitrary file A, a list of files considered to be related is displayed. FIG. 12 is an example of a schedule information display screen. As shown in the figure, a list of files that the user 1 is supposed to access a specific file (file group) at a specific date and time is displayed. As described above, the user 1 can refer to a list of URLs indicating the storage locations of other files that are considered to be related to the file A at the time when the file A is updated. At the end of the month, a list of URLs indicating the storage locations of files that are supposed to be accessed can be referenced. That is, it is possible to prevent forgetting the process for the file that needs to be accessed at the timing of updating the file A and the process for the file that needs to be accessed at a specific date and time.

  Each URL can be selected with a mouse or a keyboard, and the selected file may be opened by clicking the mouse or pressing ENTER in the selected state.

(Second embodiment of the present invention)
(1. Configuration and function)
(1-1 System configuration and function of file management system)
FIG. 13 is a system configuration diagram of the file management system according to the present embodiment. The file management system 1 includes a file management server 10, a client terminal 20, and another system server (group) 10a. Each computer is connected via a network 40, and can communicate with each other.
The other system server 10a is a server constituting a system other than the file management system, and can also be regarded as a server group.
Since the functions of the file management server 10 and the client terminal 20 are the same as those in the first embodiment, description thereof is omitted.

(1-2 File management system module configuration and functions)
FIG. 14 is a module configuration diagram of the file management system according to the present embodiment. The difference from the first embodiment is that the client terminal 20 includes a related display information generation processing unit 240, a URL history database 270, and a URL access history database 280, and displays the other system information 50 of the other system server 10a. Browser function is added.

  The related display information generation processing unit 240 merges the information stored in the URL history database 270 provided in the client terminal 20 with the related information and / or schedule information transmitted from the file management server 10 and Processing for generating display information is performed. Then, the associated information display unit 250 displays the related display information generated by the related display information generation processing unit 240.

  The URL history database 270 has the same timing when accessing any file of the file 120 of the file management server 10 among the URL information indicating the storage location of the other system information 50 of the other system server 10a accessed by the client terminal 20. This is a database that stores URL information indicating the storage location of the other system information 50 that is being accessed.

  The URL access history database 280 is a database that stores URL information indicating the storage location of the other system information 50 accessed by the client terminal 20 in the other system server 10a.

  The URL history database 270 may be stored while accumulating the same information as the information stored in the URL access history database 280. That is, the information stored in the URL access history database 280 may be deleted when a predetermined operation of the client terminal is performed. For this reason, the information needs to be accumulated in the URL history database 270.

  Here, the URL information stored in the URL history database 270 will be described in detail. FIG. 15 is a diagram illustrating an example of URL access information to another system. From the left column, it consists of access date, title, and Internet address. The access date and time is the date and time of access, the title is the title of the other system information 50, and the Internet address is a URL indicating the storage location of the accessed information. These pieces of information are automatically acquired by the OS (Operating System) of the client terminal 20 and stored in the URL access history database 280. Then, it is copied and stored in the URL history database 270 at a predetermined timing.

  Returning to FIG. 14, the associated information display unit 250 performs processing for displaying the associated information and / or schedule information as in the first embodiment, but the related display information generation processing unit 240 performs the related display information. Is generated, the related display information is displayed.

  Since the configuration and functions of the file management server 10 are the same as those in the first embodiment, description thereof will be omitted. The configurations and functions of the browser 210, the browser engine 220, and the file editing tool 260 are also the same as those in the first embodiment, and a description thereof will be omitted.

  In addition, the client program 230 is configured to newly include a URL history display processing unit. In addition to the URL list information displayed by the association information display unit 250 transmitted from the file management server 10, the URL history display processing unit includes: The corresponding URL history information in the URL history database 270 may be displayed.

(1-3 Hardware configuration of computer used in file management system)
Since the hardware configuration of the computer used in the file management system according to this embodiment is the same as that of the first embodiment, description thereof is omitted.

(2. Operation)
The operation of the file management system 1 according to this embodiment will be described below. Since the process of writing access log information, the process of generating association information, the process of generating schedule information, and the process of displaying association information and / or schedule information are the same as in the first embodiment, the description will be given. Omitted.

(2-1 Generation of related display information)
FIG. 16 is a flowchart illustrating a process of generating related display information. First, when the URL list information transmitted from the file management server 10 is received (pointing to the process of step S1005 in FIG. 10), the URL history database 270 is read (step S1601). Starting from the date and time when the file A was updated, it is determined whether there is information accessed by the same user 1 as the user who updated the file A within a certain period (step S1602). Exit. If there is, the URL indicating the storage location of the accessed information is added to the received URL list information (step S1603), and the related display information generation processing is terminated.

(2-2 Example of display of related display information)
FIG. 17 is an example of a display screen of related display information based on the association information. As shown in the figure, when the user 1 updates an arbitrary file A, the other system information 50 accessed at the same timing is displayed together with a list of files considered to be related. FIG. 18 is an example of a display screen of related display information based on schedule information. As shown in the figure, a list of files that the user 1 is supposed to access a specific file (file group) at a specific date and time, and other system information 50 accessed at the same timing as that file are displayed. As described above, the user 1 can refer to a list of URLs indicating the storage locations of other files that are considered to be related to the file A at the time when the file A is updated. At the end of the month, a list of URLs indicating the storage locations of files that are supposed to be accessed can be referenced, and a list of URLs indicating the storage locations of other system information 50 accessed at the same timing can be referenced. . In other words, by coordinating with other systems, wider and more reliable processing can be performed.

  Each URL can be selected with a mouse or a keyboard, and the selected file may be opened by clicking the mouse or pressing ENTER in the selected state.

(Other embodiments)
(1. Editing related information and / or schedule information)
FIG. 19 is an example of a screen for editing association information and / or schedule information. When a selection button 191 in the figure is pressed, another window for selecting a file is opened, and a file to be added as a related file is selected there. At this time, if the URL indicating the storage location of the file is known, the display unit 190 may be directly written. When a file displayed on the display unit 190 is added as a related file, when an add button 192 is pressed, association addition request information is transmitted to the Web server 30, and the association information management unit 160 associates the corresponding file with the association file. The information is added to the information database 140 or the schedule information database 150. The added file is displayed in the list of FIG.

In addition, when it is desired to delete a file already associated as a related file, when the delete button 193, 194, 195 displayed next to the corresponding file is pressed, the association deletion request information is transmitted to the Web server 30, The association information management unit 160 deletes the corresponding file from the association information database 140 or the schedule information database 150. The deleted file is deleted from the list of FIG. Further, when it is desired to delete access information (Internet 1) to another system, when the delete button 196 is pressed, the information is deleted from the list of FIG. At this time, when the related display information generation processing unit 240 generates the related display information, it is set so as to exclude the Internet 1 and generate it.
Note that a file once deleted may not be automatically associated.

(2. Pattern setting for multiple related files)
When a plurality of files are associated with the file A of the user 1, priority is set, and association information and / or schedule information is displayed based on the priority. The priority can be set variously, for example, the access order, the access frequency, the length of one access, and the like.

As described above, according to the present embodiment, the user can improve the work efficiency by editing the association information and / or the schedule information so that the user can easily use the work, and the work is prevented from being leaked and the work is reliably executed. can do.
Note that the association information and schedule information in each of the above embodiments can be shared by a specific group.

  Further, the association information may be generated from the order of the accessing user in addition to the generation from the access order of the files. For example, if there is access log information that has been accessed in the order of user 2, user 3, and user 1 for file A, and file A is accessed in the order of user 2 and user 3 The user 1 is caused to display the file A as a related file. In such a case, if the user 1 has not accessed the file A even after a predetermined time has elapsed, a warning message that prompts the user 1 to access the file A may be displayed. .

  Although the present invention has been described with the above embodiments, the technical scope of the present invention is not limited to the scope described in the embodiments, and various modifications or improvements can be added to these embodiments. . And embodiment which added such a change or improvement is also contained in the technical scope of the present invention. This is apparent from the claims and the means for solving the problems.

(3. Appendix)
Regarding the above embodiment, the following additional notes are disclosed.
(Appendix 1) A file management system according to the present invention includes a server that manages a plurality of files, and a client terminal that accesses and processes the plurality of files managed by the server via a network. In the management system, based on the access log information and an access log information database that stores access log information relating to a history of access to a plurality of files managed by the server from the client terminal, the user Extracting another file updated by the same user within a predetermined period starting from the update date and time of any one updated file, and associating the other file as a related file of the one arbitrary file related to the user The results of the Association information generating means generated as information, an association information database storing association information generated by the association information generating means, and the user by means of the request from the client terminal And an association information management unit that outputs association information related to the arbitrary one file stored in the association information database to the client terminal when updated.

  (Supplementary note 2) The file management system according to the present invention is the file management system according to supplementary note 1, wherein the update date and time of the arbitrary one file is biased to a specific date or time based on a predetermined regularity In some cases, a schedule information database for storing schedule information for managing an update schedule of the arbitrary one file is provided, and the association information creating unit uses the update schedule of the arbitrary one file as schedule information. The association information management means generates the association information database when the user updates the arbitrary one file in response to a request from the client terminal or when authentication to the server is performed. Stored association information and / or stored in the schedule information database. Schedule information, and outputs to the client terminal.

  (Supplementary note 3) The file management system according to the present invention is the file management system according to Supplementary note 1 or 2, wherein the file management system is synchronized with the update operation of the arbitrary one file based on the update date and time of the arbitrary one file. A URL history database storing URL history information accessed from the client terminal, history information stored in the URL history database, association information output by the association information management means, and / or schedule The apparatus includes a related display information generation unit that generates related display information by merging information, and an associated information display unit that displays the related display information generated by the related display information generation unit.

  (Supplementary note 4) The file management system according to the present invention is the file management system according to any one of supplementary notes 1 to 3, wherein the association information stored in the association information database and / or the schedule information database The stored schedule information can be edited by the user.

  (Supplementary Note 5) The file management system according to the present invention is the file management system according to Supplementary Note 4, wherein a specific pattern is extracted based on the associated information or schedule information related to the user, and based on the pattern, The association information display means displays the association information or schedule information about the user when the arbitrary file is updated by the user.

  As described above, in the present invention, when there are a plurality of patterns in the association information about the user, the priority of those patterns is set, and the information to be displayed as the association information is selected based on the priority. Therefore, it is possible to preferentially display files with high relevance, and to save the trouble of referring to files with low relevance, thereby improving the efficiency of user operations.

In addition, when the order in which the files are processed is determined, the user only needs to work according to the display order, and the user's work can be made more efficient.
Furthermore, when the association information and the schedule information are shared by the group, information common to the group can be displayed with priority, so that the work efficiency of the entire group can be improved.

Note that the user may be able to edit information related to a specific pattern.
Further, the pattern may be set according to the access frequency and the length of one access time other than the access order to the file.

1 is a system configuration diagram of a file management system according to a first embodiment. FIG. It is a module block diagram of the file management system which concerns on 1st Embodiment. It is a figure which shows an example of access log information. It is a figure which shows an example of association information. It is a figure which shows an example of schedule information. It is a hardware block diagram of the computer used with the file management system which concerns on 1st Embodiment. It is a flowchart which shows the process which writes access log information. It is a flowchart which shows the process which produces | generates association information. It is a flowchart which shows the process which produces | generates schedule information. It is a flowchart which shows the process which displays related information and / or schedule information. It is an example of the display screen of related information. It is an example of a display screen of schedule information. It is a system configuration figure of the file management system concerning a 2nd embodiment. It is a module block diagram of the file management system which concerns on 2nd Embodiment. It is a figure which shows an example of URL access information to another system. It is a flowchart which shows the process which produces | generates relevant display information. It is an example of a display screen of related display information based on related information. It is an example of the display screen of the related display information based on schedule information. It is an example of the screen which edits association information and / or schedule information.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 File management system 10 File management server 10a Other system server 20 Client terminal 30 Web server 40 Network 50 Other system information 110 Server program 120 File 130 Access log information database 140 Associated information database 150 Schedule information database 160 Associated information management part 170 Association information creation unit 210 Browser 220 Browser engine 230 Client program 240 Association display information generation processing unit 250 Association information display unit 260 File editing tool 270 URL history database 280 URL access history database 601 CPU
602 RAM
603 ROM
604 Flash memory 605 HD
606 LAN card 607 Mouse 608 Keyboard 609 Video card 609a Display 610 Sound card 610a Speaker 611 Drive

Claims (6)

In a file management system comprising a server that manages a plurality of files and a client terminal that accesses and processes a plurality of files managed by the server via a network,
An access log information database for storing access log information relating to a history of a user accessing a plurality of files managed by the server from the client terminal;
Based on the access log information, another file updated by the same user within a predetermined period is extracted from the update date and time of any one file updated by the user, and the other file is related to the user. Association information creating means for generating a result of association as an associated file of the arbitrary one file as association information between the files;
An association information database for storing association information generated by the association information creating means;
When the arbitrary file is updated by the user in response to a request from the client terminal, association information related to the arbitrary one file stored in the association information database is stored in the client terminal. A file management system comprising an associated information management means for outputting. The file management system according to claim 1,
Stores schedule information for managing an update schedule of the arbitrary one file when the update date of the arbitrary file is biased to a specific date or time based on a predetermined regularity It has a schedule information database,
The association information creating unit generates an update schedule of the arbitrary one file as schedule information,
The association information management means is stored in the association information database when the arbitrary one file is updated by a request from the client terminal by the user or when authentication to the server is performed. A file management system for outputting associated information and / or schedule information stored in the schedule information database to the client terminal. In the file management system according to claim 1 or 2,
A URL history database storing URL history information accessed from the client terminal in synchronization with the update operation of the arbitrary one file based on the update date and time of the arbitrary one file;
Related display information generating means for generating related display information by combining history information stored in a URL history database, related information output by the related information management means, and / or schedule information;
A file management system comprising: association information display means for displaying related display information generated by the related display information generation means. The file management system according to any one of claims 1 to 3,
The file management system, wherein the user can edit association information stored in the association information database and / or schedule information stored in the schedule information database. In a file management method for managing multiple files,
Based on the access log information related to the history of access to the plurality of files by the user, another date updated by the same user within a predetermined period starting from the update date and time of any one file updated by the user An association information creating step of generating a result of extracting the file and associating the other file as the association file of the arbitrary one file related to the user as association information between the files;
Storing the association information generated in the association information creation step in an association information database;
An association information display step of displaying association information stored in the association information database when the user updates the arbitrary one file. A file management method comprising: In a file management program for operating a computer to manage multiple files,
Based on the access log information related to the history of access to the plurality of files by the user, another date updated by the same user within a predetermined period starting from the update date and time of any one file updated by the user An association information creation procedure for generating a result of extracting a file and associating the other file as an associated file of the arbitrary one file related to the user as association information between the files;
A procedure for storing the association information generated in the association information creation step in an association information database;
A file management program for causing a computer to execute an association information display procedure for displaying association information stored in the association information database when the user updates any one of the files.