JP2015185101A - document file management system and document file management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a file management system capable of checking a difference between a table of content and a document file at two different dates and the content of the table of content and document file differentiated and detected.SOLUTION: A document file management system of the present invention includes: document/table of content identification information for identifying a table of content of the document and a document file; parent table of content identification information which is subordinate document/table of content identification information; a revised version; a version table showing correspondence with a disclosure date and a non-disclosure data of the table of content and the document file; versions of the table of content and document file at two different dates; a version/date retrieval unit for retrieving the table of content and the document file added, changed, and deleted by comparing a disclosure date and a non-disclosure date and totalizing the table of content and the document file of the difference; and a tree structure retrieval unit constituting a tree structure by extracting subordinate relations of the table of content and the document file from the totalization result using the document file/table of content identification information and the parent table of content identification information.

Description

  The present invention relates to a document file management system and a document file management method.

Conventionally, document file management systems for managing document files are generally known. In this document file management system, each table of contents (folder) and document file is managed in a tree structure, and each document file is arranged under a predetermined table of contents, that is, stored in a folder in response to a user instruction. ing.
In this document file management system, it is important to manage the version of the folder and document file for managing the history of the revision of the table of contents and document file at which point.

As a revised document, there is a document file management system in which the revision of a folder and a document file version is recorded as a history, and the document can be managed and browsed (for example, see Patent Document 1).
This document file management system displays the correspondence between version and date as a history document each time it is revised, for each table of contents and document. For example, when a table of contents or a document is revised, the revised date and the version at that time are displayed in association with each other. With this history document, it is possible to check the history of the revised version of the folder and document file.

JP 11-143754 A

  However, when the document management system of Patent Document 1 confirms the difference in the table of contents and the title level of the document file between different versions at each time point of two dates, the user refers to the displayed table and tracks the date. Need to look for version differences between dates. For this reason, since humans visually check and confirm the history documents, it is easy for erroneous reading of the version and date of the history documents.

Further, when it is desired to view the contents of a version of a document file detected as a difference, it is necessary to search for a folder containing this version of the document file and reach the folder.
Therefore, there are problems such as misreading of the folder (table of contents) and document file names during search, input errors, etc., making the process complicated and difficult to check.

  The present invention has been made in view of such circumstances, and the difference between the table of contents and the document file between the different versions at each time point of the two dates, and the contents of the table of contents and the document file detected by the difference. An object of the present invention is to provide a document file management system and a document file management method capable of easily checking the document.

  The present invention has been made in order to solve the above-described problems. The document file management system of the present invention includes at least a document / table of contents identification information for identifying a table of contents and a document file in a document, and a table of contents of a subordinate destination. The parent table of contents identification information, which is the document / table of contents identification information, the revision version, the date of release of the table of contents and the document file, and the date of release of the table of contents and the document file that are deleted and made unpublished A version table storage unit in which a version table indicating the correspondence between the table of contents is stored in advance and the two different specified dates are added by comparing the version, release date, and non-release date of each table of contents and document file. The changed and deleted table of contents and document files are defined as differences between the two different dates from the table of contents version table. A version / date search unit that extracts and summarizes, and extracts a dependency relationship between the table of contents and the document file from the result of the aggregation, and configures a tree structure of each of the table of contents and the document file detected as a difference, And a tree structure search unit for displaying on the display screen.

  According to the document file management method of the present invention, the version / date search unit includes at least a document / table of contents identification information for identifying each of the table of contents and the document file in the document and the document / table of contents identification information of the subordinate table of contents. Specify from the version table that shows the correspondence between the table of contents identification information, the revision version, the release date when the table of contents and document file were released, and the release date when the table of contents and document file were deleted and made private. In each of the two different dates, the table of contents and the document file are added, changed and deleted by comparing the version, publication date and non-publication date of the table of contents and the document file, and the difference between the two different dates is extracted. The version / date search process for summing up and the tree structure search unit, from the result of the summation, each of the table of contents and document file Extract the genus relationship, constitute each of the tree structure of said detected table of contents and document files as the difference, characterized in that it comprises a tree structure search process of displaying on the display screen.

  According to the present invention, revision history using a version table in which a version, a revision date (publication date), and a deletion date (non-publication date) are associated with a table of contents and a document file in a document. Therefore, based on the difference between the table of contents and the document file at the time of two different dates, a tree structure composed of the table of contents of the difference and the document file is displayed. Therefore, according to the present invention, it is possible to easily visually check the difference between the table of contents or the document file at the time of two different dates (including the contents of the document file) from the table of contents of the difference and the tree structure of the document file. Yes.

It is a conceptual diagram which shows the structural example of the file management system by one Embodiment of this invention. 3 is a diagram illustrating a configuration example of a version table stored in a version table storage unit 18. FIG. 4 is a diagram illustrating a configuration example of an extraction table stored in a version table storage unit 18. FIG. It is a figure which shows the tree structure of the table of contents and document file in a document comprised based on the extraction table memorize | stored in the version table memory | storage part. It is a flowchart which shows the operation example of the file management system by this embodiment.

  Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a conceptual diagram showing a configuration example of a file management system according to an embodiment of the present invention. In FIG. 1, a file management system 1 includes an input unit 10, a creation unit 11, an update unit 12, a version / date search unit 13, a tree structure search unit 14, a file read unit 15, an image processing unit 16, a display unit 17, A version table storage unit 18 and a file database 19 are provided.

  FIG. 2 is a diagram illustrating a configuration example of the version table stored in the version table storage unit 18. The version table includes each type of table of contents and document file, document / table of contents identification information (document / table of contents ID (Identification)), revised version, document / table of contents title, and parent table of contents identification information (parent table of contents ID). , At least items of display order, release date, non-release date, and file address.

Here, the type is information for distinguishing whether the object indicated by the document / table of contents title is a table of contents (folder) or a document file. For example, when the type is “1”, this indicates that the document / table of contents title is a table of contents. On the other hand, when the type is “2”, it indicates that the document / contents title is a document file.
The document / table of contents identification information is identification information for identifying the document / table of contents title of each table of contents and document file in the document.
The revised version indicates the version of the table of contents and document file for each document / table of contents identification information.
The document / table of contents title indicates the table of contents and the name of the document file in the document. In the present embodiment, it is assumed that the table of contents or document file is arranged in a hierarchy below the table of contents in the tree structure.

The parent table of contents identification information is identification information indicating the document / table of contents identification information of the table of contents to which each of the table of contents (folder) and the document file belongs.
The display order is a number indicating the display order in the same hierarchy in the tree structure.
The publication date is the date when the created or updated document is published on the browsing website.
The non-public date is the date when the table of contents and document file deleted from the tree structure are made private on the browsing WEB site. Here, the deletion is a deletion from the tree structure after the date of the release. That is, even if it is deleted from the tree structure, the entity is not deleted but is stored as a history in the version table of the version table storage unit 18 or in the file database 19 without being deleted.
The file address indicates an address where the document file in the document is written and stored in the file database.

Returning to FIG. 1, the input unit 10 checks the first date and the second date that the user inputs from a keyboard (not shown) in order to check the difference between the table of contents in the document such as a manual and the version of the document file. Output to the version / date search unit 13. Here, the first date is a specific date. The second date is a date when a predetermined period has elapsed from the first date. For example, if “2014/01/01” is the first date, the second date is “2014/02/01” after “2014/01/01”.
In addition, when the input unit 10 creates a new table of contents and document file, or updates each existing folder and document file, the user inputs character data and the like.

When the user creates a new table of contents (folder) or document file, the creation unit 11 registers each new folder or document file in the version table stored in the version table storage unit 18.
When the user updates an existing table of contents or document file, the update unit 12 records new version records (table rows) of the updated table of contents or document file against the version table stored in the version table storage unit 18. Data column). For example, in FIG. 2, when the version of the document / contents title “Chapter 1 General Introduction” is changed from “1” to “2”, the update unit 12 changes the version of the document / contents title “1. 2 ”is added to the version table stored in the version table storage unit 18.

  The version / date search unit 13 includes a table of contents and a history of document files stored in the version table storage unit 18 at each time point of the first date and the second date designated for the difference comparison. Search the table of contents (folder) and document file with the newest version and the latest release date. In addition, the version / date search unit 13 applies the second date to the table of contents and document file on the first date in each table of contents and document file of the searched first date and second date. The table of contents and document file added, changed, and deleted from the table of contents and document file are extracted. Also, the version / date search unit 13 creates an extraction table in which the extracted added, changed, and deleted contents and document files are tabulated.

The tree structure search unit 14 creates a tree structure of the document based on the correspondence relationship between the table of contents identification information and the parent table of contents identification information from the extracted extraction table. Then, the tree structure search unit 14 displays the extracted tree structure on the display screen of the display unit 17 via the image processing unit 16.
When a file is selected in the displayed difference table of contents and tree structure of the document file, the file reading unit 15 reads the data of the selected document file from the file database in which the file data of the document is managed. . Here, the deleted document file can also be read because the entity is stored in the file database 19. When reading this document file, the file reading unit 15 reads the file address corresponding to the table of contents / document title of the selected version from the version table stored in the version table storage unit 18. Then, the file reading unit 15 reads data of the selected document file from the file database 19 based on the read file address. The file reading unit 15 displays the read document file data on the display screen of the display unit 17 via the image processing unit 16.

The image processing unit 16 displays data output from each unit on the display screen of the display unit 17.
A version table is written and stored in the version table storage unit 18 in advance.
The file database 19 stores document files of documents that have been added, updated, and deleted (not disclosed).

  FIG. 3 is a diagram illustrating a configuration example of the extraction table stored in the version table storage unit 18. The extraction table of FIG. 3 has the same configuration as the version table of FIG. 2, but an item column is newly provided instead of the address column. That is, the extraction table includes columns for type, document / table of contents identification information, revised version, document / table of contents title, parent table of contents identification information, display order, release date, non-public date, and item. In the item column, “addition”, “change”, and “deletion” representing the contents of processing for the table of contents and the document file are stored.

  Here, the addition is added to the table of contents and the document file that are not present in the latest version as of the first date but newly exist in the latest version as of the second date. The change is added to the table of contents and the document file in which the latest version as of the second date is updated (new version) with respect to the latest version as of the first date. The deletion exists in the latest version as of the first date, and is added to the table of contents and document file that are not in the latest version as of the second date. In the following description, a case where the first date is “2014/01/01” and the second date is “2014/02/01” will be described as an example.

  In FIG. 3, the document / table of contents title “Chapter 1 General” is not at the time of the first date “2014/01/01”, but the second date “2014/02/01” is the release date. Since the version is “1”, “addition” is added to the item. The document / table of contents title “1. General” has been changed from “Chapter 1 General” to “1. General” on the second date “2014/02/01”. "Change" is added. Further, the document / table of contents title “2. Supplementary” is made public at the time of the first date “2014/01/01” and is not made public on the second date “2014/02/01”. , “Delete” is added to the item.

  FIG. 4 is a diagram showing a table of contents and a tree structure of a document file configured based on the extraction table stored in the version table storage unit 18. FIG. 4 shows the difference between the table of contents and the document file version between the first date and the second date. For example, since the document / table of contents title “Chapter 1 General” is the table of contents added on the second date as described above, “addition” is given to the item, and in the vicinity of the right side of this item. The second date “2014/02/01” indicating the added date is described. In addition, since the document / table of contents title “1. General” is a document file whose name has been changed from “Chapter 1 General” on the second date, “Change” is given to the item. In the vicinity of the side, the second date “2014/02/01” indicating the changed date is described as the changed date. The document / table of contents title “2. Supplementary” is a document file that existed in the document on the first date but has been deleted on the second date. The second date “2014/02/01” is described as the deleted date near the right side of this item.

  Returning to FIG. 1, when the user creates a new table of contents or document file, the creation unit 11 registers each new table of contents or document file in the version table stored in the version table storage unit 18. That is, the creation unit 11 writes and stores the newly created table of contents or title name of the document file in the version table together with the newly added document / table of contents identification information. Also, the creation unit 11 uses the type of table of contents or document file, the subordinate document / table of contents title document / table of contents identification information as the parent table of contents identification information, display order, date added, release date, non-public date, document file If there is, the file address in the file database 19 is written and stored in the version table stored in the version table storage unit 18.

  When an existing table of contents or document file is updated by the user, the update unit 12 changes the version of the updated table of contents or document file with respect to the version table stored in the version table storage unit 18. That is, the update unit 12 writes and stores the table of contents or the title name of the document file updated to the document / table of contents title together with the document / table of contents identification information given at the time of updating in the version table. Further, the update unit 12 uses the type of table of contents or document file, the document / table of contents identification information of the subordinate document / table of contents title, the parent table of contents identification information, the display order, the date of change as the release date, the non-public date, and the document file. If there is, the file address in the file database 19 is written and stored in the version table stored in the version table storage unit 18.

  In addition, when the table of contents or document file that has already been deleted (unpublished) from the tree structure of the document by the user, the update unit 12 deletes the table of contents or document that has been deleted from the version table stored in the version table storage unit 18. Make changes to each version of the file. That is, the update unit 12 writes and stores the table of contents or the title name of the document file updated to the document / table of contents title together with the document / table of contents identification information given at the time of updating in the version table. The update unit 12 also determines the type of the table of contents or the document file, the document / table of contents identification information of the subordinate document / character title, the parent table of contents identification information, the display order, the release date, the non-public date as the date of deletion, the document file If so, the file address in the file database 19 is written and stored in the version table stored in the version table storage unit 18.

Next, a paper information confirmation process performed by the file management system according to the embodiment of the present invention will be described with reference to FIG. FIG. 5 is a flowchart showing an operation example of the file management system according to the present embodiment.
Step S1:
The input unit 10 determines whether each data of the first date and the second date is input by the user. At this time, if the data of each of the first date and the second date is input by the user, the input unit 10 advances the process to step S2. On the other hand, when the data of each of the first date and the second date is not input by the user, the input unit 10 executes Step S1 again after a predetermined time has elapsed.

Step S2:
The input unit 10 outputs the input first date and second date data to the version / date search unit 13.
The version / date search unit 13 then supplies the date indicated by the first date and the second date supplied from the input unit 10, for example, “2014/01/01” as the first date and “2014/01/01” as the second date. 2014/02/01 "is input.

As a result, the version / date search unit 13 stores the document / table of contents identification information of the table of contents and document file that are not present in the version of the first date and exists in the version of the second date, in the version table storage unit 18. Extract from the version table. At this time, the version / date search unit 13 sequentially selects the table of contents whose release date is the second date and the document / table of contents identification information of the document file one by one in order. Then, the version / date search unit 13 extracts the table of contents of the first date, the table of contents of the first date, the table of contents that does not exist in the document file, and the document / table of contents identification information of the document file. The process of extracting the added table of contents and document file is performed for each type, that is, for each type of table of contents and document file.
For example, in the version table of FIG. 2, the table of contents “Chapter 1 General Introduction” (document / table of contents identification information “3”) existing at the time of the first date “2014/02/01” is the second date “2014”. Does not exist at the time of “/ 01/01”. Therefore, it is determined that the table of contents “Chapter 1 General” is added at the time of the first date “2014/02/01”.

Step S3:
Then, the version / date search unit 13 is not released before the first date “2014/01/01”, and the table of contents and document file released until the second date “2014/02/01”. It is determined whether or not the document / table of contents identification information has been extracted. At this time, the version / date search unit 13 is not released before the first date “2014/01/01”, and the table of contents and document file released until the second date “2014/02/01”. If is extracted, the process proceeds to step S4. On the other hand, the version / date search unit 13 does not publish the table of contents and document file before the first date “2014/01/01”, and the table of contents and document files published until the second date “2014/02/01”. If none is extracted, the process proceeds to step S5.

Step S4:
Next, the version / date search unit 13 sequentially reads the extracted table of contents and document file from the upgrade table in the version table storage unit 18. The version / date search unit 13 copies the read table of contents and document file to the extraction table in the version table storage unit 18. Further, since the version / date search unit 13 extracts the added table of contents and document file, “add” is added to the item, and the extracted table in the version table storage unit 18 corresponds to the document / table of contents identification information. To write and memorize.

Step S5:
Next, the version / date search unit 13 is released by the first date “2014/01/01” and is not disclosed (deleted) by the second date “2014/02/01”. The table of contents and the document file are extracted from the version table of the version table storage unit 18. At this time, for example, the version / date search unit 13 extracts the table of contents and document file whose non-public date is the second date “2014/02/01”. Then, the version / date search unit 13 searches for a table of contents and a document file whose release date of the extracted table of contents and document file is before the first date “2014/01/01”. As a result, the version / date search unit 13 releases the table of contents and document file that were released before the first date “2014/01/01” and were not released before the second date “2014/02/01”. To extract.

Step S6:
The version / date search unit 13 is released on the first date “2014/01/01” and is not disclosed (deleted) on the second date “2014/02/01”. Whether or not a document file has been extracted is determined.
At this time, the version / date search unit 13 has been released before the first date “2014/01/01” and has not been released until the second date “2014/02/01”. If the document file is extracted, the process proceeds to step S7. On the other hand, the version / date search unit 13 is open until the first date “2014/01/01” and is not disclosed until the second date “2014/02/01”. If no document file is extracted, the process proceeds to step S8.

Step S7:
Next, the version / date search unit 13 sequentially reads the extracted table of contents and document file from the upgrade table in the version table storage unit 18. The version / date search unit 13 copies the read table of contents and document file to the extraction table in the version table storage unit 18. Since the version / date search unit 13 extracts the deleted table of contents and document file, “delete” is added to the item, and the extracted table in the version table storage unit 18 corresponds to the document / table of contents identification information. To write and memorize.

Step S8:
Next, the version / date search unit 13 is different in the version released by the first date “2014/01/01” and the version released by the second date “2014/02/01”. The table of contents and the document file are extracted from the version table of the version table storage unit 18. At this time, for example, the version / date search unit 13 extracts the table of contents whose publication date is the second date “2014/02/01” and the document / table of contents identification information of the document file. The version / date search unit 13 then extracts a table of contents and a version with different versions from the table of contents and the document file published before the first date “2014/01/01” with respect to the extracted table of contents and version of the document file. Search document / table of contents identification information of document file. As a result, the version / date search unit 13 extracts a table of contents and a document file having different versions on the first date “2014/01/01” and the second date “2014/02/01”.

Step S9:
Then, the version / date search unit 13 determines whether or not a table of contents and a document file having different versions are extracted between the first date “2014/01/01” and the second date “2014/02/01”. I do.
At this time, the version / date search unit 13 performs processing when a table of contents and a document file having different versions are extracted between the first date “2014/01/01” and the second date “2014/02/01”. To step S10. On the other hand, the version / date search unit 13 performs processing when no table of contents and document files having different versions are extracted on the first date “2014/01/01” and the second date “2014/02/01”. To step S11.

Step S10:
Next, the version / date search unit 13 sequentially reads the extracted table of contents and document file from the upgrade table in the version table storage unit 18. The version / date search unit 13 then copies and writes the read table of contents and document file to the extraction table in the version table storage unit 18. Since the version / date search unit 13 extracts the deleted table of contents and document file, “delete” is added to the item, and the extracted table in the version table storage unit 18 corresponds to the document / table of contents identification information. To write and memorize.

Step S11:
Then, the tree structure search unit 14 refers to the extraction table of the version table storage unit 18 and generates a document file and a table of contents tree structure from the respective document files and table of contents dependency.
For example, when the document / table of contents identification information is not detected in the extraction table and the type is “1” in the extraction table, the tree structure search unit 14 detects the document / content matching the parent table of contents identification information from the version table. Search the table of contents identification information. The tree structure search unit 14 reads out the document / table of contents title “Chapter 1 general remarks” having the type “1” and the document / table of contents identification information “3” from the extraction table.
Then, the tree structure search unit 14 searches the version table for a table of contents having document / table of contents identification information that matches the parent table of contents identification information of the document / table of contents title “Chapter 1 General Introduction”.

Next, the tree structure searching unit 14 detects a document / table of contents title “first rule general rule” having a document / table of contents identification information that matches the parent table of contents identification information of “Chapter 1 General”.
Then, the tree structure search unit 14 searches the version table for the document / table of contents identification information that matches the parent table of contents identification information of the document / table of contents title “1st general rule”. The tree structure search unit 14 detects the document / table of contents title “TOP” as the document / table of contents identification information that matches the parent table of contents identification information of the document / table of contents title “Part 1 General Rules”.

Similarly, the tree structure search unit 14 searches the version table for a document / table of contents identification information that matches the parent table of contents identification information of the document / table of contents title “TOP”. Here, the tree structure search unit 14 cannot detect a document / table of contents title that has a document / table of contents identification information that matches the parent table of contents identification information of the document / table of contents title “TOP”. As a result, the tree structure search unit 14 detects that the document / table of contents title “TOP” is the apex of the tree structure.
As a result, as shown in the tree structure of FIG. 4, the tree structure search unit 14 arranges the document / table of contents title “first general rule” directly below the document / table of contents title “TOP”.
Then, the tree structure search unit 14 arranges the document / table of contents title “Chapter 1 General” in the hierarchy immediately below the document / table of contents title “Part 1 General Rules”.

Next, the tree structure search unit 14 is a document file with a type “2” and a document / table of contents title “1. Read "General" from the extraction table.
Then, the tree structure search unit 14 searches the extraction table for a table of contents having a document / table of contents identification information that matches the parent table of contents identification information of the document / table of contents title “1. General”. The tree structure search unit 14 detects a document / table of contents title “Chapter 1 General” as a document / table of contents title having a document / table of contents identification information that matches the parent table of contents identification information of the document / table of contents title “1. . The tree structure search unit 14 arranges the document / table of contents title “1. General” in the hierarchy immediately below the document / contents title “Chapter 1 General”. Here, the tree structure search unit 14 does not perform another search because the document / table of contents title having the table of contents identification information matching the parent table of contents identification information of “Chapter 1 General Introduction” has already ended.

As described above, the tree structure search unit 14 obtains the subordinate relationship from the extraction table stored in the version table storage unit 18 from the parent table of contents identification information and the document / table of contents identification information, and the table of contents and document file in the document. Create a tree structure.
At this time, when there is a table of contents and a document file that have been added, deleted, and changed, the tree structure search unit 14 determines whether the table of contents and the document file are arranged in the tree structure. A tree structure including the table of contents up to the table of contents of the vertex is generated. Then, the tree structure search unit 14 outputs the generated table of contents and the tree structure of the document file to the image processing unit 16.

Step S12:
The image processing unit 16 is supplied with the table of contents and the document file from the tree structure search unit 14, and shows a tree structure showing the table of contents between the first date and the second date in the document and the difference in the document file, as shown in FIG. In this way, it is displayed on the display screen of the display unit 17.
At this time, the image processing unit 16 uses the type of the table of contents and the document file in the tree structure and the document / table of contents identification information to indicate the type of difference between the table of contents and the document file from the extraction table of the version table storage unit 18. , And the date corresponding to each item is read. Here, as the date corresponding to the item, each of additions and changes is a release date, and deletion is a non-public date.

Then, the image processing unit 16 adds, deletes, or changes the difference between the table of contents and the document file in the vicinity of the table of contents and the document file added, deleted, and changed in the tree structure. Displays information on the date of deletion and modification.
For example, in the case of the document / table of contents title “Chapter 1 General”, the image processing unit 16 uses the document / table of contents identification information of the document / table of contents title “Chapter 1 General” to add the item “addition” and release date “2014 / "02/01" is read from the extraction table of the version table storage unit 18. Then, as shown in FIG. 4, the image processing unit 16 displays the characters “add (2014/02/01)” in the vicinity area where the characters of the document / table of contents title “Chapter 1 General” are displayed. To do.

Similarly, in the case of the document / table of contents title “1. General”, the image processing unit 16 sets the item “change” and the publication date “2014/02/01” to the document / table of contents “1. General”. Read from the extraction table of the version table storage unit 18 according to the identification information. Then, as shown in FIG. 4, the image processing unit 16 displays the characters “change (2014/02/01)” in the vicinity area where the characters of the document / contents title “1. General” are displayed. .
Further, in the case of the document / table of contents title “2. supplement”, the image processing unit 16 sets the item “deletion” and the non-public date “2014/02/01” to the document / table of contents title “2. supplement”. Read from the extraction table of the version table storage unit 18 according to the identification information. Then, as shown in FIG. 4, the image processing unit 16 displays the character “delete (2014/02/01)” in the area near the character / document title “2. supplement”. .

That is, according to the present embodiment, the tree structure of the table of contents (holder) and the document file detected as the difference between the versions of the first date and the second date after the first date is as if it were a normal subordinate. Since it is displayed as a tree structure showing the relationship, that is, only the differences of the versions are narrowed down and displayed, it is possible to easily visually identify the added, changed and deleted contents and document files.
For example, according to the present embodiment, the current date as the second date and the first date, for example, in the investigation on the business management state at the time of the designated date and the extraction of the required report document from the supervisory authority. Since the difference between the table of contents and the document file with respect to the specified date (past) is displayed, it is possible to easily extract the part that has been revised or improved, and to perform efficient document management and operation.

In addition, according to the present embodiment, the history of addition, change, and deletion of each table of contents and document file in a document is accumulated in the version table, so that the history of documents after creation can be easily managed, and past versions The knowledge content can be passed on to the document contents, and a management system for managing document revisions can be established.
In addition, according to the present embodiment, the addition, change, and deletion history of each table of contents and document file in the document is accumulated in the version table, and a difference between documents of two different dates corresponding to versions can be easily detected. Therefore, it is not necessary to individually manage documents in versions for each date, and it is not necessary to compare the presence / absence of differences between different files, so that document management costs can be suppressed.

  In addition, the program for realizing the function of the file management system 1 in FIG. 1 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into the computer system and executed. You may perform the extraction process of the difference of each version of a document file or two dates with different contents. Here, the “computer system” includes an OS and hardware such as peripheral devices.

Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used.
The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Furthermore, the “computer-readable recording medium” dynamically holds a program for a short time like a communication line when transmitting a program via a network such as the Internet or a communication line such as a telephone line. In this case, a volatile memory in a computer system serving as a server or a client in that case, and a program that holds a program for a certain period of time are also included. The program may be a program for realizing a part of the functions described above, and may be a program capable of realizing the functions described above in combination with a program already recorded in a computer system.

  The embodiment of the present invention has been described in detail with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes design and the like within a scope not departing from the gist of the present invention.

DESCRIPTION OF SYMBOLS 1 ... File management system 10 ... Input part 11 ... Creation part 12 ... Update part 13 ... Version date search part 14 ... Tree structure search part 15 ... File reading part 16 ... Image processing part 17 ... Display part 18 ... Version table storage part 19 ... file database

Claims (2)

At least the document / table of contents identification information for identifying the table of contents and document file in the document, the parent table of contents identification information that is the document / table of contents identification information of the subordinate destination table of contents, the revision version, and each of the table of contents and document file A version table storage unit in which a version table indicating a correspondence between a release date when the document is published and a non-public date in which each of the table of contents and the document file is deleted is written and stored;
The table of contents and the document file added, changed, and deleted by comparing the version, release date and non-public date of the table of contents and the document file at each of the two different designated dates are stored in the table of contents table 2 A version / date search part that extracts and aggregates the differences between two different dates,
The dependency of each table of contents and document file is extracted from the result of the aggregation using the document / table of contents identification information and the parent table of contents identification information, and each tree structure of the table of contents and document file detected as a difference is configured. A document file management system comprising: a tree structure search unit for displaying on a display screen. The version / date search unit includes at least a document / table of contents identification information for identifying a table of contents and a document file in the document, a parent table of contents identification information which is the document / table of contents identification information of the subordinate table of contents, and a revision version From the version table showing the correspondence between the release date when the table of contents and document file were released and the release date when the table of contents and document file were deleted and made private, at each of two specified different dates Version / date search process for extracting the table of contents and document files added, changed and deleted by comparing the version, release date and non-public date of the table of contents and document file, and summing them as the difference between the two different dates When,
The tree structure search unit extracts the dependency of the table of contents and the document file from the result of the aggregation using the document / table of contents identification information and the parent table of contents identification information, and each of the table of contents and the document file detected as the difference A document file management method comprising: a tree structure search process for forming a tree structure and displaying the tree structure on a display screen.

Images