File management apparatus and file management program

Abstract

To provide a file management apparatus which allows relevant files, which are related to an object file, such as a document, to be accessed when associating the relevant files, regardless of locations where the relevant files are stored, and can reduce data volume of the object file as compared with a case where all relevant files are attached.SOLUTION: A file management apparatus includes at least one processor. The processor acquires information on an object file, a storage location of a relevant file related to the object file, and a viewer. When the viewer is allowed to access the storage location of the relevant file, the processor provides information on the storage location of the relevant file to the viewer. When the viewer is not allowed to access the storage location of the relevant file, the processor provides the relevant file to the viewer.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a file management device and a file management program.

Background Art

[0002] Patent Document 1 discloses a program for causing a computer to function as a file management device. The computer is caused to function as file management means for handling a file in which original file storage location information for specifying the location where the original file of the file is stored is set as attribute information separately from actual file storage location information for specifying the location where the replicated file is actually stored.

[0003] Patent Document 2 discloses a document management device including: first registration means for registering, in a storage device, a unique operation identifier assigned to a new registration operation of a document in association with the document when the new registration operation of the document is performed; second registration means for registering, in the storage device, a derivation relationship indicating that a unique second operation identifier assigned to an operation performed on a first document corresponding to the first operation identifier registered in the storage device is derived from the first operation identifier, and when a second document different from the first document is generated as a result of the operation, registering the second operation identifier in the storage device in association with the second document; and related document registration means for registering, in the storage device, as a related document attribute of the second operation identifier assigned to the setting operation, a third operation identifier registered in the storage device in association with a related document when the operation on the first document corresponding to the first operation identifier is a setting operation for setting a related document for the first document.

[0004] In Patent Document 3, in an automatic document management method for automatically associating related documents, there are a document (1-1) opened first, a home document, reference documents (1-2), (1-3) opened in relation to the home document, a reference stack (1-4) for temporarily storing the association therebetween, and a document management area (1-5) for finally storing the reference relationship as the related attribute information (1-6) of the home document. When the home document (1-1) is opened, a plurality of related opened documents (1-2), (1-3) are automatically stored in the reference stack (1-4). When closing the home document (1-1), the user is asked whether to store the information of the reference stack (1-4) in the document management area (1-5), or whether to edit it, and only the necessary document (1-2) is stored. When the corresponding document is opened after the next time, the necessary related document (1-2) can be retrieved based on the related document attribute information (1-6) stored in the related document management area (1-5). A document management method is disclosed which is characterized by this.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Patent Document 2

Patent Document 3

Summary of the Invention

Problems to be Solved by the Invention

[0006] There is a known technique of associating and storing related documents related to a target document according to the operation history of the target document. In this technique, when the target document is displayed for editing or the like, the related documents are also displayed in conjunction. When the target document is shared with other users, depending on the storage location of the related documents of the target document, the storage location may not be shared with other users, and other users may not be able to access the related documents. On the other hand, there is a technique of attaching related documents to the target document, but as the number of attached related documents increases, the file size becomes large, and the handling of the target document becomes troublesome.

[0007] An object of the present invention is to provide a file management apparatus and a file management program that can suppress the data capacity of a target file while enabling access to related files regardless of the storage location where the related files are stored when associating related files related to a target file such as a document, and compared to the case of attaching all related files.

Means for Solving the Problems

[0008] The file management apparatus according to the first aspect includes at least one processor. The processor acquires information regarding a target file, a storage destination of related files related to the target file, and a viewer. When the viewer can access the storage destination of the related files, the processor provides the viewer with information indicating the storage destination of the related files. When the viewer cannot access the storage destination of the related files, the processor provides the viewer with the related files.

[0009] The file management apparatus according to the second aspect is the file management apparatus according to the first aspect, wherein the processor confirms with the user who manages the target file the form of providing the viewer with the related files.

[0010] The file management device according to the third aspect is the file management device according to the second aspect, wherein the processor receives from the user whether to switch the form of providing the related file to the viewer from the information indicating the storage destination to the related file or from the related file to the information indicating the storage destination.

[0011] The file management device according to the fourth aspect is the file management device according to the second or third aspect, wherein the processor receives the addition of the related file, and at the time of the addition, receives whether to use the information indicating the storage destination of the related file or the related file as the form of providing the related file to the viewer.

[0012] The file management program according to the fifth aspect causes a computer to execute steps of: acquiring information regarding a target file, a storage destination of a related file related to the target file, and a viewer; when the viewer can access the storage destination of the related file, providing the viewer with information indicating the storage destination of the related file; and when the viewer cannot access the storage destination of the related file, providing the viewer with the related file.

Advantages of the Invention

[0013] According to the first aspect, when associating a related file related to a target file such as a document, it is possible to suppress the data volume of the target file while enabling access to the related file regardless of the storage location where the related file is stored, and compared to the case of attaching all related files.

[0014] According to the second aspect, the related file is provided to the viewer in an appropriate form as compared to the case where the user who manages the target file does not confirm the form of providing the related file to the viewer.

[0015] According to the third aspect, the related file is provided to the viewer in the form intended by the user as compared to the case where the user who manages the target file cannot switch the form of providing the related file to the viewer.

[0016] According to the fourth aspect, access to the added related file becomes possible as compared with the case where a form of providing the related file to the viewer is not accepted when adding the related file.

[0017] According to the fifth aspect, when associating related files related to a target file such as a document, access to the related file is enabled regardless of the storage location where the related file is stored, and the data volume of the target file can be suppressed as compared with the case where all related files are attached.

Brief Description of the Drawings

[0018]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Embodiments for Carrying Out the Invention

[0019] Hereinafter, an example of an embodiment of the technology of the present invention will be described with reference to the drawings. In each drawing, the same or equivalent components and parts are given the same reference numerals. Also, the dimensional ratios in the drawings are exaggerated for the convenience of explanation and may be different from the actual ratios.

[0020] FIG. 1 is a diagram showing a schematic configuration of a file management apparatus according to an embodiment.

[0021] As shown in FIG. 1, the file management apparatus 1 includes a plurality of user terminals 10 each used by a respective user, and a server 20. The plurality of user terminals 10 include, as an example, a first user terminal 10A used by one user A and a second user terminal 10B used by another user B. There is no particular limitation on the number of user terminals 10.

[0022] The file management apparatus 1 is, as an example, a system in which a plurality of user terminals 10 and a server 20 are connected via the Internet, a wired or wireless network. In FIG. 1, the file management apparatus 1 is illustrated as a system connected via a wireless network as an example. The file management apparatus 1 is an apparatus that manages files, folders, shortcuts, etc. using the server 20. In FIG. 1, reference numerals are shown separately for the first user terminal 10A and the second user terminal 10B, but when the first user terminal 10A and the second user terminal 10B are not distinguished, they will be described as "user terminal 10".

[0023] The user terminal 10 is composed of a computer device such as a desktop computer, a notebook computer, or a tablet computer. The user terminal 10 is an apparatus that creates, edits, and saves files. The files include document files, image files, or files combining documents and images. Also, the user terminal 10 displays files transmitted from other users.

[0024] The user terminal 10 has an input unit 15 and a display unit 16. In the user terminal 10, for example, file creation, editing, and saving are performed by the input unit 15, and the file is displayed on the display unit 16.

[0025] As an example, in the first user terminal 10A used by user A, according to the operation history of any one file 30, a related file 32 related to the one file 30 is stored in association with the one file 30. In this specification, any one file 30 with which the related file 32 is associated is referred to as a target file 30. In this specification, each of the target file 30 and the related file 32 is referred to as the target file 30 and the related file 32 according to their mutual relationship, and any file can become the target file 30 or the related file 32 depending on its relationship with other files. The specific configuration and operation of the user terminal 10 will be described later.

[0026] The server 20 is a server configured by a computer device. For example, an in-house shared server or a cloud server is used. The server 20 has a function of sharing and managing files sent from users in services provided for multiple users. In the server 20, for example, when the target file 30 is sent from the first user terminal 10A of user A, it is possible to share the target file 30 with another user B. Also, the server 20 is a device that enables user B to access the related file 32 related to the target file 30 when user B opens the target file 30 on the second user terminal 10B. The specific configuration and operation of the server 20 will be described later.

[0027] FIG. 2 is a block diagram showing the hardware configuration of the user terminal 10.

[0028] As shown in FIG. 2, the user terminal 10 includes components such as a CPU (Central Processing Unit), a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a storage 14, an input unit 15, a display unit 16, and a communication interface 17. Each component is connected to be communicable with each other via a bus 19.

[0029] The CPU 11 is a central processing unit that executes various programs and controls each part. That is, the CPU 11 reads a program from the ROM 12 or the storage 14 and executes the program using the RAM 13 as a working area. The CPU 11 performs control of each of the above components and various arithmetic processes according to the program recorded in the ROM 12 or the storage 14. In this embodiment, a file management program is stored in the ROM 12 or the storage 14.

[0030] The ROM 12 stores various programs and various data. The RAM 13 temporarily stores a program or data as a working area. The storage 14 is composed of an HDD (Hard Disk Drive) or an SSD (Solid State Drive) and stores various programs including an operating system and various data.

[0031] The input unit 15 includes a pointing device such as a mouse and a keyboard and is used to perform various inputs.

[0032] The display unit 16 is, for example, a liquid crystal display and displays various information. The display unit 16 may adopt a touch panel method and function as the input unit 15.

[0033] The communication interface 17 is an interface for communicating with other devices such as the server 20. For example, standards such as Ethernet (registered trademark), FDDI, Wi-Fi (registered trademark), etc. are used.

[0034] FIG. 3 is a block diagram showing the hardware configuration of the server 20.

[0035] As shown in FIG. 3, the server 20 has components such as a CPU 21, a ROM 22, a RAM 23, a storage 24, and a communication interface 25. Each component is communicably connected to each other via a bus 29.

[0036] The CPU 21 is a central processing unit that executes various programs and controls each part. That is, the CPU (processor) 21 reads a program from the ROM 22 or the storage 24 and executes the program using the RAM 23 as a work area. The CPU 21 performs control of the above components and various arithmetic processes according to the program recorded in the ROM 22 or the storage 24. In this embodiment, a file management program is stored in the ROM 22 or the storage 24.

[0037] The ROM 22 stores various programs and various data. The RAM 23 temporarily stores a program or data as a work area. The storage 24 is composed of an HDD (Hard Disk Drive) or an SSD (Solid State Drive) and stores various programs including an operating system and various data.

[0038] The communication interface 25 is an interface for communicating with other devices such as a plurality of user terminals 10, and for example, standards such as Ethernet (registered trademark), FDDI, Wi-Fi (registered trademark), etc. are used.

[0039] Next, the functional configurations of the user terminal 10 and the server 20 will be described.

[0040] FIG. 4 is a block diagram showing an example of the functional configuration of the user terminal 10.

[0041] As shown in FIG. 4, the user terminal 10 has, as functional components, a creation unit 101, a form switching unit 102, an addition unit 103, a transmission unit 104, and a reception unit 105. Each functional component is realized by the CPU 11 reading out a file management program stored in the ROM 12 or the storage 14, expanding it in the RAM 13, and executing it.

[0042] The creation unit 101 creates and edits files. For example, the user creates and edits a file by inputting data using the input unit 15 of the user terminal 10. Also, the user may create and edit a file using data received from another device through the communication interface 17 of the user terminal 10. As an example, in the first user terminal 10A used by user A, when creating and editing the target file 30 (see FIG. 1), the operation history of the target file 30 is stored in the storage 14 or the like. In the user terminal 10, information on the related file 32 related to the target file 30 is stored in the storage 14 or the like according to the operation history of the target file 30.

[0043] The form switching unit 102 switches the form in which the related file 32 is provided to the viewer. As an example, in the first user terminal 10A, the form switching unit 102 switches the form in which the related file 32 is provided to user B as an example of the viewer according to the selection of user A. For example, when the form in which the related file 32 is provided to user B is an object (for example, the related file 32 itself), according to the selection of user A, the form is switched from the related file 32 to information indicating the storage destination of the related file 32 (for example, a link). Also, for example, when the form in which the related file 32 is provided to user B is information indicating the storage destination of the related file 32 (for example, a link), according to the selection of user A, the form is switched from the information indicating the storage destination of the related file 32 to the related file 32 (for example, an object). The switching of the form in which the related file 32 is provided to user B may be performed autonomously by user A or in response to confirmation of the form from the server 20.

[0044] The addition unit 103 adds the related file 32 related to the target file 30. In the user terminal 10, the related file 32 is set according to the operation history of the target file 30. However, when another related file 32 is to be added, the other related file 32 is added by the addition unit 103.

[0045] The transmission unit 104 transmits files and the like to the server 20. As an example, in the first user terminal 10A, the target file 30, the information in the form of providing the related file 32 to other users, the information on the addition of the related file 32, and the like are transmitted to the server 20.

[0046] The reception unit 105 receives the files transmitted from the plurality of user terminals 10 from the server 20.

[0047] FIG. 5 is a block diagram showing an example of the functional configuration of the server 20.

[0048] As shown in FIG. 5, the server 20 includes, as functional components, a reception unit 201, an acquisition unit 202, a file management unit 203, a form confirmation unit 204, a switching reception unit 205, a provision unit 206, an addition reception unit 207, an addition form reception unit 208, and a transmission unit 209. Each functional component is realized by the CPU 21 reading out the file management program stored in the ROM 22 or the storage 24 and expanding it in the RAM 23 for execution.

[0049] The reception unit 201 receives files and the like transmitted from the plurality of user terminals 10. The file also includes the related information of the file. For example, when the target file 30 is received from the first user terminal 10A, the related information of the target file 30 includes the information of the related file 32 related to the target file 30.

[0050] The acquisition unit 202 acquires the storage destination of the target file 30, the storage destination of the related file 32 related to the target file 30, and the information regarding the user B as an example of the viewer.

[0051] The file management unit 203 manages operations related to files, such as the content, attributes, and editing of files. The file management unit 203 includes a file content management unit 203A and a file attribute management unit 203B, and distributes operations to the file content management unit 203A and the file attribute management unit 203B according to operation requests from users. The file content management unit 203A manages the content of the file itself, such as the text information described in the file, the information of the attached annotations (i.e., notes), and the layout information.

[0052] In addition, the file attribute management unit 203B manages the attributes of the file. Examples of attributes include file name, creation date, update date, creator, updater, related file information, etc. When the attributes are changed triggered by operations such as saving the file or the user editing the attributes, the file attribute management unit 203B reflects the result in the file attributes. The related file information includes the form of providing the related file 32 to user B.

[0053] The form confirmation unit 204 confirms the form of providing the related file 32 to user B for user A who manages the target file 30. The forms of providing the related file 32 to user B include information indicating the storage destination of the related file 32 (e.g., link), object (e.g., the related file 32 itself). The object may be a compressed file obtained by compressing the related file 32. The form confirmation unit 204 confirms whether to use the information indicating the storage destination of the related file 32 or the object as the form to be provided to user B. The confirmation result by the form confirmation unit 204 is sent to the file attribute management unit 203B of the file management unit 203.

[0054] The switching reception unit 205 receives the switching of the form of providing the related file 32 to user B. For example, it receives whether to switch the form of providing the related file 32 to user B from the related file 32 to the information indicating the storage destination of the related file 32, or from the information indicating the storage destination of the related file 32 to the related file 32.

[0055] The providing unit 206 provides the user B with information indicating the storage destination of the related file 32 or the related file 32. For example, when the user B can access the storage destination of the related file 32, the information indicating the storage destination of the related file 32 is provided to the user B, and when the user B cannot access the storage destination of the related file 32, the related file 32 is provided to the user B.

[0056] The additional reception unit 207 receives the addition of the related file 32 related to the target file 30. For example, when the related file 32 is added by the addition unit 103 of the user terminal 10, the additional reception unit 207 receives the addition of the related file 32.

[0057] When the additional reception unit 207 receives the addition of the related file 32, the additional form reception unit 208 receives the form for providing the added related file 32 to the user B. Examples of the form for providing the added related file 32 to the user B include information (e.g., a link) indicating the storage destination of the added related file 32, or the added related file 32 (e.g., an object).

[0058] The transmission unit 209 transmits files and the like to a plurality of user terminals 10. For example, when the target file 30 is received by the reception unit 201 from the first user terminal 10A, the transmission unit 209 transmits the target file 30 to the second user terminal 10B.

[0059] Next, the operation of the file management device will be described.

[0060] FIG. 6 is a flowchart showing the flow of file management processing by the server 20 of the file management device 1. The file management processing is performed by the CPU 21 reading the file management program from the ROM 22 or the storage 24 and expanding and executing it in the RAM 23.

[0061] When a file management instruction is input by any user, the CPU 21 of the server 20 performs the file management process shown in FIG. 6.

[0062] As shown in FIG. 6, the CPU 21 determines whether user A has saved the target file 30 (step S51). For example, when the target file 30 is saved in the storage 14 of the first user terminal 10A or the storage 24 of the server 20, the CPU 21 determines that user A has saved the target file 30. In the file management process of this example, when user A saves the target file 30, the attributes of the target file 30 are also updated. The attributes of the target file 30 include, for example, file name, creation date, update date, creator, updater, etc. In addition, the attributes of the target file 30 also include related file information. If the related file 32 is associated from the operation history of the target file 30, it is updated to have the related file 32. Also, if the related file 32 is not associated from the operation history of the target file 30, it is updated to have no related file 32.

[0063] If user A does not save the target file 30 (step S51: N0), the CPU 21 ends the process based on the file management program. If user A saves the target file 30 (step S51: YES), the CPU 21 determines whether there is a related file 32 related to the target file 30 (step S52). Whether there is a related file 32 related to the target file 30 is determined by the attributes of the target file 30. For example, whether there is a related file 32 related to the target file 30 may be extracted using the method described in Japanese Patent Laid-Open No. 9-330312.

[0064] If there is no related file 32 (step S52: N0), the CPU 21 ends the process based on the file management program. That is, when there is no related file 32, the CPU 21 ends the update of the related file attributes without setting anything in the related file attributes.

[0065] When there is a related file 32 (step S52: YES), the CPU 21 acquires the storage destination of the target file 30 and the storage destination of the related file 32 (step S53). Based on the storage destinations of the target file 30 and the related file 32, in steps S55, S56, etc. to be described later, it is determined whether to provide information (e.g., a link) indicating the storage destination of the related file 32 or to provide it with the related file 32 (e.g., an object).

[0066] The CPU 21 determines whether it has acquired information about the viewer (step S54). Here, the viewer is the person who views the target file 30. For example, user A designates user B as the recipient of an email in order to allow user B to view the target file 30, and describes information (e.g., a link) indicating the storage destination of the target file 30 in the body of the email and sends it. The means of designating the viewer is not limited to sending by email. In a data exchange service such as a messenger, the recipient may be designated as the viewer by sending or sharing information indicating the storage destination of the target file 30. Note that the timing of acquiring information about the viewer does not necessarily have to be after acquiring the storage destinations of the target file and the related file. Also, instead of providing information indicating the storage destination of the target file 30, the target file 30 itself may be provided to user B.

[0067] When information about the viewer is not acquired (step S54: NO), the CPU 21 sets information about the viewer (step S64). For example, user A himself / herself may input information about the viewer (e.g., the access authority of the viewer, etc.), and set the input information as information about the viewer. Note that the timing of setting information about the viewer does not necessarily have to be after acquiring the storage destinations of the target file and the related file. In this case, in step S54, it is determined that information about the viewer has been acquired. Hereinafter, the description will be made on the premise that user B is designated as the viewer.

[0068] When information about the viewer is obtained (step S54: YES), or after the information about the viewer is set in step S64, the CPU 21 determines whether the storage destination of the related file 32 is a server that requires authentication (step S55). A server that requires authentication is, for example, a cloud server or the like, but also includes other shared servers. A server that does not require authentication is, for example, a NAS (Network - Attached Storage) within a company, but also includes other shared servers. NAS refers to an external storage device directly connected to a network and accessible from a computer or the like through the network.

[0069] Whether the storage destination of the related file 32 is a server that requires authentication can be confirmed by making an inquiry to the server. For example, the server 20 can inquire of the server where the related file 32 is stored whether authentication is required to confirm the necessity of authentication. Alternatively, the server 20 may attempt to access the server where the file 32 is stored anonymously to confirm whether authentication is required.

[0070] If the storage destination of the related file 32 is a server that requires authentication (step S55: YES), the CPU 21 determines whether the storage destination of the related file 32 is the same as the storage destination of the target file 30 (step S56).

[0071] If the storage destination of the related file 32 is the same as the storage destination of the target file 30 (step S56: YES), the CPU 21 provides the user B with information (e.g., a link) indicating the storage destination of the related file 32 (step S57). If the storage destination of the related file 32 is the same as the storage destination of the target file 30 and information indicating the storage destination of the target file 30 has been provided to the user B, it is considered that authentication is completed when the user B accesses the target file 30. Therefore, since authentication does not occur when accessing the related file 32, it is sufficient to provide information indicating the storage destination of the related file 32.

[0072] When the storage destination of the related file 32 is not the same as the storage destination of the target file 30 (step S56: NO), the CPU 21 provides the related file 32 to the user B (step S58). When the storage destination of the related file 32 is different from the storage destination of the target file 30, since authentication occurs when the user B accesses the related file 32, the user B cannot directly access the related file 32. Therefore, the related file 32 itself is provided to the user B.

[0073] Although not shown in the figure, after step S56, the CPU 21 may determine whether authentication occurs each time the related file 32 is accessed. And when authentication does not occur each time the related file 32 is accessed, information indicating the storage destination of the related file 32 is provided. Also, when authentication occurs each time the related file 32 is accessed, the related file 32 (for example, an object) is provided.

[0074] When the storage destination of the related file 32 is not a server that requires authentication by the user B (step S55: NO), the CPU 21 determines whether the storage destination of the related file 32 is a local folder (step S59). The local folder corresponds to a folder set in the RAM 13 of the first user terminal 10A used by the user A, etc.

[0075] When the storage destination of the related file 32 is a local folder (step S59: YES), the CPU 21 provides the related file 32 to the user B (step S60). When the storage destination of the related file 32 is the local folder of the first user terminal 10A, the user B cannot access the related file 32 stored in the local folder. Therefore, the related file 32 is provided to the user B.

[0076] If the storage destination of the related file 32 is not a local folder (step S59: NO), the CPU 21 proceeds to the process of step S57. That is, the CPU 21 provides the user B with information (e.g., a link) indicating the storage destination of the related file 32 (step S57). If the storage destination of the related file 32 is not a server that requires authentication by the user B (step S55: NO) and the storage destination of the related file 32 is not a local folder (step S59: NO), it is considered that the related file 32 is stored in a server that does not require authentication or a shared folder that can be accessed by anyone without authentication. Therefore, since the user B can access the related file 32, information indicating the storage destination of the related file 32 is provided to the user B.

[0077] After the process of step S57, step S58, or step S60, the CPU 21 ends the process based on the file management program.

[0078] FIG. 7 shows, as an example of a screen displayed on the second user terminal 10B used by the user B, a property dialog of a target document. The target document is an example of a target file, and five related documents are associated with the target file as examples of related files. In the example shown in FIG. 7, the related document 1 stored in the local folder has the related document 1 itself attached to and provided with the target document. The user B can open the related document 1 by clicking on the icon or document name of the related document 1. Also, for the related documents 2 and 3 stored in the shared folder of the server that does not require authentication, links indicating the storage destinations of the related documents 2 and 3 are set. The user B can open the related documents 2 and 3 by clicking on the links. Also, for the related documents 4 and 5 stored in the server that requires authentication, the related documents 4 and 5 themselves are attached to and provided with the target document. The user B can open the related document 4 or the related document 5 by clicking on the icon or document name of the related document 4 or the related document 5.

[0079] FIG. 8 is a flowchart showing the flow of the mode switching process by the server 20 of the file management apparatus 1. The mode switching process is a process of switching the mode of providing related files associated with the target file. The mode switching process is performed by the CPU 21 reading the mode switching program from the ROM 22 or the storage 24, expanding it in the RAM 23, and executing it.

[0080] As an example, after the processing of steps S57, S58, and S60 in the flowchart shown in FIG. 6, the mode switching process shown in FIG. 8 is performed.

[0081] As shown in FIG. 8, the CPU 21 checks the mode of providing the related file 32 to user A (step S71). For example, the CPU 21 causes the first user terminal 10A to display a mode confirmation message for allowing user A to confirm the provision mode of the related file 32 determined in the processing of step S57, step S58, or step S60 shown in FIG. 6. The mode confirmation message displays, for example, whether the "mode of providing related files" is set to either the related file 32 or the information indicating the storage destination of the related file 32. Further, in the mode confirmation message, for example, the user A is allowed to select whether to switch the set "mode of providing related files" to either the related file 32 or the information indicating the storage destination of the related file 32.

[0082] The CPU 21 determines whether it has received a request from user A to switch the mode of providing the related file 32 (step S72). The switching of the mode of providing the related file 32 may be from providing the related file 32 itself to providing the information indicating the storage destination of the related file 32, or from providing the information indicating the storage destination of the related file 32 to providing the related file 32 itself.

[0083] When the form switch for providing the related file 32 is not accepted (step S72: NO), the CPU 21 ends the process based on the form switch program. When the form switch for providing the related file 32 is accepted from user A (step S72: YES), the CPU 21 determines whether the accepted form is information indicating the storage destination of the related file 32 (step S73).

[0084] When the accepted form is information indicating the storage destination of the related file 32 (step S73: YES), the CPU 21 adds the information indicating the storage destination of the related file 32 to the target file 30 and releases the attachment of the related file 32 itself (step S74).

[0085] When the accepted form is not information indicating the storage destination of the related file 32 (step S73: NO), the CPU 21 attaches the related file 32 itself to the target file and deletes the information indicating the storage destination of the related file 32 (step S75). For example, when attaching the target file 30 to an email and sending it to an external company email address, the form set with the information (e.g., link) indicating the storage destination of the related file 32 can be switched to the related file 32 (e.g., object) and sent.

[0086] After the process of step S74 or step S75, the CPU 21 ends the process based on the form switch program.

[0087] FIG. 9 is a flowchart showing the flow of the additional acceptance process by the server 20 of the file management apparatus 1. The additional acceptance process is a process of accepting the addition of the related file 32 associated with the target file 30. The additional acceptance process is performed by the CPU 21 reading the additional acceptance program from the ROM 22 or the storage 24, expanding it in the RAM 23, and executing it. The additional acceptance process is performed independently of the processes shown in FIGS. 6 and 8.

[0088] As shown in FIG. 9, the CPU 21 determines whether or not to accept the addition of the related file 32 related to the target file 30 (step S81). As shown in FIG. 10, the addition of the related file 32 is performed by the addition acceptance screen displayed on the first user terminal 10A. User A adds the file to the related file 32 by selecting the file to be added from among the folders of multiple hierarchies. Thereby, the addition of the related file 32 is accepted.

[0089] When the addition of the related file 32 is not accepted (step S81: N0), the CPU 21 ends the process based on the addition processing program. When the addition of the related file 32 is accepted (step S81: YES), the CPU 21 acquires the form in which the added related file 32 is provided (step S82). As the form in which the added related file 32 is provided, there is an attachment of information indicating the storage destination of the related file 32 or the related file 32 itself.

[0090] As shown in FIG. 10, when User A adds the related file 32, the form in which the added related file 32 is provided is acquired by setting the setting form to either a link (information indicating the storage destination) or a file (object). Thereby, the process based on the addition acceptance program ends.

[0091] In the above file management device 1, when associating the related file 32 related to the target file 30, access to the related file 32 is enabled regardless of the storage location where the related file 32 is stored, and compared with the case where all the related files 32 are attached, the data capacity of the target file 30 can be suppressed.

[0092] The processing of the above user terminal 10 and server 20 can also be realized by a dedicated hardware circuit. In this case, it may be executed by one piece of hardware or may be executed by a plurality of pieces of hardware.

[0093] In each of the above embodiments, the processor refers to a processor in a broad sense, including a general-purpose processor (e.g., CPU: Central Processing Unit, etc.) and a dedicated processor (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.).

[0094] Also, the operation of the processor in each of the above embodiments may be achieved not only by one processor but also by a plurality of physically separated processors cooperating with each other. Also, the order of each operation of the processor is not limited to the order described in each of the above embodiments and may be changed as appropriate.

[0095] Also, the programs for operating the user terminal 10 and the server 20 may be provided by a computer-readable recording medium such as a USB (Universal Serial Bus) memory, a flexible disk, a CD-ROM (Compact Disc Read Only Memory), etc., or may be provided online via a network such as the Internet. In this case, the program recorded on the computer-readable recording medium is usually transferred and stored in a memory or a storage, etc. Also, this program may be provided, for example, as a single application software or incorporated into the software of each device as a function of the user terminal 10 and the server 20.

[0096] Also, in the above embodiment, there is one server 20, but the present invention is also applicable to a file management device including a plurality of servers.

[0097] Although the present invention has been described in detail with respect to specific embodiments, it is obvious to those skilled in the art that the present invention is not limited to such embodiments and that various other embodiments are possible within the scope of the present invention.

Explanation of Symbols

[0098] 1 File Management Device 10 User Terminals 10A User Terminal 10B User Terminal 11, 21 CPU 12, 22 ROM 13, 23 RAM 14, 24 Storage 15 Input Unit 16 Display Unit 17, 25 Communication Interface 19, 29 Bus 20 Server 30 Target File 32 Related File 101 Creation Unit 102 Form Switching Unit 103 Addition Unit 104 Transmission Unit 105 Reception Unit 201 Reception Unit 202 Acquisition Unit 203 File Management Unit 203A File Content Management Unit 203B File Attribute Management Unit 204 Form Confirmation Unit 205 Switching Reception Unit 206 Provision Unit 207 Addition Reception Unit 208 Additional Form Reception Unit 209 Transmission Unit User A User B (An example of a viewer)

Claims

1. Comprising at least one processor, The processor is, Obtain the storage destination of the target file and related files related to the target file and information about the viewer, When the viewer can access the storage destination of the related file, provide the viewer with information indicating the storage destination of the related file; when the viewer cannot access the storage destination of the related file, provide the viewer with the related file. A file management device.

2. The processor according to claim 1, wherein the processor confirms, to the user who manages the target file, the form in which the related file is provided to the viewer.

3. The processor according to claim 2, wherein the processor receives from the user whether to switch the form of providing the related file to the viewer from the information indicating the storage destination to the related file or from the related file to the information indicating the storage destination. File management device.

4. The processor according to claim 2 or claim 3, wherein the processor receives an addition of the related file, and when adding, receives whether to use the information indicating the storage destination or the related file as the form of providing the related file to the viewer. File management device.

5. A step of obtaining information about the target file, the storage destination of related files related to the target file, and the viewer; When the viewer can access the storage destination of the related file, a step of providing the viewer with information indicating the storage destination of the related file; when the viewer cannot access the storage destination of the related file, a step of providing the viewer with the related file; A file management program for causing a computer to execute.

Images