JPH05181723A - File managing device - Google Patents

Abstract

PURPOSE:To prevent the generation of mismatching for the management of the number of files by referring to a file management rule in each software and managing the number of files to be formed/deleted. CONSTITUTION:This file managing device for managing the number of files having the same name at the time of forming/deleting files is constituted of a file management rule storing means 3 for storing a file management rule differently determined in each started software and a file managing means 4 for managing the number of files to be formed/deleted while referring to the file management rule determined in each software. The means 4 adds or deletes the number of files while referring to the file management rule based upon both application softwares stored in the means 3. Since different file management rules for plural application softwares are stored, a file having the same required file name can be accessed even when a different application software is driven.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file management device for managing the version number when creating / deleting files having the same name by different software such as application software.

[0002]

2. Description of the Related Art Files created / deleted by a user are managed by an operating system so that they can be easily handled by a computer system. And the created file is given a file name,
It is registered in a directory in the operating system. If the user specifies only the name when using the file, the operating system refers to the directory and finds it from the storage medium storing the specified file. In application software that handles files, such as word processing software or editor software, it is often the case that some version number management is performed for a plurality of files having the same name. However, if the operating system that builds the application software does not have a file management mechanism, there are many cases in which version number management is realized by providing a special file naming rule for each application software.

FIG. 6 is a block diagram of the same-name file storage device that manages files of the same name. In FIG.
The same-name file storage device includes a file name input device 61 for inputting a file name to be stored, a file storage device 62 in which a file to be stored and its file name are stored in a pair, and a file name input device 61. If the file name is the same in the file name comparison device 63 that compares the file name input from the file name stored in the file storage device 62 with the file name comparison device 63, the file name comparison device 63 From the file name input device 61 and outputs an instruction signal from the file name input device 61 to add an identification name to the file name input device 61. The file storage device as described above is described in, for example, Japanese Patent Laid-Open No. 2-64830. With such a configuration, if the input file name is the same as the file name already stored in the file storage device 62, the file name comparison device 63 outputs an instruction signal to output the file name. After the file name input from the input device 61, for example, a version number is added as a suffix. When saving the same file as above,
It is possible to prevent the old file from being destroyed by overwriting the file simply by giving an identification name such as the version number to the file as a suffix.

[0004]

However, the rules for naming file names in the same file tend to be unique to each application software. For example, in the application software A, a file that does not have an identifier for version number management may be the latest version, whereas in the application software B, a file that has a final number in the identifier may be the latest version. Then, for example, when sharing the files named by the two application software A and B, the file names named by one of the application software are input even though the application software is running on the same operating system. However, there is a problem that a desired file cannot be viewed while running other application software due to inconsistency in version number management.

The present invention is for solving the above problems. Even if a file named by a plurality of software (for example, application software) having different file version management is shared, the file version An object of the present invention is to provide a file management device that does not cause inconsistency in management.

[0006]

In order to achieve the above object, a file management apparatus of the present invention manages version numbers of a plurality of files having the same name when creating / deleting files, and is activated. Storage means (3 in FIG. 1) for storing different file management rules determined for each software
And a management unit (4 in FIG. 1) that manages the version number of the created / deleted file by referring to the file management rule for each software.

[0007]

[Operation] For example, when a file having the same name is shared by a plurality of application software, a file management rule determined for each application software, for example, a version number management rule is stored in the storage means. The storage means stores a file management rule determined by the application software A and a file management rule determined by the application software B, for example. Then, the file created by the application software A or the application software B is given a version number or deleted by the file management means with reference to the file management rule based on both the application software in the storage means. Since different file management rules of a plurality of application software are stored as described above, it is possible to access files having the same desired file name even when different application software are running.

[0008]

EXAMPLE FIG. 1 is a diagram for explaining an example of a file management apparatus according to the present invention. In FIG.
The file management device creates / creates a file entity on a secondary storage device such as a hard disk or a floppy disk.
File creating / deleting means 1 to be deleted, and file name storing means 2 for storing the correspondence between the file entity and the file name as a file management table on the secondary storage device,
When a file is created or deleted by the file management rule storage means 3 for storing a file management rule different for each application software, for example, a rule for naming a file version number, and the file creation / deletion means 1, the above file management rule. The file name storage means 2 is referred to by referring to the file management rule stored in the storage means 3.
And a file entity on the secondary storage device corresponding to the file management table created by the file management means 4, for example, 5, 6,
7 and 7.

Here, in order to manage the file version number,
An example will be described for two application softwares A and B that use different naming conventions. For example, the naming convention of the version number in the application software A is as follows. (A) To manage the version number, an extension in the form of version number is added to the end of the file name. (B) When there are a plurality of versions, the version number of the oldest version is “−1−”. Hereinafter, as the version number becomes newer, the number part is incremented by "1". (C) The latest version does not have an extension for managing the version number.

Further, for example, the naming convention of the version number in the application software B is as follows. (A) To manage the version number, an extension consisting of the symbol "%" and the version number is added to the end of the file name. (B) When multiple versions exist, the version number of the oldest version is
Add "1" after "%". Hereinafter, as the version number becomes newer, the version number increases the number after “%” by “1”. (C) The latest version has an extension in which the number after "%" is the largest version number.

FIG. 2 is a diagram for explaining the file entity and the file management rule of each application software. For example, referring to FIG. 2, "foo.txt"
A case in which three versions exist for a file with the file name Operating system A
2, the oldest version (first version) of the file entity is “foo.txt” according to the version number naming convention.
-1- ", the second version is" foo.txt-2- ", and the latest version (third version) is" foo.txt "without an extension. Similarly, in the application software B, as shown in FIG. 2, the earliest version (first version) of the file entity is “foo.txt% 1” and the second version according to the version number naming rule.
The version is "foo.txt% 2", and the latest version (third version) is "foo.txt% 3" with an extension.

The file management means 4 creates the file management table 2 in accordance with the file management rules unique to the respective application software A and B as described above. That is, as shown in the file management table in the file name storage means 2 in FIG. 1, for example, for one file entity, the same file name and the file management rules of the respective application software A and B are used. Assign a street extension. That is, in the file management table shown in FIG. 1, the file entity “foo.
Two extensions are assigned to "txt".
For example, in the file entity 5, "foo.txt-1
Two different names, "-" and "foo.txt% 1" are given. In the same manner, the file management table shown in FIG. 1 is created by the file management means 4.

A description will be given of a case where a new version of the file name "foo.txt", that is, the fourth version is created by the file creating / deleting means 1 in the file management device having the above-mentioned configuration. When the file creation / deletion means 1 creates the fourth version of the file name “foo.txt”, that is, the file entity 8, the file management means 4 is activated by the request of the file creation / deletion means 1. The file management means 4 refers to the file management rules of the application software A and B stored in the file management table and the file management rule storage means 3, and determines the following items according to the respective version number naming rules. 1. According to the version number naming convention of the application software A, the name of the file entity 8 is “foo.txt”. 2. According to the version number naming convention of the application software B, the name of the file entity 8 is “foo.txt%
4 ”. 3. The name of the file entity 7 is changed from “foo.txt” to “foo.txt-3-” according to the version number naming convention of the application software A.

FIG. 3 is a diagram showing the relationship between the file management table and the file entity after the fourth edition is created. FIG. 4 is a diagram for explaining the version management rule for the entity file of each application software. The file management means 4 changes the contents of the file management table in the file name storage means 2 shown in FIG. 1 based on the determined items, and the file management table shown in FIG. 3 and each file entity on the secondary storage device are changed. Correspond to. As described above, since the correspondence between the file entity, for example, 5 to 8 and the file management table by the file management means 4 can be known, the file "f"
oo. Even after creating a new version of "txt", in each file entity, a file holding the correct version number can be seen from either application software A or B.

FIG. 5 is a flow chart showing the contents of processing when a new file entity is created by the file creation / deletion means. The file management of this embodiment will be described in more detail with reference to FIG. In step 51, create a file /
The deleting means 1 creates or deletes a file entity. In step 52, it is checked whether or not there is an unprocessed file management rule in the file management rule storage means 3. After processing the file management rules for all the application software, if no unprocessed file management rules remain in the file management rule storage means 3,
The process ends. If there is a file management rule that has not been processed, the process proceeds to the next step 53. In step 53, if an unprocessed file management rule remains in the file management rule storage means 3 in step 52, one unprocessed file management rule is retrieved from the file management rule storage means 3. In step 54, in step 5
3 determines the name of the file entity created according to the file management rule retrieved from the file management rule storage means 3. For example, "foo.txt" is named. In step 55, the file name to be changed accompanying the name of the file entity is determined by the file management rule. For example, application software A
Assuming that the file of the fourth edition is created in, the file name is determined to be “foo.txt”. Further, in order that the same file name can be accessed by the application software B, “foo.txt% 4” is determined by adding “% 4” after “foo.txt”. In step 56, the contents of the file management table are changed according to the items decided in step 55. That is, the contents are changed from the file management table of FIG. 3 to the file management table of FIG. Then, the process returns to step 52, and the same processing is repeated for the number of application software.

In the above embodiment, the case where there are two application softwares has been described. However, even if the number of application softwares increases, a similar file management table is created so that any application software can be operated. You can see files with the same name.

[0017]

As described above, according to the present invention, there is no contradiction in version number management among a plurality of softwares having different management rules for file version number management.
You can share files with the same name.

[Brief description of drawings]

FIG. 1 is a diagram for explaining an embodiment of a file management device according to the present invention.

FIG. 2 is a diagram for explaining a file entity and file management rules of each application software.

FIG. 3 is a diagram showing a relationship between a file management table and a file entity after creating a fourth edition.

FIG. 4 is a diagram for explaining a version number management rule for an entity file of each application software.

FIG. 5 is a flowchart showing the contents of processing when a new file entity is created by the file creation / deletion means.

FIG. 6 is a block configuration diagram of a same-name file storage device that manages files with the same name.

[Explanation of symbols]

1 ... File creation / deletion means 4 ... File management means 2 ... File name storage means 5 to 8 ...
..File 3 ... File management rule storage means

Claims (1)

[Claims] 1. A file management device for managing version numbers of a plurality of files having the same name when creating / deleting files, and a storage means for storing different file management rules determined for each software to be started. A file management device comprising: management means for managing a version number of a file to be created / deleted by referring to a file management rule for each software.