JP2007011959A - File management apparatus, method, and control program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a file management apparatus method, and a control program capable of restricting, for each user, a hierarchical structure of files or the like which can be browsed by a user such as a designer and a system administrator, based on access rights. <P>SOLUTION: The file management apparatus includes an input means 21 for acquiring user identification information of a user terminal 20 and a table storage means 14 for associating the user identification information of the user terminal 20 and user attribute information with access rights for files, to be stored. The apparatus also includes an information storage means 15 for storing files used by the user of the user terminal 20 and a control means 12 for reading the access rights for files and the user attribute information corresponding to the user identification information acquired by the input means 11 and 21, from the table storage means 14. The apparatus also includes a display means 16 and 25 for displaying the files stored in the information storage means 15 in a hierarchical structure in accordance with the access rights for files and the user attribute information read by the control means 12. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a file management apparatus, method, and control program for managing files that are transmitted to and received from a plurality of user terminals.

Conventionally, when design information created by a designer is handed over to a person in charge such as a printing company, the design manuscript is sent by post or fax so that the design information is not leaked to a third party via the network. The method of sending was used.
In addition, a technique is known in which files used by a plurality of users are managed by a management server, and electronic data is transmitted from the management server to a user's terminal in response to a request from the user ( Patent Document 1).
Japanese Patent Laid-Open No. 2003-6184

However, in the method of sending design manuscripts by mail, it takes time for the manuscript to be sent to the person in charge of the printing company, so that the person in charge of the printing company cannot start processing quickly. There was a problem. In addition, in the method of sending a manuscript of design by FAX, there is a problem that a person in charge of a printing company or the like cannot electronically process the manuscript of the received design, although there is no time delay in processing.
In addition, in the technique described in Patent Document 1, even if other users' files cannot be browsed, the file names of other users can be browsed. There was a problem that it was possible to guess from the file name etc.
In particular, if the person in charge has to exchange files with multiple customer companies and multiple designers, it is preferable from the viewpoint of protecting privacy information and corporate confidentiality that even folder names and file names are exposed to other companies. It is obvious that it is not a thing.

  The present invention has been made to solve the above-described problems, and its purpose is to limit the hierarchical structure of files and the like that can be browsed by a user such as a designer and a system administrator for each user based on usage rights. It is an object to provide a file management apparatus, a method, and a control program.

  The present invention has been made to solve the above problems, and the invention according to claim 1 is a file management apparatus for managing a file to be transmitted to and received from a terminal, the user of the terminal Input means for acquiring the identification information of the terminal, first storage means for storing the identification information of the user of the terminal and the attribute information of the user, and the right to use the file in association with each other, and the file used by the user of the terminal Second storage means for storing, a first control means for reading out the authority to use the file corresponding to the user identification information acquired by the input means and the attribute information of the user from the first storage means, Display means for displaying a file stored in the second storage means in a hierarchical structure in accordance with the authority to use the file read by the first control means and the attribute information of the user; It is a file management apparatus, characterized in that it comprises.

  Further, in the invention according to claim 2, deletion information indicating that a deletion instruction has been input from the terminal for each file stored in the second storage means is used as identification information of the user of the terminal. For the third storage means for storing the information in association with the user identified by the identification information of the user of the terminal whose deletion information is stored in the third storage means, the display means For the user specified by the identification information of the user of the terminal that does not display the file in which the instruction is input and the deletion information is not stored in the third storage unit, the display unit instructs the deletion 2. The file management apparatus according to claim 1, further comprising: a second control unit that displays a file in which is input.

  The invention according to claim 3 is a file management method for managing a file to be transmitted to and received from a terminal, the first step of acquiring identification information of a user of the terminal, and the terminal A second step of storing the identification information of the user and the attribute information of the user in association with the use authority of the file, a third step of storing the file used by the user of the terminal, and the first step A fourth step of reading out the file use authority and the user attribute information corresponding to the user identification information obtained in the step from the file use authority and the user attribute information stored in the second step; According to the usage authority of the file read in the fourth step and the attribute information of the user, the file stored in the third step is hierarchically structured. Is a file management method characterized in that it comprises a fifth step Shimesuru.

  According to a fourth aspect of the present invention, for each file stored in the third step, deletion information indicating that a deletion instruction is input from the terminal is associated with identification information of a user of the terminal. For the sixth step to be stored and the user specified by the identification information of the user of the terminal that has stored the deletion information in the sixth step, the deletion instruction is input in the fifth step For the user specified by the identification information of the user of the terminal that does not display the file and does not store the deletion information in the sixth step, the deletion instruction is input in the fifth step The file management method according to claim 3, further comprising a seventh step of displaying the file.

  According to a fifth aspect of the present invention, there is provided a control program for controlling a file management apparatus for managing a file transmitted / received to / from a terminal, wherein the identification information of the user of the terminal is acquired. A second step of storing the identification information of the user of the terminal and the attribute information of the user in association with the authority to use the file, and a third step of storing the file used by the user of the terminal The file use authority and the user attribute information corresponding to the user identification information acquired in the first step, and the file use authority and the user attribute information stored in the second step. According to the fourth step to be read, the authority to use the file read in the fourth step, and the attribute information of the user, the third step is performed. Tsu is a control program for controlling the file management apparatus, characterized in that it comprises a fifth step of displaying a hierarchical structure file stored in up.

  Further, in the invention described in claim 6, deletion information indicating that a deletion instruction is input from the terminal is associated with identification information of the user of the terminal for each file stored in the third step. For the sixth step to be stored and the user specified by the identification information of the user of the terminal that has stored the deletion information in the sixth step, the deletion instruction is input in the fifth step For the user specified by the identification information of the user of the terminal that does not display the file and does not store the deletion information in the sixth step, the deletion instruction is input in the fifth step 7. A control program for controlling a file management apparatus according to claim 5, further comprising a seventh step of displaying a file.

In the present invention, the hierarchical structure that the user of the terminal browses with the display unit is changed according to the authority to use the file stored in the first storage unit and the attribute information of the user.
Thereby, when a plurality of terminals perform transmission / reception of files with the file management device, different hierarchical structures can be displayed on the display means of the user of one terminal and the user of another terminal, It is possible to prevent users of other terminals from knowing the usage status of their files.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing a configuration of a file management system according to an embodiment of the present invention. This file management system includes a file management server 10 and a user terminal 20. The file management server 10 and the user terminal 20 are connected via a network 30. As the network 30, a network such as the Internet or an intranet is used. Although FIG. 1 shows a case where one user terminal 20 is connected to the network 30, two or more user terminals 20 are connected to the network 30 when the file management system is actually operated.

The file management server 10 includes an input unit 11, a control unit 12, a communication unit 13, a table storage unit 14, an information storage unit 15, and a display unit 16. A device such as a PC is used as the file management server 10. The input unit 11 includes input devices such as a keyboard and a mouse, and acquires a signal corresponding to the operation based on an operation of a system administrator using the file management server 10 and outputs the signal to the control unit 12.
When a signal is input from the input unit 11 or the communication unit 13, the control unit 12 refers to the table storage unit 14 to display information on the file recorded in the information storage unit 15 on the display unit 16. Perform processing such as. The communication unit 13 is connected to the Web via the network 30 with the user terminal 20 and transmits and receives files and the like.

The table storage unit 14 records a table that is information relating to a file recorded in the information storage unit 15 and a folder in which the file is stored. The configuration of this table will be described later. The information storage unit 15 records files and folders managed by the file management system according to the present embodiment.
The display means 16 is composed of an output device such as an LCD (Liquid Crystal Display), and stores the contents of the files recorded in the information storage means 15, each file and those files based on the control of the control means 12. Information on the hierarchical structure showing the relationship of the folders to be displayed is displayed on the display screen.

The user terminal 20 includes an input unit 21, a control unit 22, a communication unit 23, a storage unit 24, and a display unit 25. A device such as a PC is used as the user terminal 20. The input unit 21 includes input devices such as a keyboard and a mouse, and acquires a signal corresponding to the operation based on an operation of a user who is a user of the user terminal 20 and outputs the signal to the control unit 22.
The control unit 22 uploads a file created by the user operating the input unit 21 from the communication unit 23 to the file management server 10 via the network 30, or receives a file from the file management server 10. Thus, the file is downloaded and recorded in the storage unit 24, or the hierarchical structure of files and folders managed by the file management server 10 is displayed on the display unit 25.

  The communication unit 23 is connected to the Web, and transmits and receives information such as files to and from the file management server 10 via the network 30. The storage unit 24 stores a file relating to a design or the like created by the user of the user terminal 20 or a file downloaded from the management server 10. The display unit 25 displays the file stored in the storage unit 24, the hierarchical structure managed by the file management server 10 and the like on the display screen according to the file use authority and the user attribute information.

FIG. 2 is a flowchart showing processing of the file management server 10 according to the present embodiment.
First, the control unit 12 of the file management server 10 determines whether or not login from the user terminal 20 is permitted (step S01). Specifically, the ID and PW (Pass Word) acquired from the input unit 11 of the file management server 10 or the ID and PW acquired from the input unit 21 of the user terminal 20 via the network 30 are the file management server 10. Authentication is performed as to whether or not the ID and PW recorded in advance are matched. If the ID and the PW do not match, “NO” is determined in the step S01, and the process proceeds to the step S01. On the other hand, if the ID and PW match, “YES” is determined in the step S01.

Next, the control means 12 reads the authority information stored in the table storage means 14 in advance in association with the ID (step S02). Note that the process of step S02 will be described more specifically with reference to FIGS.
And the control means 12 performs a predetermined process based on the signal input from the input means 11 of the file management apparatus 10 or the input means 21 of the user terminal 20. The control means 12 determines which process is to be executed based on the input signal (step S03). The types of signals include “folder creation (C1)”, “file upload (C2)”, “file copy (C3)”, “file deletion (C4)”, and the like. The control means 12 executes the processes of steps S04 to S07, respectively, depending on whether the control command is C1 to C8. Specific processing methods in these processes C1 to C4 will be described later. In addition, about the process of step S04-S07,
This will be described more specifically with reference to FIGS.

Next, the control means 12 refers to a timer or the like, and when a predetermined time has elapsed, deletes the unlinked file by batch processing (step S08). As the predetermined time, for example, midnight is set. The processing in step S08 will be described more specifically with reference to FIG.
Next, the control means 12 determines whether or not a signal for instructing logout has been input (step S09). If the control means 12 has not received a logout signal, “NO” is determined in the step S09, and the process proceeds to a step S03. On the other hand, if the control means 12 receives a logout signal, “YES” is determined in the step S09, and the process proceeds to a step S01. In the following description, a case will be described in which the file management system of the present embodiment is mounted on a system called “Admisimo”.

Next, the authentication process at the time of login in step S01 of FIG. 2 will be described.
FIG. 3 is a table showing the authority set for the user of the file management system of the present embodiment. As shown in the figure, different “authorities” are set for the “system administrator” who uses the file management server 10 and the “user” who uses the user terminal 20. Here, the “system administrator” refers to a user who is in charge of the task of managing the file management system according to the present embodiment. The “user” refers to a general user who uses the file management system according to the present embodiment. The identification information for identifying “user” is stored in association with attribute information about the company to which the user belongs, the project that the user is in charge of, and the like.

  "Authority" for changing files and folders, etc. includes "Create", "Reference", "Authority setting", "Delete" of folder, "Register", "Reference", "Download", " Set for each of “Update” and “Delete”. Here, “◎” in the figure indicates that all folders or files can always be operated. In addition, “○” indicates that only the part for which reference authority is currently set can be operated for all folders or files, but when an administrator screen is created separately There is a possibility that the operation becomes possible. “Δ” indicates that only the part for which the reference authority is set can be operated.

  In the file management system according to the present embodiment, the concept of a project composed of “group” and “assignment” is set as a unit for setting the authority to access a folder. Here, the “group” is for grouping users belonging to the project into meaningful units. When a project is created, a “no designation” group is created as a base group. “Assignment” means that a user managed by the file management system according to the present embodiment belongs to a project.

  A user assigned to a project has a role of “owner” or “member” in the project. Here, “owner” refers to a user who is in a position to manage a project and has authority to refer to all folders or files in the project. “Member” means a user who participates in the project and does not correspond to the owner, and each system administrator or user's authority set for the folder in the project. Can be accessed according to.

  There are two types of “project”: “Project” and “Personal”. Here, “Project” is a project in which a plurality of owners and a plurality of groups can be set, and the user can belong to a plurality of Projects. “Personal” is a project that is displayed as “personal folder” on the management screen displayed on the display means 16, and the owner is always one person. The group is also only a group that is designated as “no designation”, and the user cannot be an owner of a plurality of Personal projects. However, it is possible to become a member of another Personal.

  FIG. 4 shows an example of setting access authority using the concept of the project described above. In the figure, “◎” indicates that all folders or files can always be operated. “◯” indicates that only the portion where the authority is set can be operated for all folders or files. However, if a separate management screen is created, there is a possibility that all operations can be performed. “◇” indicates that operations are always possible only for folders or files in the project to which the user belongs. “□” indicates that only a folder or file in the project to which the user belongs can be operated.

  Next, the types of folders used in the file management system according to the present embodiment will be described. As shown in FIG. 5, in the file management system according to the present embodiment, “root folder f1”, “project root folder f3”, “group root folder f4”, “project folder f5 (f51, f52)”, The “non-project folder f2” is used. Here, the “root folder f1” is a folder that is the root of all folders. You cannot set access permissions for the root folder, store files, or delete the root folder itself.

The “project root folder f3” is a base group folder of the project when the project is created. Folders created in a project are always created under the project root folder. The “group root folder f4” is a folder serving as a base of the group when the group is created in the project, and is created in a layer immediately below the project root folder.
The “project folder f5 (f51, f52)” is a folder that belongs to either Project or Personal, and a project root folder or a group root folder always exists when the project folder is followed up. The “non-project folder f2” is a folder that does not belong to either Project or Personal, and exists mainly for classifying project folders using the hierarchical structure of folders. If you follow the upper layer from the non-project folder to the root folder, there is no project root folder or group root folder.
Note that the selection range of the user to which the access authority is set varies depending on the types of the folders f1 to f5 described above.

  FIG. 6 is a table summarizing users who can set access rights and users who can set access rights for each type of folder. In FIG. 6, the part indicated by (* 1) indicates that the rule of the project root folder is applied if the project is Personal and the upper level is the project root folder. In addition, the root folder indicated by (* 2) cannot be created. This root folder is displayed as “/” at the top of each folder. The non-project folder indicated by (* 3) can be created only by the system administrator of the file management system according to the present embodiment.

FIG. 7 shows an example of a screen displayed on the display means 16 and 25 when a folder is newly created in the file management system according to the present embodiment. There are three methods for creating a new folder in this file management system: a method for creating a folder on the folder management screen, a method for creating a project, and a method for creating a group. In the method of creating on the folder management screen, an upper folder for creating a folder is selected and created on the new registration screen. In the method of creating a project, by creating a new project, a project name folder is created in the case of Project, and an owner name folder is created in the case of Personal. In the method of creating a group, a folder with a group name is created under the project root folder by creating a new group.
At the time of folder creation, a user who has authority over the upper folder is selected as the initial user. By checking “Delete” on the display screen of FIG. 7, it is possible not to give authority to the folder in which the user is created. Also, if the upper folder is deleted when the folder is created, the folder cannot be deleted.

  FIG. 8 is a diagram showing an example of the hierarchical structure of folders displayed on the display means 16 and 23 of the present embodiment. The following rules are set for the display method of the hierarchical structure on the display means 16 and 23. That is, as shown in FIG. 8A, the hierarchical structure of all folders is displayed on the display means 16 of the file management server 10 used by the system administrator. On the other hand, as shown in FIG. 8B, only the root folder is displayed on the display means 23 of the user terminal 20 used by a user who has no reference authority, and the hierarchical structure of other folders is not displayed. . However, even if the folder has no reference authority, if there is a folder with reference authority below it, only the folder name can be referred to when displaying the hierarchical structure. A folder created as a personal project is displayed in Personal when displaying a hierarchical structure, in Project in other cases, and is not displayed in both Personal and Project.

FIG. 9 is a diagram showing another example of the hierarchical structure of folders displayed on the display means 16 and 23 of the present embodiment. The following rules are set for the display method of the hierarchical structure on the display means 16 and 23. That is, the display means 16 of the file management server 10 used by the system administrator includes all folders (Company X, Company A, Project A, Mr. a, Company B, Project B, as shown in FIG. 9A). , B's folder) is displayed.
On the other hand, Mr. a who is a user is set with usage authority and attribute information so that only a folder related to Mr. a can be referred to, and the display means 23 of the user terminal 20 used by Mr. a has FIG. Only the folders shown in (b) (Folders of Company A, Company X, and Project A) are displayed, and folders not related to Mr. a (Folders of Company B, Project B, and Mr. b) are not displayed.
Also, the user B, who is the user, is set with usage authority and attribute information so that only the folder related to Mr. b can be referred to, and the display means 23 of the user terminal 20 used by Mr. b has FIG. Only the folder shown in (c) (the folder of company B, company X, and project B) is displayed, and the folder not related to Mr. b (the folder of company A, project A, and Mr. a) is not displayed.
As described above, all folders and their hierarchical structure can be browsed for the system administrator (FIG. 9 (a)), and only the folders having usage rights and attribute information and their hierarchical structure are available for the user. Since browsing is possible (FIGS. 9B and 9C), it is possible to prevent other users from browsing their folder and its hierarchical structure.

FIG. 10 is a diagram showing an example of an authority setting screen for a folder in the file management system according to the present embodiment. In order to set authority for a folder, it is necessary to satisfy the conditions of a user who can set access authority and a user who can set access authority (see FIG. 6). A user who is set with the access right can add and delete users in the folder, delete folders, create subfolders, and register files.
When the access authority for the folder is deleted, only the authority set for the deleted folder is deleted. When deleting including a lower layer folder, the access right can be deleted even from the lower layer folder by checking “inherit” on the display screen of FIG.

FIG. 11 is a diagram showing an example of a folder deletion screen in the file management system according to the present embodiment. If the folder has a deletion authority (see FIG. 4), the folder can be deleted. However, if the folder to be deleted or the folder below it is a “project or group root folder”, and there are folders that do not have authority in the lower folder, the folder to be deleted or the folder below it If there is a file that can be referenced by the user, the folder to be deleted, or the folder under it, if there is a specification file or a trafficking file whose status has not ended, the folder Can not be deleted.
When the deletion is executed, all lower folders or files are deleted from the folder. A deleted folder or file cannot be recovered.

FIG. 12 is a diagram illustrating an example of a screen displayed when file registration is performed in the file management system according to the present embodiment. When access authority is set for a folder, a file can be registered in that folder. When a file is registered in a folder, in the present embodiment, an email notifying that the file has been registered is transmitted to the user set as the “destination” in the display screen of FIG. I have to.
If you are referring to a folder with administrator or owner authority and you are not a user with folder authority settings, or if there is no destination user for the folder, you can refer to the folder. However, the file cannot be registered.

FIG. 13 is a diagram showing an example of a file list screen in the file management system of this embodiment. When access authority is set for the folder, the file can be browsed and downloaded. A file can be downloaded when access authority is set for the folder, when the download date is before the end date of the file, or when the file is not deleted.
The validity period set in the folder at the time of registration is set for the file. If the validity period has passed since the date when the file was registered, the user cannot refer to the file. However, by extending the valid period for a predetermined period (for example, 7 days), it is possible to refer to the file only during the extended period.
If the file is deleted, the file cannot be referred to. However, only the user who deleted the file cannot refer to the file, and other users can continue to view the file.

  FIG. 14 is a table showing authority set for a file in the file management system of the present embodiment. As shown in the figure, depending on whether or not “system administrator” and “user” have access rights, the authority to “reference”, “download”, “extend”, and “delete” files, respectively. Is set. In the figure, “中” indicates that the operation is possible and the number of operations is not limited. In addition, “◯” indicates that the operation is possible, but the number of operations that can be performed is limited to one time. Further, “x” indicates that the operation is impossible. In addition, the part shown by (* 1) has shown that it follows the authority of the owner of FIG. 4 when it is the owner of a project.

  FIG. 15 is a diagram showing an example of a file copy screen in the file management system of this embodiment. When access authority is set for a file copy source folder or a copy destination folder, the file can be copied. When the file copy is executed, the user set as the “notification destination” on the display screen of FIG. 15 is notified that the file copy has been performed. When copying is executed, the file at the time of copying is copied to the copy destination. Therefore, even if the copy source is updated or deleted after copying, the copy destination is not affected. It should be noted that when copying is executed, information on the validity period of the file and information on the deletion or extension setting of the file for each user are not copied.

Next, specific processing in the file management server 10 of this embodiment will be described.
In the file management system according to the present embodiment, the hierarchical structure displayed on the display unit 25 of the user terminal 20 is separated from the structure when the folder is actually stored in the information storage unit 15, and a table is provided for information that associates the structures of the two. It is recorded in the storage means 14. Thereby, even when a plurality of user terminals 20 are connected to the network 30, different hierarchical structures are provided for each display means 25 of each user terminal 20 based on user attribute information (affiliated company, etc.). Can be displayed.

FIG. 16 is an ER (Entity Relation) diagram showing the relationship between tables stored in the table storage unit 14 of the file management server 10 of this embodiment. The table storage means 14 includes a folder information table 14a, a folder update history information table 14b, a folder hierarchy information table 14c, a file information table 14d, an object information table 14e, a user authority information table 14f, a file reference information table 14g, and a user information table 14h. Is remembered.
The folder information table 14a is a table that holds information for associating real folders recorded in the information storage unit 15 with virtual folders displayed on the display units 16 and 25, and includes “folder ID”, “folder name”, Holds information such as "physical folder name", "deletion period", "project folder flag", "creator", "creation date", "last updater", "last update date", "data revision" Yes.

The folder update history information table 14b is a table that holds a file update history for a folder. “Update history ID”, “Folder ID”, “File name”, “Description”, “User full name”, “Save date / time” Etc. are held.
The folder hierarchy information table 14c is a table for managing folder and file hierarchy information, and holds information such as “hierarchy ID”, “upper folder”, and “lower folder”.
The file information table 14d is a table for managing virtual file information, and includes “file ID”, “object ID”, “file name”, “file description”, “deletion period”, “version number”, “creator” ”,“ Creation date ”,“ last updater ”,“ last update date ”,“ data revision ”, and the like.

The object information table 14e is a table for managing information on actual files, and holds information such as “object ID”, “absolute folder path”, “physical file name”, and “file size”.
The user authority information table 14f is a table for managing the authority of a user to a folder, and holds information such as “user authority ID”, “user ID”, and “folder ID”.
The file reference information table 14g is a table for managing the user's authority to the file, and holds information such as “file ID”, “user ID”, “extended deletion period”, and “deletion flag”.
The user information table 14h is a table for managing information about users who use the user terminal 20, and holds information such as “user ID” and “folder ID”.

  FIG. 17 is a diagram showing the relationship between the virtual folder displayed on the display means 16 and 25 and the actual folder stored on the information storage means 15. The virtual folder and the real folder are linked one-on-one by the folder information table 14a and the folder hierarchy information table 14c stored in the table storage unit 14. Here, “project A”, “project A1”, “project B”, and “project B1” of the virtual folders are “system naming 1”, “system naming 2”, “system naming 3”, “ The case corresponding to “system naming 4” is shown. The virtual folder exists in a state where a hierarchical structure is taken, but the corresponding real folder exists in a state where no hierarchical structure is taken.

  FIG. 18 is a diagram showing the relationship between the virtual files displayed on the display means 16 and 25 and the actual files stored in the information storage means 15. The file uploaded to the file management server 10 from the user terminal 20 via the network 30 is renamed by changing the file name by the control unit 12 of the file management server 10 and recorded in the information storage unit 15. Information about the file is held in two places, the file information table 14d and the object information table 14e. Similar to the folder management (FIG. 17), the information that associates the virtual file with the real file is managed by the table storage means 14, but the two are not necessarily in a one-to-one relationship. Here, the case where the virtual file “project A1” corresponds to the real file “system naming 2” is shown.

  Next, folder creation processing in the file management server 10 according to the present embodiment will be described. This process corresponds to the process of step S04 in FIG. When a new folder is created, a physical folder is created in the information storage unit 15, and information about the folder is added to the folder information table 14a, folder hierarchy information 14c, and user authority information table 14f of the table storage unit 14. Is done. The folder name is automatically determined by the control means 12 as “Web server name_creation user ID_creation date / time_thread ID”. For example, “WebSvr01 — 5 — 200506031015130123 — 3500” is used as the folder name.

Next, file upload processing in the file management server 10 according to the present embodiment will be described. This process corresponds to the process of step S05 in FIG. When the file upload process is performed, information regarding the file is added to the folder update history information table 14b, the folder hierarchy information 14c, the file information table 14d, and the object information table 14e of the table storage unit 14.
FIG. 19 is a diagram illustrating the state of the file information table 14d (FIG. 19A) and the object information table 14e (FIG. 19B) when performing file upload processing. 19A is associated with the addition of the virtual file name “Project A”, and FIG. 19B shows the physical file name “200550631a1...” And the physical folder path “X: “\ WebSvr01... \” Is added. When the virtual file name is renamed to the physical file name, the control unit 12 uses the name “YYYYMMDD + upload unique MD5Hash + _serial number.tlc”. For example, “200550611a2b3c4d... _01.tlc” is used as the physical file name. “MD5Hash” indicates a hash method.

FIG. 20 shows the state of the file information table 14d (FIGS. 20A and 20C) and the object information table 14E (FIGS. 20B and 20D) when the uploaded file is updated. FIG. By updating the uploaded file, the file information table 14d changes from FIG. 20A to FIG. 20B. That is, the version information changes from “1” to “2”, and the object ID changes from “1” to “2”.
The object information table 14e changes from FIG. 20 (b) to FIG. 20 (d). That is, information of the physical folder path “X: ¥ WebSvr01...” With the object ID “2” and the physical file name “20055061XX...” Is newly added.
As described with reference to FIG. 20, when the uploaded file is updated, the information storage unit 15 stores the files before and after the upload as separate files. This prevents an I / O error from occurring even if another user is downloading the file.

FIG. 21 shows a file information table 14d (FIGS. 21 (a) and (c)), an object information table 14e (FIGS. 21 (b) and (d)), and a folder when a new file creation process is performed by copying. It is a figure which shows the state of the hierarchy information table 14c (FIG.21 (e)). This process corresponds to the process of step S06 in FIG. Here, as shown in FIG. 21E, a case will be described in which a file in a folder with a hierarchy ID “1” is copied to a folder with a hierarchy ID “2”. By performing the process of creating a new file by copying, the file information table 14d changes from FIG. 21A to FIG. 21B. That is, information of the file ID “2” having the same virtual file name, version number, and object ID as the file ID “1” is added. Since the object IDs of the file IDs “1” and “2” are both “2”, they are the same before (FIG. 21 (b)) and after (FIG. 21 (d)) before creating a new file by copying. Reference is made to the object ID “2”.
In the process of FIG. 21, the object information table 14e is not added or updated, and the actual file is not copied, so that the process of creating a new file by copying can be speeded up.

FIG. 22 shows a file information table 14d (FIGS. 22A and 22C), an object information table 14e (FIGS. 22B and 22D), and a folder when processing for updating a copy source file is performed. It is a figure which shows the state of the hierarchy information table 14c (FIG.22 (e)).
Here, as shown in FIG. 22E, a case will be described in which a file in a folder whose hierarchy ID is “1” is updated. By updating the file, the file information table 14d changes from FIG. 22A to FIG. 22C. That is, the version number for the file with the file ID “1” is changed from “2” to “3”, and the object ID is changed from “2” to “3”. Further, the object information table 14 changes from FIG. 22B to FIG. 22D. That is, the physical file name of the reference destination of the file whose file ID is “1” changes from “” “20050631XX...” To “200550631ZZ.
As described above, in the file management system of this embodiment, the copy source file and the updated file of the copy source file are stored as separate files in the information storage unit 15. If a copy exists, the copy itself refers to the file at the time of creating the copy.

FIG. 23 shows the state of the file information table 14d (FIGS. 23A and 23C) and the object information table 14e (FIGS. 23B and 23D) when processing for updating a link by uploading is performed. FIG.
By performing the process of updating the link by uploading, the file information table 14d changes from FIG. 23 (a) to FIG. 23 (c). That is, the object ID of the file with the file ID “2” is updated from “2” to “4”. Further, the object information table 14 changes as shown in FIG. 23B from FIG. That is, information of “physical folder path” and “physical file name” for the file with the file ID “4” is added.

FIG. 24 is a diagram showing the state of the file information table 14d (FIGS. 24A and 24C) and the object information table 14e (FIGS. 24B and 24D) when performing update processing by copying. It is. Here, a case where information with a file ID “1” is copied to information with a file ID “2” will be described.
By performing the update process by copying, the file information table 14d changes from FIG. 24 (a) to FIG. 24 (c). That is, the file with the file ID “2” is changed to the same information as the “virtual file name”, “version number”, and “object ID” with the file ID “1”.
Further, the object information table 14 changes from FIG. 24B to FIG. 24D. That is, information of “physical folder path” and “physical file name” for the file with the file ID “4” is added.

FIG. 25 shows a file information table 14d (FIGS. 25 (a) and (c)) and an object information table 14e (FIGS. 25 (b) and (d)) when a file deletion process is performed by an administrator's operation. It is a figure which shows the state of. Here, a case where a file with the file ID “1” is deleted will be described. This process corresponds to the process of step S07 in FIG.
The file information table 14d changes from FIG. 25 (a) to FIG. 25 (c) by performing the file deletion process by the operation of the administrator. That is, the information of “virtual file name”, “version number”, and “object ID” of the file with the file ID “1” is deleted from the file information table 14d.
Further, the object information table 14 changes from FIG. 25B to FIG. 25D. That is, the object ID “3” linked to the file IDs “1” and “2” is changed to a linked state only from the file ID “2”.

  FIG. 26 is a diagram illustrating a state of the file information table 14d when a file deletion process is performed by a user operation. When the user deletes the file, the deletion flag is changed from “0” to “1”. A file whose deletion flag is set to “1” is not displayed on the display screen of the user terminal 20 used by the user who deleted the file. On the other hand, for users other than the user who deleted the file, since the deletion flag remains “0”, the file can be viewed.

FIG. 27 shows the state of the file information table 14d (FIGS. 27A and 27C) and the object information table 14e (FIGS. 27B and 27D) when a file is deleted by batch processing. FIG. This process corresponds to the process of step S08 in FIG. Here, a case where a file with a file ID other than “2” is deleted from the information storage unit 15 will be described.
Before and after deletion of files in batch processing, the state of the file information table 14d is as shown in FIGS. 27 (a) and 27 (c) and does not change. On the other hand, the object information table 14 changes from FIG. 27 (b) to FIG. 27 (d). That is, the file IDs “1”, “2”, and “4” that are not linked from the file ID “2” are deleted from the information storage unit 15.

  By performing the processing as described above, the access authority for each user is controlled on a folder-by-folder basis, and a user who has access authority to a folder also has access authority to subordinate files. The check is performed in real time every time a folder is accessed, and it is confirmed whether or not a combination of a user ID and a folder ID exists in the user authority information table 14f. Although the overhead caused by checking each time is foreseen, the access authority can be updated immediately in response to updates from other sessions.

According to the file management system according to the embodiment of the present invention described above, the display unit 25 of the user terminal 20 or the display unit of the file management server 10 according to the usage authority set for the user or system administrator and the attribute information thereof. Since the hierarchical structure displayed at 16 is made different, it is possible to prevent a user from knowing information such as the hierarchical structure of other users.
In addition, when a certain user deletes a predetermined file, a deletion flag is added and recorded. Therefore, the file is not deleted for other users who do not have the deletion flag added to the file. Since it can be displayed continuously, the convenience for the user can be improved.

In the embodiment described above, functions such as SSL (Secure Socket Layer), PKI (Public Key Infrastructure), biometric authentication, and firewall may be used when performing communication via the network 30. Further, when logging in in step S01 of FIG. 2, authentication may be performed between the user terminal 20 and the file management server 10 using a one-time password. By performing such processing, it is possible to prevent electronic data such as design from being leaked to a third party via the network 30, and safety for protection of copyright, personal information, confidential business information, etc. The sex can be increased.
Further, since the network 30 can use the Internet instead of a dedicated line, and can manage files using a commonly used browser, system administrators and users need to communicate with each other. Cost can be reduced. Therefore, anyone who wants to use the file management system according to the present embodiment can use the file management system as compared with a conventional system used in a specific company. In the file management system according to the present embodiment, when communication is performed between the file management apparatus 10 and the user terminal 20, a function capable of transmitting and receiving a large amount of information may be provided.

  In the embodiment described above, a program for realizing the functions of the control unit 12 of the management server 10 and the control unit 22 of the user terminal 20 in FIG. 1 is recorded on a computer-readable recording medium. The file management system may be controlled by causing the computer system to read and execute the program recorded in the above. The “computer system” here includes an OS and hardware such as peripheral devices.

  The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” dynamically holds a program for a short time, like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, it is also assumed that a server that holds a program for a certain time, such as a volatile memory inside a computer system that serves as a server or client. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes designs and the like that do not depart from the gist of the present invention.

It is a block diagram which shows the structure of the file management system by embodiment of this invention. It is a flowchart which shows the process of the file management server 10 by this embodiment. It is the table | surface shown about the authority set with respect to the user of the file management system of this embodiment. It is a table | surface which shows the example which sets the authority of access using the concept of a project. It is a figure shown about the kind of folder used with the file management system by this embodiment. It is the table | surface which put together about the user who can set the authority of access with respect to each kind of folder, and the user who becomes the object of the authority of access. In the file management system according to the present embodiment, an example of a screen displayed on the display means 16 and 25 when a folder is newly created is shown. It is a figure which shows an example of the hierarchical structure of the folder displayed on the display means 16 and 23 of this embodiment. It is a figure which shows the other example of the hierarchical structure of the folder displayed on the display means 16 and 23 of this embodiment. It is a figure which shows an example of the setting screen of the authority with respect to the folder in the file management system by this embodiment. It is a figure which shows an example of the folder deletion screen in the file management system by this embodiment. It is a figure which shows an example of the screen displayed when registering a file in the file management system by this embodiment. It is a figure which shows an example of the file list screen in the file management system of this embodiment. 5 is a table showing authority set for a file in the file management system of the present embodiment. It is a figure which shows an example of the copy screen of the file in the file management system of this embodiment. It is an ER figure which shows the relationship of the table memorize | stored in the table memory | storage means 14 of the file management server 10 of this embodiment. FIG. 4 is a diagram showing the relationship between virtual folders displayed on display means 16 and 25 and real folders stored on information storage means 15. 4 is a diagram showing the relationship between virtual files displayed on display means 16 and 25 and real files stored in information storage means 15. FIG. It is a figure which shows the state of the file information table 14d and the object information table 14e in the case of performing a file upload process. It is a figure which shows the state of the file information table 14d in the case of performing the update process of the uploaded file, and the object information table 14e. It is a figure which shows the state of the file information table 14d, the object information table 14e, and the folder hierarchy information table 14c in the case of performing the process of new file creation by copying. It is a figure which shows the state of the file information table 14d, the object information table 14e, and the folder hierarchy information table 14c in the case of performing the process which updates the copy source file. It is a figure which shows the state of the file information table 14d and the object information table 14e in the case of performing the process which updates a link by upload. It is a figure which shows the state of the file information table 14d in the case of performing the update process by copying, and the object information table 14e. It is a figure which shows the state of the file information table 14d and the object information table 14e when performing the deletion process of a file by operation of an administrator. It is a figure which shows the state of the file information table 14d when performing the process of deletion of a file by a user's operation. It is a figure which shows the state of the file information table 14d in the case of deleting a file by batch processing, and the object information table 14e.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... File management server, 11 ... Input means, 12 ... Control means, 13 ... Communication means, 14 ... Table storage means, 14a ... Folder information table, 14b ... Folder Update history information table, 14c ... folder hierarchy information table, 14d ... file information table, 14e ... object information table, 14f ... user authority information table, 14g ... file reference information table, 14h ..User information table, 15... Information storage means, 16... Display means, 20... User terminal, 21. ... Storage means, 25 ... Display means, 30 ... Network

Claims (6)

A file management device for managing files sent to and received from a terminal,
Input means for acquiring identification information of a user of the terminal;
First storage means for storing the identification information of the user of the terminal and the attribute information of the user in association with the authority to use the file;
Second storage means for storing a file used by a user of the terminal;
First control means for reading out the authority to use the file corresponding to the user identification information acquired by the input means and the attribute information of the user from the first storage means;
Display means for displaying a file stored in the second storage means in a hierarchical structure according to the authority to use the file read by the first control means and the attribute information of the user;
A file management apparatus comprising: Third storage means for storing deletion information indicating that a deletion instruction is input from the terminal for each file stored in the second storage means in association with identification information of a user of the terminal; ,
For the user specified by the identification information of the user of the terminal whose deletion information is stored in the third storage means, the display means does not display the file in which the deletion instruction is input, Second control for displaying a file in which the deletion instruction is input by the display means for a user specified by identification information of a user of the terminal whose deletion information is not stored in a third storage means Means,
The file management apparatus according to claim 1, further comprising: A file management method for managing files sent to and received from a terminal,
A first step of obtaining identification information of a user of the terminal;
A second step of storing the identification information of the user of the terminal and the attribute information of the user in association with the authority to use the file;
A third step of storing a file used by a user of the terminal;
Read the file usage authority and the user attribute information corresponding to the user identification information acquired in the first step from the file usage authority and the user attribute information stored in the second step. And the steps
A fifth step of displaying the file stored in the third step in a hierarchical structure according to the authority to use the file read in the fourth step and the attribute information of the user;
A file management method characterized by comprising: A sixth step of storing, for each file stored in the third step, deletion information indicating that a deletion instruction has been input from the terminal in association with identification information of the user of the terminal;
For the user specified by the identification information of the user of the terminal that has stored the deletion information in the sixth step, the file in which the deletion instruction is input in the fifth step is not displayed. A seventh step of displaying a file in which the deletion instruction is input in the fifth step for a user specified by the identification information of the user of the terminal that does not store the deletion information in the step of 6. When,
The file management method according to claim 3, further comprising: A control program for controlling a file management device for managing files sent to and received from a terminal,
A first step of acquiring identification information of a user of the terminal;
A second step of storing the identification information of the user of the terminal and the attribute information of the user in association with the authority to use the file;
A third step of storing a file used by a user of the terminal;
The use authority of the file corresponding to the user identification information acquired in the first step and the attribute information of the user are read from the use authority of the file stored in the second step and the attribute information of the user. A fourth step;
A fifth step of displaying the file stored in the third step in a hierarchical structure according to the authority to use the file read in the fourth step and the attribute information of the user;
A control program for controlling a file management apparatus characterized by comprising: A sixth step of storing, for each file stored in the third step, deletion information indicating that a deletion instruction is input from the terminal in association with identification information of the user of the terminal;
For the user specified by the identification information of the user of the terminal that has stored the deletion information in the sixth step, the file in which the deletion instruction is input in the fifth step is not displayed. A seventh step of displaying a file in which the deletion instruction is input in the fifth step for a user specified by the user identification information of the terminal that does not store the deletion information in the step of 6. When,
The control program for controlling the file management apparatus according to claim 5.

Images