File management system, file management method, and file management program

Abstract

To provide a file shortcut technique for suppressing the occurrence of "broken links."SOLUTION: A file management system is provided with a tracking update unit for updating first link information stored in a first original tracking file and a first link tracking file when a first original file is operated, and a link update unit for updating the first link information stored in a first link file designated by the first link tracking file when the first link information is updated by the tracking update unit.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a file management system, a file management method, and a file management program. [Background technology]

[0002] In computer-related technical fields, a user interface called a file shortcut is used. According to the file shortcut, the computer accesses a storage area of ​​the auxiliary storage device designated by the shortcut in response to a user's operation of the shortcut icon. The computer loads the original file from the accessed storage area into the main storage device.

[0003] The following Patent Document 1 describes a technology related to file shortcuts. In detail, in addition to an original file and a link file, a trace file is stored in a storage means. When the original file is moved or otherwise moved in the storage means, a trace update means rewrites the information in the trace file. A link update means rewrites the information in the link file based on the information in the trace file (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Publication No. 09-288606 Summary of the Invention [Problem to be solved by the invention]

[0005] In the case of a file shortcut according to the background art, even if a user operates the shortcut icon after a specific operation is performed on the original file, the computer may not be able to access the original file. This phenomenon is known as a "broken link."

[0006] The present disclosure aims to provide a file shortcut technology that is less likely to cause link breakage. [Means for solving the problem]

[0007] The file management system of the present disclosure includes a memory unit that stores a first original file storing substantive information, a first link file storing first link information specifying the first original file, a first original tracking file storing the first link information and first link tracking information specifying the first link file, and a first link tracking file storing the first link information, a tracking update unit that updates the first link information stored in the first original tracking file and the first link tracking file when the first original file is operated, and a link update unit that updates the first link information stored in the first link file specified by the first link tracking information when the first link information is updated by the tracking update unit.

[0008] The file management method of the present disclosure includes a storage step of storing a first original file storing substantive information, a first link file storing first link information designating the first original file, a first original tracking file storing the first link information and first link tracking information designating the first link file, and a first link tracking file storing the first link information, a tracking update step of updating the first link information stored in the first original tracking file and the first link tracking file when the first original file is operated, and a link update step of updating the first link information stored in the first link file designated by the first link tracking information when the first link information is updated by the tracking update step.

[0009] The file management program of the present disclosure causes a computer to execute, when a first original file storing substantive information and a first link file storing first link information designating the first original file are created, a storage process for storing a first original tracking file storing the first link information and first link tracking information designating the first link file, and a first link tracking file storing the first link information; a tracking update process for updating the first link information stored in the first original tracking file and the first link tracking file when the first original file is operated; and a link update process for updating the first link information stored in the first link file designated by the first link tracking information when the first link information is updated by the tracking update process. Effect of the Invention

[0010] According to the file management system, file management method, and file management program disclosed herein, a file shortcut technology that is less likely to cause "link breakage" can be provided. [Brief description of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating a configuration of a file management system according to a first embodiment of the present disclosure. [Diagram 2] FIG. 2 is a diagram showing a specific data structure of the shortcut file shown in FIG. [Diagram 3] FIG. 3 is a diagram showing a specific data structure of the entity tracking file shown in FIG. [Figure 4] FIG. 4 is a diagram showing a specific data structure of the link tracking file shown in FIG. [Diagram 5] FIG. 5 is a flow chart of the control unit 1 when creating a new original file. [Figure 6] FIG. 6 is a diagram showing the entity tracking file newly created in step S102 of FIG. [Figure 7]FIG. 7 is a flowchart showing the process of creating a new shortcut file for an original file. [Figure 8] FIG. 8 shows various files after the shortcut file is newly created. [Figure 9] FIG. 9 is a flowchart showing the process of additionally creating a shortcut file for an original file. [Figure 10] FIG. 10 shows various files after the shortcut file has been additionally created. [Figure 11] FIG. 11 is a flowchart showing the process of creating a copy of an original file. [Figure 12] FIG. 12 shows various files after the original file is copied. [Figure 13] FIG. 13 is a flowchart showing a process for creating a new shortcut file for a duplicated file. [Figure 14] FIG. 14 shows various files after the shortcut file is newly created. [Figure 15] FIG. 15 is a flowchart showing the process of moving the original file 26. [Figure 16] FIG. 16 shows various files after the original files are moved. [Figure 17] FIG. 17 is a flowchart showing the process of updating a replicated file. [Figure 18] FIG. 18 is a diagram showing various files after the replicated file is updated. [Figure 19] FIG. 19 is a flowchart showing the process of deleting an original file. [Figure 20] FIG. 20 shows various files after the original files are deleted. [Figure 21] FIG. 21 is a diagram showing a configuration of a file management system 100 according to the second embodiment of the present disclosure. [Figure 22] FIG. 22 is a diagram showing a configuration of the server shown in FIG. [Figure 23] FIG. 23 is a flowchart of each control unit when a shortcut file 27 for an original file is newly created. [Figure 24] FIG. 24 is a flow chart of the control section for changing the file name, etc. of the original file. [Diagram 25] FIG. 25 is a flowchart of the control section when deleting an original file. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] Exemplary embodiments of the present disclosure will now be described with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference characters and description thereof will not be repeated.

[0013] [Configuration of the file management system 100 according to the first embodiment] Fig. 1 is a diagram showing a configuration of a file management system 100 according to a first embodiment of the present disclosure. As shown in Fig. 1, the file management system 100 is typically an information processing device. Examples of the information processing device include a personal computer, a smartphone, and a tablet terminal.

[0014] In detail, the file management system 100 includes a control unit 1 and a storage unit 2. The file management system 100 additionally includes a display unit 3 and an operation unit 4. The control unit 1, the storage unit 2, the display unit 3 and the operation unit 4 are connected to each other so as to be able to communicate with each other via an external bus 5. Note that, although reference numeral "200" and a communication IF 6 are shown in FIG. 1, these are used in the second embodiment.

[0015] The control unit 1 controls each unit of the file management system 100. The control unit 1 includes a central processing unit or a microcomputer, and executes various programs described below. The control unit 1 is an example of a "computer" in this disclosure.

[0016] The storage unit 2 includes a hard disk drive and / or a semiconductor memory, and stores various programs and various files. The storage unit 2 is an example of the "storage unit" in this disclosure.

[0017] The various programs typically include an operating system 21, a file management program 22, and an application program 23. Below, the operating system 21, the file management program 22, and the application program 23 may be referred to as "OS 21," "program 22," and "app 23," respectively.

[0018] The program 22 is an application program. The app 23 is an application program different from the program 22. The application program is a program created according to a specific function desired by the user. The OS 21, the program 22, and the app 23 are executed by the control unit 1.

[0019] Various programs can be stored and provided to a computer using a non-transitory computer readable medium. The non-transitory computer readable medium includes various tangible storage media. Examples of the non-transitory computer readable medium include a flexible disk, a magnetic tape, a hard disk drive, a magneto-optical disk, a CD-ROM, a CD-R, a CD-R / W, and a semiconductor memory.

[0020] In addition, various programs may be provided to the computer by various kinds of transitory computer readable media. Examples of the transitory computer readable medium include an electric signal, an optical signal, and an electromagnetic wave. The transitory computer readable medium can provide the program to the computer via a wired communication path such as an electric wire and an optical fiber, or via a wireless communication path.

[0021] Files are collections of electronic data, which is data for use in computer processing and can be stored on non-transitory or transitory computer-readable media.

[0022] The various files include an original file 26 , a shortcut file 27 , an entity tracking file 28 , and a link tracking file 29 .

[0023] Among the various files, the entity tracking file 28 and the link tracking file 29 are so-called hidden files. That is, the control unit 1 that executes the program 22 does not display the hidden files on the display unit 3. This makes it possible to prevent the entity tracking file 28 and the link tracking file 29 from being deleted or changed according to user operations.

[0024] In detail, the original file 26 stores substantial information. The substantial information is data that the control unit 1 can access by a file shortcut. The file shortcut is a function provided by the OS 21. A first example of the original file 26 is an electronic file created by an application in response to a user operation. The electronic file is created by the application 23 or by another information processing device different from the file management system 100. A second example of the original file 26 is a folder created by the OS 21 in response to a user operation.

[0025] Here, the various files may include a duplicated file 25. The duplicated file 25 is a duplicate of an original file 26. Therefore, the duplicated file 25 stores the same substantive information as the original file 26 at the time of creating the duplicated file 25. The duplicated file 25 is created by the OS 21 and the application 23 in response to a user operation.

[0026] The shortcut file 27 is an example of any one of the "first link file," "second link file," and "third link file" of the present disclosure. The shortcut file 27 is an electronic file solely for opening the target electronic file. The target electronic file is the original file 26 or the duplicated file 25. The shortcut file 27 stores link information 271. The link information 271 is information that specifies the target electronic file. In detail, the link information 271 is a full path name that indicates the location in the memory unit 2 of the target electronic file.

[0027] The entity tracking file 28 is preferably managed together with the target electronic file. For example, the entity tracking file 28 is metadata of the target electronic file. This metadata is a so-called property of the target electronic data, and is information such as the state or attributes of the target electronic file. By treating the entity tracking file 28 as metadata, it becomes easy to associate (link) the entity tracking file 28 with the target electronic file.

[0028] Specifically, the entity tracking file 28 stores link information 281 and link tracking information 282. The link information 281 is similar to the link information 271. The link tracking information 282 is information that specifies the shortcut file 27. Specifically, the link tracking information 282 indicates the full path name that indicates the location of the target shortcut file 27.

[0029] The link tracking file 29 is preferably managed together with the shortcut file 27. The link tracking file 29 is created every time a shortcut file 27 is newly created. For example, the link tracking file 29 is metadata of the shortcut file 27. This metadata is so-called properties of the shortcut file 27. By treating the link tracking file 29 as metadata, it becomes easy to associate the link tracking file 29 with the shortcut file 27.

[0030] The link tracking file 29 stores link information 291. The link information 291 is similar to the link information 271.

[0031] The display unit 3 displays various information and is a liquid crystal display, an organic EL display, or the like.

[0032] The operation unit 4 accepts operations by a user of the file management system 100. The operation unit 4 is an input device such as a mouse and a keyboard.

[0033] [Data structure of shortcut file 27] Fig. 2 is a diagram showing a specific data structure of the shortcut file 27 shown in Fig. 1. As shown in Fig. 2, the shortcut file 27 stores link information 271 and sequential number information 272. The sequential number information 272 is information indicating the order in which the shortcut files 27 were created, and is also information indicating a priority level, which will be described later. In Fig. 2, "1" is shown as the sequential number information 272. The link information 271 is as described above. In Fig. 2, the full path name of the target electronic file, i.e., the original file 26 or the duplicated file 25, is shown as the link information 271.

[0034] [Data structure of entity tracking file 28] Fig. 3 is a diagram showing a specific data structure of the entity tracking file 28 shown in Fig. 1. As shown in Fig. 3, the entity tracking file 28 is created by the program 22 every time a target electronic file is created. The entity tracking file 28 stores link information 281 and serial number information 283 for the target electronic file. The link information 281 and the serial number information 283 are similar to the link information 271 and the serial number information 272.

[0035] The entity tracking file 28 can further store link tracking information 282 and sequence number information 285 for each shortcut file 27 that is created.

[0036] The sequential number information 285 is information indicating the order in which the corresponding link tracking information 282 was created, and is also information indicating the priority, which will be described later. In FIG. 3, "ii-1" is shown as one piece of sequential number information 285. The link tracking information 282 is as described above. In FIG. 3, the link tracking information 282 is the full path name of the shortcut file 27. In FIG. 3, "full path name of shortcut file 27(1)" is shown as the link tracking information 282 corresponding to "ii-1" as the sequential number information 285.

[0037] Furthermore, each time a duplicate file 25 of a target electronic file is created, the entity tracking file 28 can store duplicate link information 287 and serial number information 288 for the duplicate file 25. The duplicate link information 287 is information indicating the location of the duplicate file 25 in the storage unit 2.

[0038] The sequential number information 288 is information indicating the order in which the duplicated files 25 were created, and is also information indicating the priority, which will be described later. In FIG. 3, "iii-1" is shown as one piece of sequential number information 288. The duplicated link information 287 is as described above. In FIG. 3, the duplicated link information 287 is the full path name of the corresponding duplicated file 25. In FIG. 3, "the full path name of duplicated file 25(1)" is shown as the duplicated link information 287 corresponding to "iii-1" as the sequential number information 288.

[0039] [Data structure of link tracking file 29] Fig. 4 is a diagram showing a specific data structure of the link tracking file 29 shown in Fig. 1. As shown in Fig. 4, the link tracking file 29 stores link information 291 and sequential number information 292, similar to the shortcut file 27.

[0040] The link tracking file 29 can further store duplicate link information 294 and sequence number information 295 for each duplicate file 25 created. The duplicate link information 294 is similar to the duplicate link information 287.

[0041] The sequential number information 295 is information indicating the order in which the duplicated files 25 were created, and is also information indicating priority, which will be described later. In FIG. 4, "1" is shown as one piece of sequential number information 295. The duplicated link information 294 is as already explained. In FIG. 4, the duplicated link information 294 is the full path name of the corresponding duplicated file 25. In FIG. 4, "the full path name of duplicated file 25(1)" is shown as the duplicated link information 294 corresponding to "1" as the sequential number information 295.

[0042] [Processing of control unit 1] The processing of the control unit 1 will be described below. For ease of explanation, the "control unit 1 executing OS 21" may be referred to as "OS 21." The "control unit 1 executing program 22" may be referred to as "program 22." The "control unit 1 executing application 23" may be referred to as "application 23."

[0043] [New creation of original file 26] Fig. 5 is a flowchart of the control unit 1 when creating a new original file 26. Fig. 6 is a diagram showing an entity tracking file 28 newly created in step S102 of Fig. 5.

[0044] As shown in FIG. 5, in step S101, the control unit 1 newly creates an original file 26. As a specific example of step S101, first, the application 23 creates the original file 26 in accordance with a user operation. In response to the application 23 accepting a user operation for saving the original file 26, the OS 21 allocates an available memory area A in the storage unit 2 to the original file 26. The OS 21 further saves the original file 26 in the memory area A. This ends step S101. Note that the OS 21 may also save the original file 26 transmitted from another information processing device in a memory area of ​​the storage unit 2.

[0045] Next, in step S102, the program 22 creates an entity tracking file 28 (see FIG. 6) for the newly created original file 26 in the available memory area B of the memory unit 2. In step S102, the entity tracking file 28 storing the link information 281 is created. Therefore, at the end of step S102, the link tracking information 282 and the duplicate link information 287 are "Null". In addition, the link information 281 is the full path name of the original file 26.

[0046] [Create new shortcut file 27] Fig. 7 is a flowchart of the control unit 1 when a shortcut file 27 is newly created for an original file 26. Fig. 8 is a diagram showing the shortcut file 27 newly created in step S201 shown in Fig. 7, the entity tracking file 28 updated in step S202 in the same figure, and the link tracking file 29 newly created in step S203 in the same figure.

[0047] As shown in Fig. 7, in step S201, the OS21 newly creates a shortcut file 27. In detail, the OS21 accepts a user operation for creating the shortcut file 27 from the operation unit 4. In response to this, the OS21 newly creates a shortcut file 27 that stores link information 271. The link information 271 is a full path name indicating the location in the storage unit 2 of the original file 26 (see step S101 in Fig. 5) (see Fig. 8). The OS21 further stores the newly created shortcut file 27 in an available storage area C in the storage unit 2.

[0048] In step S202, the program 22 updates the entity tracking file 28. In detail, the program 22 additionally stores the link tracking information 282 (see FIG. 8) of the newly created shortcut file 27 in the entity tracking file 28. In FIG. 8, the full path name of the target shortcut file 27 is illustrated as the link tracking information 282.

[0049] In step S203, the program 22 newly creates a link tracking file 29. In detail, link information 291 (see FIG. 8) is stored in the link tracking file 29. At the end of step S203, the duplicate link information 294 in the link tracking file 29 is Null.

[0050] The original file 26 and the shortcut file 27 are bidirectionally associated with each other by the entity tracing file 28 updated in step S202.

[0051] [Additional shortcut file 27] Fig. 9 is a flowchart of the control unit 1 when a shortcut file 27 is additionally created for an original file 26. Fig. 10 is a diagram showing the shortcut file 27 additionally created in step S301 shown in Fig. 9, the entity tracking file 28 updated in step S302 in the same figure, and the link tracking file 29 additionally created in step S303 in the same figure.

[0052] As shown in FIG. 9, in step S301, the OS 21 additionally creates a shortcut file 27 for the original file 26 and stores it in the available storage area D in the storage unit 2 (step S301). Hereinafter, the shortcut file 27 created in step S301 will be referred to as "shortcut file 27B" (see FIG. 10). Meanwhile, the shortcut file 27 created in step S201 (see FIG. 7) will be referred to as "shortcut file 27A" (see FIG. 10). The shortcut files 27A and 27B are separate electronic files, but store the same link information 271. Note that step S301 is an example of "when a first link file is newly created as a second link file" in this disclosure.

[0053] In step S302, the program 22 updates the entity tracking file 28 so that the link tracking information 282 stored in the entity tracking file 28 also designates the shortcut file 27B. In detail, the program 22 additionally stores the link tracking information 282 of the shortcut file 27B created in step S301 in the entity tracking file 28 (see FIG. 10).

[0054] In step S303, the program 22 additionally creates a link tracking file 29 storing link information 291 in correspondence with the shortcut file 27B. Hereinafter, the link tracking file 29 created in step S303 will be referred to as a "link tracking file 29B" (see FIG. 10). In contrast, the link tracking file 29 created in step S203 (see FIG. 7) will be referred to as a "link tracking file 29A" (see FIG. 10). The link tracking files 29A and 29B are separate electronic files, and store different link information 291. In detail, the link tracking file 29B stores the link information 291 of the shortcut file 27 newly created in step S301. At the end of step S303, the duplicated link information 294 of the link tracking file 29B is Null.

[0055] Through steps S201 to S203, the original file 26 is associated with the shortcut files 27A and 27B.

[0056] [Copy of original file 26] Fig. 11 is a flowchart of the control unit 1 when creating a copy of the original file 26. Fig. 12 is a diagram showing the entity tracking file 28 updated in step S402 shown in Fig. 11, the entity tracking file 28 newly created in step S403 in the same figure, and the link tracking file 29 updated in step S404 in the same figure.

[0057] As shown in Fig. 11, in step S401, the OS 21 newly creates a duplicated file 25. As a specific example of step S401, first, the application 23 or the OS 21 creates the duplicated file 25, which is a duplicate of the original file 26, in response to a user operation for creating a duplicate of the original file 26. The OS 21 further allocates an available memory area D in the storage unit 2 to the duplicated file 25. The OS 21 further saves the duplicated file 25 in the allocated memory area D. Therefore, step S401 is an example of "a case in which the first original file is newly duplicated as a first duplicated file" in the present disclosure.

[0058] In step S402, the program 22 functions as the "tracing update unit" of the present disclosure, and updates the entity tracing file 28. In detail, the program 22 additionally stores the duplication link information 287, which is a full path name indicating the location of the duplicated file 25 in the storage unit 2, in the entity tracing file 28 created in step S202 (see FIG. 7).

[0059] In step S403, the program 22 functions as a "tracking update unit" of the present disclosure and creates a new entity tracking file 28 (an example of a "first duplicate tracking file" of the present disclosure). In detail, the program 22 creates a new entity tracking file 28 in the available memory area E of the memory unit 2 in correspondence with the duplicate file 25 created in step S401. Hereinafter, the entity tracking file 28 created in step S403 will be referred to as an "entity tracking file 28B" (see FIG. 12). Meanwhile, the entity tracking file 28 updated in step S202 (see FIG. 7) will be referred to as an "entity tracking file 28A" (see FIG. 12). The entity tracking files 28A and 28B are separate electronic files. In FIG. 12, the full path name of the duplicate file 25 created in step S401 is illustrated as link information 281 in the entity tracking file 28B. Also, in FIG. 12, the full path name of the original file 26, which is a copy as viewed from the copy file 25, is illustrated as copy link information 287 in the entity tracing file 28B.

[0060] In step S404, the program 22 updates the link tracking file 29 (step S404). In detail, the program 22 additionally stores, in the link tracking file 29 created in step S203, copy link information 294 indicating the location of the copy file 25 in the storage unit 2 by a full path name, and sequence number information 295 (see FIG. 4, an example of "priority" in the present disclosure).

[0061] Through steps S401 to S404, the control unit 1 associates the original file 26, the duplicated file 25, and the link tracking file 29 with each other.

[0062] [Create a new shortcut file 27 for the duplicate file 25] Fig. 13 is a flowchart of the control unit 1 when a shortcut file 27 is newly created for the duplicated file 25. Fig. 14 is a diagram showing the shortcut file 27C newly created in step S501 shown in Fig. 13, the entity tracking file 28B updated in step S502 in the same figure, and the link tracking file 29C newly created in step S503.

[0063] As shown in FIG. 13, in step S501, the OS 21 creates a new shortcut file 27 for the duplicated file 25. The method of creating the shortcut file 27 may be the same as that in step S201 (see FIG. 7). The OS 21 stores the shortcut file 27 created in step S501 in the available storage area F in the storage unit 2. Hereinafter, the shortcut file 27 created in step S501 will be referred to as a "shortcut file 27C" (see FIG. 14). In the shortcut file 27C, the link information 271 in particular is a full path name indicating the location of the duplicated file 25 in the storage unit 2. Step S501 is an example of "a case where a third link file storing second link information specifying a first duplicated file is newly created" in the present disclosure.

[0064] In step S502, the program 22 functions as an example of a "tracing update unit" of the present disclosure, and updates the entity tracing file 28B. In detail, the program 22 additionally stores link tracing information 282 that specifies the shortcut file 27C (an example of the "third link file" of the present disclosure) created in step S501 in the entity tracing file 28B. In FIG. 14, a full path name indicating the location of the shortcut file 27C in the storage unit 2 is illustrated as the link tracing information 282.

[0065] In step S503, the program 22 functions as an example of a "tracing update unit" of the present disclosure, and creates a new link tracing file 29. Hereinafter, the link tracing file 29 created in step S503 will be referred to as a "link tracing file 29C" (an example of a "third link tracing file" of the present disclosure) (see FIG. 14). The link tracing files 29A and 29C are separate electronic files, but store different link information 291 and duplicated link information 294. In detail, the link tracing file 29C stores the link information 291 of the shortcut file 27C newly created in step S501. The link tracing file 29C additionally stores duplicated link information 294 indicating the location of the original file 26, which is a duplicate from the duplicated file 25, by a full path name.

[0066] By steps S501 to S503, the files other than the shortcut files 27A and 27C are associated with each other.

[0067] [Processing when moving original file 26] Fig. 15 is a flowchart of the control unit 1 when moving the original file 26. Fig. 16 is a diagram showing the entity tracing files 28A, 28B and the link tracing files 29A, 29C after the original file 26 has been moved.

[0068] 15, in step S601, the OS 21 changes the location of the original file 26 in the storage unit 2 in response to a user operation to move the original file 26. The movement of the original file 26 is an example of "when the first original file is operated" in the present disclosure, and is an example of "when the first original file is moved" in the present disclosure.

[0069] In step S602, program 22 functions as the "tracking update unit" of the present disclosure, and updates the pre-movement link information 281 (i.e., the full path name of the original file 26 before the move) in entity tracking files 28A, 28B (see FIG. 14) to post-movement link information 281 (i.e., the full path name of the original file 26 after the move) as shown in FIG. 16.

[0070] As described above, the entity tracking file 28 is managed as, for example, metadata together with the target electronic file. Therefore, in step S602, the entity tracking file 28 is moved to the same location as the original file 26. This makes it easy to associate (link) the entity tracking file 28 with the target electronic file.

[0071] Furthermore, in step S603, the program 22 functions as the "tracing update unit" of the present disclosure, and updates the link information 291 before the movement in the link tracing file 29A (i.e., the full path name of the original file 26 before the movement) to the link information 291 after the movement as shown in Fig. 16. Similarly, the program 22 functions as the "tracing update unit" of the present disclosure, and updates the link information 291 before the movement in the link tracing file 29C (i.e., the full path name of the duplicated file 25 before the movement) to the link information 291 after the movement as shown in Fig. 16.

[0072] In step S604, the program 22 functions as the "link update unit" of the present disclosure, and when each link information 281, 291 is updated in steps S602, S603, the program 22 updates the link information 291 in each of the shortcut files 27A, 27C specified in the link tracking files 29A, 29C to the link information 291 updated in step S603.

[0073] In this way, the entity tracing files 28A, 28B and the link tracing files 29A, 29C store the link information 281, 291 of the original file 26 after movement. Therefore, the shortcut files 27A, 27C can provide a file shortcut technique that is less likely to cause "link breakage."

[0074] [Processing when updating replicated file 25] Fig. 17 is a flowchart of the control unit 1 when updating the duplicated file 25. Fig. 18 is a diagram showing the entity tracing files 28A, 28B and the link tracing files 29A, 29C after the duplicated file 25 has been updated.

[0075] 17, in step S701, the OS 21 updates the duplicated file 25. The update of the duplicated file 25 is an example of "when the first duplicated file is updated" in the present disclosure. In detail, in response to the application 23 accepting a user operation for updating the duplicated file 25, the OS 21 saves the updated duplicated file 25 in an available memory area G in the storage unit 2. The memory area G may be the same as or different from the memory area D.

[0076] In step S702, the program 22 functions as a "tracing update unit" of the present disclosure. The program 22 updates the pre-update copy link information 287 in the entity tracing file 28A to the post-update copy link information 287 as shown in FIG. 18. Here, the entity tracing file 28A is an example of the "first original tracing file" of the present disclosure. The pre-update copy link information 287 is the full path name of the pre-update copy file 25. The post-update copy link information 287 is the full path name of the post-update copy file 25.

[0077] Furthermore, in step S703, the program 22 functions as a "tracing update unit" of the present disclosure. The program 22 updates the pre-update link information 281 in the entity tracing file 28B to the post-update link information 281. Here, the entity tracing file 28B is an example of the "first replication tracing file" of the present disclosure. The pre-update link information 281 is the full path name of the replication file 25 before the update. The post-update link information 281 is the full path name of the replication file 25 after the update (see FIG. 18).

[0078] In step S703, the program 22 further updates the pre-update link tracking information 282 in the entity tracking file 28B to the post-update link tracking information 282. The pre-update link tracking information 282 is the full path name of the pre-update shortcut file 27C. The post-update link tracking information 282 is the full path name of the post-update shortcut file 27C (see FIG. 18).

[0079] In step S704, the program 22 updates the link tracking file 29A. In detail, the duplicated link information 294 of the link tracking file 29A is updated to the full path name of the original file 26 instead of the full path name of the duplicated file 25 (see FIG. 18).

[0080] In step S705, the program 22 further updates the link tracking file 29A. In detail, the link information 291 of the link tracking file 29A is updated to the full path name of the shortcut file 27C instead of the full path name of the shortcut file 27A (see FIG. 18).

[0081] In step S706, the program 22 updates the link tracking file 29C (an example of a "third link tracking file" in this disclosure). In detail, the link information 291 of the link tracking file 29C is updated to the full path name of the shortcut file 27C.

[0082] When steps S705 and S706 are executed, each of the link tracking files 29A and 29C may store a plurality of link information 291. In this case, in step S705, the link information 291 including the highest priority sequence number information 292 is processed from among the plurality of link information 291 in the link tracking file 29A. In step S706, the link information 291 corresponding to the highest priority sequence number information 292 is processed from among the plurality of link information 291 in the link tracking file 29C.

[0083] When the duplicated file 25 is updated in steps S701 to S706, the updated duplicated file 25 takes the position of the original file 26. On the other hand, after the duplicated file 25 is updated, the original file 26 takes the position of the duplicated file 25.

[0084] In step S707, the program 22 generates image data indicating that an updated duplicate file 25 exists. The program 22 passes the image data to the OS 21 through an API provided by the OS 21. The OS 22 functions as a "display control unit" in this disclosure, and transfers the image data to the display unit 3. The display unit 3 displays that an updated duplicate file 25 exists based on the image data. This notifies the user that an updated duplicate file 25 exists.

[0085] [Processing when deleting original file 26] Fig. 19 is a flowchart of the control unit 1 when deleting the original file 26. Fig. 20 is a diagram showing various files after the original file 26 is deleted.

[0086] 19, in step S801, the OS 21 deletes the original file 26. The deletion of the original file 26 is an example of "when the first original file is deleted" in the present disclosure. In detail, in response to receiving a user operation to delete the original file 26, the OS 21 releases the storage area of ​​the original file 26 in the storage unit 2 and makes it available.

[0087] In step S802, the program 22 deletes the entity tracking file 28A. In detail, the program 22 releases the memory area B of the entity tracking file 28A in the memory unit 2 and makes it available for use. In the embodiment, since the entity tracking file 28A is a property of the original file 26, the entity tracking file 28A is deleted in step S801 (see FIG. 20). In FIG. 20, the deletion of the entity tracking file 28A is represented by a strikethrough.

[0088] In step S803, the program 22 updates the link information 281 (i.e., the full path name of the original file 26) in each entity tracking file 28 (specifically, the entity tracking file 28B) to “Null.” That is, step S803 is an example of “removing the first original file from the first copy link information stored in the first copy tracking file” of the present disclosure.

[0089] In step S804, the program 22 updates the link information 291 stored in the link tracking file 29A from the full path name of the shortcut file 27A to the full path name of the shortcut file 27C (ie, the full path name of the duplicated file 25).

[0090] In step S805, the program 22 updates the duplicated link information 294 stored in the link tracking file 29A to the full path name of the shortcut file 27C (ie, the full path name of the duplicated file 25).

[0091] In step S806, the program 22 updates the duplicate link information 294 stored in the link tracking file 29C to the full path name of the original file 26 to "Null".

[0092] Even if the original file 26 is deleted, the duplicate file 25 remains through steps S801 to S806, so the program 22 can update the entity tracing file 28B and the link tracing file 29 appropriately.

[0093] In step S807, the program 22 passes the display mode of the icon of the shortcut file 27C or the duplicated file 25 to the OS 21 by the API. The OS 21 changes the display mode of the icon of the shortcut file 27C or the duplicated file 25 and displays these icons on the display unit 3. This allows the user to visually recognize the shortcut file 27 and the duplicated file 25 that are being processed.

[0094] [Configuration of the file management system 100 according to the second embodiment] Fig. 21 is a diagram showing a configuration of a file management system 100 according to the second embodiment of the present disclosure. As shown in Fig. 21, the file management system 100 includes a plurality of information processing devices 200 and a server 300. The plurality of information processing devices 200 and the server 300 are connected to each other via a network 400 so as to be able to communicate with each other.

[0095] 1, each information processing device 200 differs from the file management system 100 (i.e., the information processing device) of the first embodiment in that it further includes a communication interface (hereinafter, referred to as "communication IF") 6 and that the storage unit 2 stores a program 51 instead of a program 22. Therefore, a description of the control unit 1, the display unit 3, and the operation unit 4 will be omitted.

[0096] The communication IF 6 performs two-way data communication with the server 300 via the network 400. In detail, the communication IF 6 transmits various data received from the control unit 1 to the network 400 in accordance with a communication protocol. The communication IF 6 receives various data from the network 400 in accordance with the communication protocol and transfers it to the control unit 1.

[0097] The storage unit 2 further stores various files, including a shortcut file 27 (see FIG. 2) and a link tracking file 29 (see FIG. 4).

[0098] Fig. 22 is a diagram showing a configuration of the server 300 shown in Fig. 21. As shown in Fig. 22, the server 300 includes a control unit 7, a storage unit 8, and a communication IF9.

[0099] The control unit 7 controls each unit of the server 300. The control unit 7 executes various programs, similar to the control unit 1. The control unit 7 is another example of the "computer" in this disclosure.

[0100] The storage unit 8 stores various programs and various files. The storage unit 8 is another example of the “storage unit” in the present disclosure.

[0101] The various programs typically include an OS 81, a program 82, and an application 83. The program 82 is an application program. The application 83 is an application program different from the program 82. The OS 81, the program 82, and the application 83 are executed by the control unit 7.

[0102] The various files include original files 26 and entity tracking files 28. The various files may also include duplicate files 25.

[0103] In detail, the original file 26 is data that can be accessed by each information processing device 200 via a file shortcut.

[0104] The entity tracing file 28 stores link information 281 and link tracing information 282 (see FIG. 3). The link information 281 is similar to the link information 271.

[0105] [Processing of control units 1 and 7] The processing of the control units 1 and 7 will be described below. For ease of explanation, the "control unit 1 executing program 51" may be referred to as the "program 51." The "control unit 7 executing OS 81" may be referred to as the "OS 81." Furthermore, the "control unit 7 executing program 82" may be referred to as the "program 82." The "control unit 7 executing application 83" may be referred to as the "application 83."

[0106] [New creation of original file 26] The operation of the control units 1 and 7 when creating a new original file 26 will be described below with reference to FIGS.

[0107] 5, in step S101, the control unit 1 in any one of the plurality of information processing devices 200 creates a new original file 26. As a specific example of step S101, first, the application 23 creates the original file 26 in accordance with a user operation. In response to the application 23 accepting a user operation for saving the original file 26 in the server 300, the OS 21 executes a process for transmitting the original file 26 to the server 300. Under the control of the OS 21, the communication IF 6 sends the original file 26 to the network 400 in accordance with a communication protocol.

[0108] In the server 300, when the communication IF 9 receives the original file 26, it transfers it to the control unit 7 under the control of the OS 81. The OS 81 allocates an available memory area A in the memory unit 8. The OS 81 further stores the original file 26 in the memory area A. This ends step S101. Note that the OS 21 may also store the original file 26 transmitted from another information processing device in the memory area of ​​the memory unit 2.

[0109] Next, in step S102, the program 82 creates a new entity tracking file 28 (see FIG. 6) for the newly created original file 26 in the available memory area B of the memory unit 8. In step S102, the entity tracking file 28 storing the link information 281 is created. Therefore, at the end of step S102, the link tracking information 282 and the duplicate link information 287 are "Null". In addition, the link information 281 is the full path name of the original file 26.

[0110] [Create new shortcut file 27] Fig. 23 is a flowchart of the control units 1, 7 when creating a new shortcut file 27 for the original file 26. Fig. 23 differs from Fig. 7 in that it further includes step S206 and includes step S207 instead of step S202.

[0111] As shown in Fig. 23, step S206 is executed immediately after step S201. In step S206, the program 51 passes the link tracking information 282 (see Fig. 8) of the newly created shortcut file 27 to the OS 21 in order to cause the program 82 of the server 300 to update the entity tracking file 28. Under the control of the OS 21, the communication IF 6 sends the link tracking information 282 to the network 400 in accordance with the communication protocol.

[0112] In step S207, when the communication IF 9 of the server 300 receives the link tracking information 282, it transfers it to the control unit 7 under the control of the OS 81. The program 82 updates the entity tracking file 28 (see FIG. 8). In detail, the program 22 additionally stores the link tracking information 282 (see FIG. 8) of the newly created shortcut file 27 in the entity tracking file 28. In FIG. 8, the full path name of the target shortcut file 27 is illustrated as the link tracking information 282.

[0113] In step S203, the program 51 creates a new link tracking file 29.

[0114] The original file 26 and the shortcut file 27 are bidirectionally associated with each other by the entity tracing file 28 updated in step S207.

[0115] Here, when each of the multiple information processing devices 200 creates a shortcut file 27 for the same original file 26, the entity tracing file 28 of the server 300 stores the link tracing information 282 of each information processing device 200.

[0116] [Processing when changing the file name, etc. of original file 26] First, hereinafter, "the file name, etc. of the original file 26" includes not only the file name but also the location of the original file 26.

[0117] FIG. 24 is a flow chart of the control units 1 and 7 for changing the file name etc. of the original file 26.

[0118] 24, in step S901, the OS 81 of the server 300 changes the file name, etc., of the original file 26 in response to, for example, a user operation on any of the multiple information processing devices 200. Changing the file name, etc. of the original file 26 is another example of "when the first original file is operated" in the present disclosure, and is another example of "when the first original file is moved" in the present disclosure.

[0119] In step S902, the program 82 functions as the "tracking update unit" of the present disclosure, and updates the link information 281 before the change in the entity tracking file 28 (i.e., the full path name of the original file 26 before the change) to the link information 281 after the change (i.e., the full path name of the original file 26 after the change). As described above, the entity tracking file 28 is managed as, for example, metadata together with the target electronic file.

[0120] Furthermore, in step S903, the program 82 functions as a "tracing update unit" of the present disclosure, and passes the changed link information 281 (full path name of the original file 26 after movement) to the OS 81 in order to cause each program 51 of the multiple information processing devices 200 to update the link tracing file 29. Under the control of the OS 81, the communication IF 9 sends the link information 281 to the network 400 in accordance with the communication protocol. Note that if a transmission error occurs in the link information 281, the OS 81 may execute retransmission control of the link information 281.

[0121] In step S904, when the communication IF 6 in each information processing device 200 receives the link information 281, it transfers it to the control unit 1 under the control of the OS 21. The program 51 updates the link tracking file 29 of the own device (i.e., the information processing device) 200. In detail, the program 51 updates the link information 291 in the link tracking file 29 with the received link information 281 (i.e., the full path name of the original file 26 after the change).

[0122] In step S905, in each of the multiple information processing devices 200, the program 51 functions as the “link update unit” of the present disclosure, and when each link information 281, 291 is updated in steps S903 and S904, the link information 291 in the shortcut file 27 specified in the link tracking file 29 is updated to the link information 291 updated in step S904.

[0123] [Processing when deleting original file 26] FIG. 25 is a flow chart of the control units 1 and 7 when the original file 26 is deleted.

[0124] Before the process of FIG. 25 is started, the memory unit 8 stores the original file 26 and the duplicated file 25 of the original file 26. Therefore, the memory unit 8 also stores entity tracking files 28A and 28B. The entity tracking file 28A is the entity tracking file 28 of the original file 26. Also, the entity tracking file 28B is the entity tracking file 28 of the duplicated file 25. The detailed data structure of the entity tracking file 28 is as shown in FIG. 3, so a detailed description thereof will be omitted.

[0125] 25 is started, a shortcut file 27A is stored in the storage unit 2 of the first information processing device 200. The first information processing device 200 is one of the multiple information processing devices 200. The shortcut file 27A is a shortcut file 27 of the original file 26. Therefore, a link tracking file 29A of the original file 26 is stored in the storage unit 2.

[0126] 25 is started, a shortcut file 27B is stored in the storage unit 2 of the second information processing device 200. The second information processing device 200 is one information processing device 200 different from the first information processing device 200. The shortcut file 27B is a shortcut file 27 of the duplicated file 256. Therefore, a link tracking file 29B of the duplicated file 256 is stored in the storage unit 2.

[0127] 25 is started, a user operation for deleting the original file 26 is performed in any one of the information processing devices 200. In the information processing device 200, the communication IF 6 transmits a request for deleting the original file 26 to the network 400 under the control of the OS 21.

[0128] In the server 300, in response to receiving a deletion request via the communication IF 9 and the OS 81, the program 82 starts the process of FIG. 25, that is, updating of various files.

[0129] In step S1001, the program 82 obtains the link tracing information 282 (ie, the full path name of the shortcut file 27) from the entity tracing file 28A of the original file 26 to be deleted.

[0130] In step S1002, the program 82 identifies the information processing device 200 that stores the shortcut file 27 of the original file 26, that is, the first information processing device 200, from the link tracking information 282 acquired in step S1001.

[0131] Furthermore, in step S1002, under the control of the OS 81, the communication IF 9 sends a deletion request to the network 400 to cause the information processing device (i.e., the first information processing device) 200 identified in step S1002 to delete the link information 291 from the link tracking file 29A.

[0132] In step S1003, in the first information processing apparatus 200, when the program 51 receives the deletion request from the network 400 via the communication IF 6 and the OS 81, the program 51 deletes the link information 291 from the link tracking file 29A via the OS 81.

[0133] In step S1004, the program 82 of the server 300 obtains the duplicate link information 287 (ie, the full path name of the duplicate file 25) from the entity tracing file 28A.

[0134] In step S1005, the program 82 obtains the link tracing information 282 (ie, the full path name of the shortcut file 27) from the entity tracing file 28B.

[0135] In step S1006, the program 82 identifies the information processing device 200 that stores the shortcut file 27 of the duplicated file 25, that is, the second information processing device 200, from the link tracking information 282 acquired in step S1005.

[0136] Furthermore, in step S1006, the communication IF9, under the control of the OS81, sends a deletion request to the network 400 to cause the information processing device (i.e., the second information processing device) 200 identified in step S1002 to delete the link information 291 from the link tracking file 29B.

[0137] In step S1007, in the second information processing apparatus 200, when the program 51 receives the deletion request from the network 400 via the communication IF 6 and the OS 81, the program 51 deletes the link information 291 from the link tracking file 29B via the OS 81.

[0138] In step S1008, the program 82 deletes the link tracing information 282 (ie, the full path name of the shortcut file 27) from the entity tracing file 28B.

[0139] In step S1009, in the first information processing device 200, the program 51 updates the link tracing file 29A through the OS 81. In detail, in the link tracing file 29A, the link information 291 of the duplicated file 25 is changed to the link information 291 of the new original file 26. Furthermore, in the link tracing file 29A, the sequence number information 295 (see FIG. 4) of the link information 291 of the duplicated file 25 is updated.

[0140] In step S1010, in the second information processing device 200, the program 51 updates the link tracing file 29B via the OS 81. In detail, in the link tracing file 29A, the sequence number information 295 (see FIG. 4) of the link information 291 of the duplicate file 25 is updated.

[0141] In step S1011, the program 82 deletes the entity tracking file 28A.

[0142] The embodiments of the present disclosure have been described above with reference to the drawings. However, the present disclosure is not limited to the above-mentioned embodiments, and can be implemented in various aspects without departing from the gist of the disclosure. In addition, various disclosures can be formed by appropriately combining multiple components disclosed in the above-mentioned embodiments. For example, some components may be deleted from all components shown in the embodiments. Furthermore, components across different embodiments may be appropriately combined. The drawings are mainly shown schematically for ease of understanding, and the thickness, length, number, spacing, etc. of each component shown in the drawings may differ from the actual ones due to the convenience of drawing. In addition, the material, shape, dimensions, etc. of each component shown in the above-mentioned embodiments are examples and are not particularly limited, and various changes are possible within a range that does not substantially deviate from the effects of the present disclosure.

[0143] (1) When various operations (moving, updating, deleting, etc.) are performed on the original file 26 or the duplicated file 25, if there are a large number of various files related to the original file 26 or the duplicated file 25, it takes time for the program 22 to process. Therefore, it is preferable that the processing of the program 22 be batch processing rather than real-time processing. In addition, it is preferable that, when the processing of the program 22 starts, a message indicating that the processing of the program 22 is about to start is displayed on the display unit 3.

[0144] (2) In the embodiment, various pieces of serial number information indicate the priority. However, this is not limiting, and the priority may be indicated by the time of updating the original file 26 or the copy file 25. Furthermore, the priority may be set by a user operation.

[0145] (3) Furthermore, when it is predetermined that the original file 26 or the duplicated file 25 is to be deleted, it is efficient to give high priority to the various files to be deleted.

[0146] (4) Furthermore, if the server goes down temporarily, the program 22 refers to files in order of priority and displays the target files to the user.

[0147] (5) In the second embodiment, the server 300 and the multiple information processing devices 200 are communicatively connected via the network 400. However, this is not limiting, and at least one of the multiple information processing devices 200 may perform the same process as the server 300. [Industrial Applicability]

[0148] The file management system, file management method, and file management program according to the present disclosure have industrial applicability. [Explanation of symbols]

[0149] 100 File Management System 1. Control section 11 Processing section 12. Main memory 2 Auxiliary storage 21 Operating Systems 22 File Management Programs 23 Application Programs

Claims

1. a first original file storing substantive information; a storage unit that stores a first link file that stores first link information that designates the first original file, a first original tracking file that stores the first link information and first link tracking information that designates the first link file, and a first link tracking file that stores the first link information; a tracing update unit that updates the first link information stored in the first original tracing file and the first link tracing file when the first original file is operated; a link update unit that updates the first link information stored in the first link file designated by the first link tracking file when the first link information is updated by the tracking update unit; A file management system comprising:

2. When the first link file is newly created as a second link file, The tracking update unit is updating the first original tracking file so that the first linked tracking information stored in the first original tracking file also points to the second linked file; updating the first link tracking file; 2. The file management system according to claim 1, further comprising: a second link tracking file storing said first link information, said second link tracking file being generated in correspondence with said second link file.

3. When the first original file is newly copied as a first copied file, The first original tracking file further stores first copy link information that designates the first copy file; The first link tracking file further stores the first duplicate link information together with a priority of the first duplicate file; The tracking update unit is updating the first original tracking file so that the first duplicate link information stored in the first original tracking file designates the first duplicate file; creating a first copy tracking file corresponding to the first copy file, the first copy tracking file storing the first link information specifying the first copy file instead of the first original file and the first copy link information specifying the first original file instead of the first copy file; The file management system according to claim 1 , further comprising: updating said first link tracking file so that said first duplicate link information stored in said first link tracking file designates said first duplicate file.

4. When a third link file is newly created, the third link file storing the second link information specifying the first duplicate file is created. The tracking update unit is updating the first replication tracking file so that the second link tracking information stored in the first replication tracking file designates the third link file; 4. The file management system according to claim 3, further comprising: a third link tracking file storing second duplicate link information and said first link information, said third link file being corresponding to said third link file.

5. When the first original file is moved, The tracking update unit is updating the first link information stored in the first original tracking file; updating the first link information stored in the first replication tracking file; updating the first link information stored in the first link tracking file; The file management system according to claim 4 , further comprising: updating said first link information stored in said third link tracking file.

6. The file management system of claim 5 , wherein the first original tracking file is moved to the same destination as the first original file.

7. When the first replicated file is updated, The tracking update unit is 5. The file management system of claim 4, further comprising: updating the first duplicate link information stored in the first original tracking file; and updating the first duplicate link information and the second link tracking information stored in the first duplicate tracking file.

8. The tracking update unit is updating the first link tracking file so that the first link information stored in the first link tracking file designates the first original file instead of the first duplicated file; updating the first link tracking file so that the first duplicate link information stored in the first link tracking file designates the first original file instead of the first duplicate file; The file management system according to claim 7 , further comprising: updating said third link tracking file so that said first link information stored in said third link tracking file designates said first replicated file.

9. Display and A display control unit that controls the display unit; Further comprising: The file management system according to claim 7 , wherein the display control unit causes the display unit to display a message indicating that the updated first duplicate file exists.

10. If the first original file is deleted, The tracking update unit is Deleting the first original tracking file; updating the first copy tracking file to exclude the first original file from the first copy link information stored in the first copy tracking file; updating the first link tracking file so that the first link information stored in the first link tracking file designates the first duplicate file; updating the first link tracking file so that the first duplicate link information stored in the first link tracking file designates the first duplicate file; 5. The file management system according to claim 4, further comprising: updating said third link tracking file so as to exclude said first original file from said first link information stored in said third link tracking file.

11. Display and A display control unit that controls the display unit; Further comprising: The file management system according to claim 10 , wherein the display control unit changes a display mode of the first link file or the first duplicate file.

12. a storage step of storing a first original file storing substantial information, a first link file storing first link information designating the first original file, a first original tracking file storing the first link information and first link tracking information designating the first link file, and a first link tracking file storing the first link information; a tracing update step of updating the first link information stored in the first original tracing file and the first link tracing file when the first original file is operated; a link updating step of updating the first link information stored in the first link file designated by the first link tracking information when the first link information is updated by the tracking updating step; A file management method, including:

13. On the computer, a first original file storing substantive information; a storage step of storing, when a first link file storing first link information designating the first original file is created, a first original tracking file storing the first link information and first link tracking information designating the first link file, and a first link tracking file storing the first link information; a tracing update step of updating the first link information stored in the first original tracing file and the first link tracing file when the first original file is operated; a link updating step of updating the first link information stored in the first link file designated by the first link tracking information when the first link information is updated by the tracking updating step; A file management program that runs

Images