JP2005316715A - Document management system, method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a document management system, method and program, capable of performing version management even to a file not version-managed by a collection source file system. <P>SOLUTION: A range of a file to be version-managed is designated by a designation part 111. An updated file or a newly added file is detected by monitoring the designated range 101 by a monitoring part 112, is acquired by an acquisition part 113, and is managed as a different version to an existing file. When it is decided that the updated file is a file similar to the existing version-managed file, it is managed as a version upgraded file in the existing file. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a document management system, method, and program, and more particularly, to a document management system, method, and program capable of performing version management on a file that is not version-managed by a collection source file system.

  In general, when files are managed by multiple systems, if a file managed on one side is updated, it is automatically updated to the system managing the other file, and the existing file is overwritten and updated. Will be deleted, the file with the contents before the update will be deleted.

  For this reason, it is impossible to check the state of the file before the update is performed, and it is impossible to cancel the update and return it to the original state, so that the file management function cannot be satisfied.

  As a conventional technique for automatically and efficiently collecting the latest document information when collecting documents on the network, there is one disclosed in Patent Document 1.

In the prior art disclosed in Patent Document 1, documents can be collected by predicting the next update time of a document on the network, and the latest document can always be collected efficiently and automatically. it can. Furthermore, since documents with a high average data transmission rate can be preferentially acquired, efficient document collection is possible by not collecting some documents with a low average data transmission rate.
JP 09-31802

  However, in the prior art disclosed in Patent Document 1, even if the latest updated document information can be collected automatically and efficiently, it is not possible to acquire a document in a state before updating. There's a problem.

  SUMMARY An advantage of some aspects of the invention is that it provides a document management system, method, and program that can perform version management on a file that is not version-managed by a collection source file system.

  In order to achieve the above object, the invention of claim 1 copies the collection target file of the first file system, registers the copied collection target file in the second file system, and stores the registered collection target file. In the document management system managed by the second file system, the update of the collection target file is detected by the file update monitoring means for monitoring the collection target file of the first file system and the file update monitoring means. In such a case, the updated file is copied and registered in the second file system, and the file related to the registration is managed as a file having a version different from that of the collection source file that has already been registered. Means.

  The invention according to claim 2 is the invention according to claim 1, wherein the version management means detects that a new file is generated based on the collection target file by the file update monitoring means. The newly generated file is copied and registered in the second file system, and the file related to the registration is managed as the same file as the collection target file that has already been registered but with a different version. It is characterized by that.

  In the invention of claim 3, in the invention of claim 2, the version management means compares the file name of the newly generated file with the file name of the collection target file that has already been registered. When the two are similar, the newly generated file is managed as the same file as the collection target file of the generation source but as a different version of the file.

  According to a fourth aspect of the present invention, in the second aspect of the invention, the version management unit compares the file name of the newly generated file with the file name of the collection target file that is already registered. If the files are similar and the newly generated file is in the same hierarchy as the collection source file of the generation source, the newly generated file is the same as the collection target file of the generation source. These files are managed as different version files.

  According to a fifth aspect of the present invention, the collection target file of the first file system is copied, the copied collection target file is registered in the second file system, and the registered collection target file is stored in the second file. In a document management system for managing documents managed by a system, when the collection target file of the first file system is monitored by a file update monitoring unit, and the update of the collection target file is detected by the file update monitoring unit The updated file is copied and registered in the second file system, and the file related to the registration is managed as a file having a version different from that of the collection source file that has already been registered. To do.

  The invention according to claim 6 copies the collection target file of the first file system, registers the copied collection target file in the second file system, and sets the registered collection target file as the second file. A document management program for causing a computer to execute document management managed by the system, the step of monitoring the collection target file of the first file system, and an update of the collection target file detected by the monitoring Copying the updated file and registering it in the second file system, and managing the file related to the registration as a file having a version different from that of the file to be collected that has already been registered. It is characterized by that.

  According to the present invention, the collection target file of the first file system is monitored by the file update monitoring means, and when the update of the collection target file is detected by the file update monitoring means, the updated file is copied. The file is registered in the second file system, and the file related to the registration is managed as a file having a different version from the file to be collected that has already been registered. The effect is that version management can be automatically performed even for files that are not yet installed.

  Hereinafter, an embodiment of a document management system, method and program according to the present invention will be described in detail with reference to the accompanying drawings.

  FIG. 1 is a system configuration diagram of a document management system configured by applying a document management system, method and program according to the present invention.

  In FIG. 1, the document management system includes a collection source file management apparatus 100 and a storage destination file management apparatus 110.

  The collection source file management apparatus 100 is configured to include at least a storage area for a document to be managed, and has a designated range 101 for a document to be managed in the storage area.

  The collection source file management apparatus 100 is a management apparatus that is not subjected to version management.

  The designated range 101 is a range designated by the storage destination file management apparatus 110.

  The file managed in the specified range 101 is migrated or copied to the version-managed storage file management apparatus 110.

  The storage destination file management apparatus 110 includes a designation unit 111, a monitoring unit 112, an acquisition unit 113, a determination unit 114, a determination unit 115, a management unit 116, and a storage unit 117.

  The designation unit 111 designates a collection range of target files to be managed.

  In the example shown in the figure, the designated range designated by the designation unit 111 is shown. Files managed in the designated range 101 can be transferred to the storage destination file management apparatus 110 or copied.

  The monitoring unit 112 monitors whether a file within the specified range 101 of the collection source file management apparatus 100 has been updated or created. The file monitoring is a constant monitoring or monitoring at a fixed time, and detects that a file within the specified range 101 has been updated or a new file has been created.

  For example, the monitoring unit 112 registers a file name and a file status within the specified range 101, compares the file status with respect to the file name and the file status within the specified range 101, and detects different files. . Here, the file status indicates file attributes such as update date and time and creator name.

  The acquisition unit 113 updates or newly updates a file that is updated or newly added among files in the specified range 101 monitored by the monitoring unit 112 so that the storage destination file management apparatus 110 performs version management of the file. Get the added file.

  The determination unit 114 determines whether or not version management of the file acquired by the acquisition unit 113 is performed. That is, instead of performing version management for all the files in the designated range 101, it is possible to designate a file that is not subject to version management based on preset setting information.

  For example, files that are not subjected to version management are listed and stored as files, and when the determination unit 113 determines, only the files that are not listed in the list list with reference to the listed files are versioned. Try to manage.

  The determination unit 115 determines that the updated file or the newly added file among the files in the specified range 101 is a version-up file in the same file when the file is similar to the file already stored and managed by the storage unit 117. To do.

  Here, as a method [1] of identifying similar files, the file name of the version management target file of the collection source file management apparatus 100 and the file name of the version managed by the storage destination file management apparatus 110 are compared, and the collection source file Similar to the case where the prefix of the file managed by the management apparatus 100 is the same as the file managed by the storage destination file management apparatus 110 and exists in the same hierarchy as the file managed by the storage destination file management apparatus 110 Judge as a file.

  For example, the name of the file subject to version management in the collection source file management apparatus 100 is “test01.txt”, the file name that is version-managed by the storage destination file management apparatus 110 is “test.txt”, and is stored. If the file is in the same hierarchy as the file managed by the destination file management apparatus 110, it is determined as a similar file, and "test01.txt" is version-managed as an upgrade file of "test.txt".

  Furthermore, as a method of identifying similar files [2], it can be identified by comparing specific attribute information of files.

  For example, “file ID + version number” is held as one of the attribute information of the file, and even when the name of the file is correct by referring to the “file ID + version number” when performing version management discrimination Version control can be performed.

  The version management unit 115 manages a plurality of the same files by adding version information to the files determined to be version managed by the determination unit 113 among the version management target files acquired by the acquisition unit 112 It is.

  Further, when the determination unit 114 determines that the version management target file is a similar file in the existing file, the version management target file is version-managed as an upgrade file of the existing file.

  That is, a plurality of versions can be managed for one file, and even if the file names are different, it can be automatically managed as an upgraded file of an existing file.

  The storage unit 116 stores a file with version information.

  According to such a configuration, version management can be automatically performed even for a file whose version is not managed by the collection source file management apparatus 100.

  That is, it becomes possible to automatically perform version management of a file that has been renamed and saved for the purpose of maintaining the file state before update in the collection source file management apparatus 100.

  FIG. 2 is a diagram showing a management image of the document management system according to the present invention.

  FIG. 2 shows a file status 200 that is not version-managed by the collection source file management apparatus and a version-managed file status 210.

  The file management state 200 prior to version management is stored as a plurality of files in a state in which the name has been changed due to reasons such as having an update history for the same file (201, 202, 203). .

  A file management state 210 in which version management is performed indicates a state 204 managed as one file from the state (201, 202, 203) stored as a plurality of files.

  As a result, the user who operates the file can edit the file without worrying about the update history of the file.

  FIG. 3 is a diagram showing a screen for designating a file for which version management is not performed in the present invention.

  In FIG. 3, a file that is not subjected to version management can be designated in a system that performs version management. This makes it possible to perform version management of only the necessary files in a timely manner, rather than easily managing all the files, thereby improving the manageability and functionality of the files.

  Next, version management of this system will be described.

  FIG. 4 is a flowchart showing the flow of version management according to the present invention.

  As shown in FIG. 4, the processing is started by monitoring an arbitrary position on the system that is not version-controlled, the monitored file or folder is updated (step 401), and the monitoring function is monitored Is detected (step 402). In order to perform version management for the file or folder whose update is detected, the updated file or folder is acquired (step 403).

  It is determined whether or not version management is performed on the acquired file or folder (step 404). If the file or folder is version management (YES in step 404), version information is assigned to the management target file. Then, version management is performed (step 405). When version management is not performed (NO in step 404), file management is performed by overwriting an existing file in the same manner as normal file management (step 406).

  Through the above processing, the version management system of the present invention can appropriately perform version management.

  This makes it possible to automatically and smoothly transfer and copy files from a file system that is not version-controlled, and to automatically manage versions of files that have remained in history. It becomes possible.

  The processing shown in the follow chart can also be realized by a file management program that can be executed by a computer.

  In the first embodiment, a file is managed by performing version management for a file in a system that is not subjected to version management. The embodiment shown in FIG. 5 shows an example in which the version management system is used as a backup system in file management of an existing system as a usage application.

  FIG. 5 can be broadly divided into an existing system part and a version management system part of the present invention.

  As a result of processing in the existing system, if the file (document) is stored in a file system that does not support version management, the edited file (document) is not updated in the existing system, so every time the edited file (document) is updated. Is overwritten, and the previous file state cannot be retained.

  Therefore, by using the version management system of this system as a backup of the file server, the management performance of the file (document) can be improved and the redundancy can be secured without changing the existing system.

  With the above processing, the version management system of the present invention can be easily combined with each other without changing the existing system, and further helps to improve the management performance of the existing file system.

  Therefore, by applying the present invention, it becomes possible to perform file management with the addition of a version management function. Furthermore, the file system that has not been version-controlled can be renamed, assigned attribute information, or a directory. If the file history is managed by changing the file name, it can be expected that the version can be automatically managed.

  The processing shown in the flowchart can also be realized by a version management program that can be executed by a computer.

  The present invention is not limited to the embodiments described above and shown in the drawings, and can be implemented with appropriate modifications within a range not changing the gist thereof.

  For example, in the first embodiment or the second embodiment, as a method of storing the version-controlled file, the file before the upgrade and the file after the upgrade are stored respectively. Alternatively, only the difference between the file before the version upgrade and the subsequent file may be stored as a separate file, and the difference between the version changes may be managed based on the associated information.

  Specifically, as shown in FIG. 6, when the version upgraded to “test.txt” (601) of ver1.0 is “test.txt” (602) of ver1.1, Only the difference between ver1.0 and ver1.1 is cut out in the difference file “diff.txt” (604), and the version change (605) for the cut out difference is recorded.

  Further, when the version is upgraded to ver1.2, the difference from ver1.1 is cut out in the difference file “diff.txt” (604), and the version change (606) for the cut-out difference is recorded. To.

  FIG. 7 is a diagram showing a method in the case where file management is managed by a difference file in the present invention.

  In FIG. 7, the difference when version 1.0 “test.txt” (601) is upgraded to version 1.1 “test.txt” (602) is extracted into a difference file “diff.txt” (604). The detailed information of the extracted difference is managed as a difference management table 701.

  For example, the difference contents described in the row (record) (1) of the difference file “diff.txt” (604, 604-A) can be obtained by referring to the difference management table 701 in the first row of the [change location] column. Since the one described as (1) can be found, it can be determined that the difference is when the version is changed from ver1.0 to ver1.1.

  By managing in this way, it is only necessary to manage differences even when the number of files for version management increases, and it is possible to minimize the compression of the disk capacity.

  Furthermore, in the above embodiment, by storing a name change rule in a process that can automatically import a file that has been left in the history by changing the name or the like in a system that is not version-controlled, It may be configured so that version management can be performed between files having completely different names.

  The present invention is applicable to a document management system, method, and program for migrating files from a collection source file management device to a storage destination file management device, and in particular, a version automatically in a file for which an update history has been manually created. It becomes possible to manage, and similar files can be managed as upgraded files of existing version-controlled files, which is useful for improving file management performance.

The figure which shows the system configuration | structure of the document management system concerning this invention. The figure which shows the version management image of the document management system concerning this invention. The figure which shows the screen which designates the file which does not perform version management in this invention. The flowchart which shows the flow of the version management concerning this invention. The network figure which shows the other Example of the document management system concerning this invention. The figure which shows the storage management method of the version management object file in this invention. The figure which shows the method in the case of managing the management of the file in this invention by a difference file.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Collection source file management apparatus 101 Specification range 110 Storage destination file management apparatus 111 Specification part 112 Monitoring part 113 Acquisition part 114 Judgment part 115 Judgment part 116 Management part 117 Storage part

Claims (6)

In a document management system for copying a collection target file in a first file system, registering the copied collection target file in a second file system, and managing the registered collection target file in the second file system;
File update monitoring means for monitoring the collection target file of the first file system;
When the update of the collection target file is detected by the file update monitoring means, the updated file is copied and registered in the second file system, and the file related to the registration is already registered. A document management system comprising: version management means for managing a file of a different version from a collection target file of an update source. The version management means includes
When it is detected by the file update monitoring means that a new file is generated based on the collection target file, the newly generated file is copied and registered in the second file system, and 2. The document management system according to claim 1, wherein a file related to registration is managed as a file of the same version as a collection source file that has already been registered but with a different version. The version management means includes
If the file name of the newly created file is compared with the file name of the collection target file that has already been registered, and the two are similar, the newly created file is collected by the creator. The document management system according to claim 2, wherein the document management system manages the same file as the target file as a different version of the file. The version management means includes
The file name of the newly generated file is compared with the file name of the collection source file already registered, and both are similar, and the newly generated file is collected by the generation source. 3. The document management according to claim 2, wherein when the file is in the same hierarchy as the target file, the newly generated file is managed as a different version of the same file as the collection target file of the generation source. system. Document management for document management for copying a collection target file in the first file system, registering the copied collection target file in the second file system, and managing the registered collection target file in the second file system In the system,
Monitoring the collection target file of the first file system by file update monitoring means;
When the update of the collection target file is detected by the file update monitoring means, the updated file is copied and registered in the second file system, and the file related to the registration is already registered. A document management method characterized in that it is managed as a file of a version different from the file to be collected at the update source. Document management for copying the collection target file in the first file system, registering the copied collection target file in the second file system, and managing the registered collection target file in the second file system by a computer A document management program to be executed,
Monitoring the collection target file of the first file system;
When an update of the collection target file is detected by the monitoring, the updated file is copied and registered in the second file system, and the file related to the registration is already registered in the update source. A document management program comprising: a management target file and a step of managing the file as a different version file.

Images