JP2000259615A - Method for managing version of composite document and computer readable recording medium storing composite document version management program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make it possible to execute operation for grasping the edition history of a composite document itself or returning the state of the composite document to a just preceding state when the constitution of the composite document is changed or the version of document components is updated in a composite document management system. SOLUTION: Document components constituting a composite document are specified, a constitutional information table storing constitutional information indicting the constitution of document component groups of a composite document is prepared by a constitutional information table registering program 106 and stored in a secondary storage device 109a. When the addition of a new version of document components corresponding to the constitutional information registered in the constitutional information table, the addition of a new document component or the deletion of a certain document component is generated, the constitutional information is updated by a composite document version updating program 107, the updated constitutional information is registered in the constitutional information table in addition to the unupdated constitutional information and the constitutional information table is read out from the device 109a and displayed by a composite document version history display program 108.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document management system using a computer device. Related to version control methods.

[0002]

2. Description of the Related Art In recent years, with the increase in creation, reuse, and distribution of digitized documents on a computer, a document management system for creating, editing, storing, and managing a large number of digitized documents in a company or the like has been developed. Needs are increasing. Such a document management system can store the history of document changes,
It is necessary to restore past documents and the like, and a version management function is indispensable. Here, the version management function refers to the content data of each version, the version number, the date and time of creation, etc., so that when a user edits or saves a document or program source, it can extract it back to an arbitrary version. It is a function to manage information. As a result, it is possible to restore a document of a version at an arbitrary point in the past, and to grasp an editing process by displaying a list of version information. Documents directly related to the core business of the company, legal documents, etc. accurately record who changed what and when,
Since it is necessary to store them, a version management function is indispensable in a document management system that manages them. For example, as an example of a method of managing the version of a document file, there is an invention disclosed in Japanese Patent Application Laid-Open No. 9-62657 (hereinafter, this is referred to as Known Example 1). In the well-known example 1, each version is managed for each document file to be edited, and it is possible to restore a document at an arbitrary point in the past.

Here, writing of a large-scale document and development of a program are often performed by a plurality of people working together, and at this time, the document is divided into several document parts and created and edited. In such a case, the document is not a single document file, but SGML (Standard Generalized Markup L).
anguage), HTML (HyperText Markup Language), XML (eXt
ensibleMarkup Language) or OLE (Object Linking
Multiple files are created as a compound document that is linked by links using, for example, and Embedding). As described above, a document management system that manages a document created as a compound document requires not only a function of managing the version of each file but also a function of managing the version of the entire compound document.

[0004] As an example of a method of managing the version of a compound document, there is an invention described in Japanese Patent Application Laid-Open No. H11-143752 (hereinafter referred to as Known Example 2). In the second prior art, a document part is registered in a “configuration management folder” that manages a version update mode indicating the name, version, and registration state of the document part constituting the compound document. There are two types of document part version update modes, “automatic update” and “fixed”. When a document part registered in the automatic update mode is edited and upgraded, the document part referenced from the configuration management folder is updated. The version is also updated automatically, so that you can always refer to the latest version. On the other hand, when the version of a document component registered in the confirmation mode is upgraded, the configuration management folder still refers to a certain fixed version and is not affected by the version upgrade. Referencing from the configuration management folder only refers to the document part of the version before the update. When each document part is written by a different person in charge, each author can switch the version update mode at any time, so it is possible to control which version of the document in charge is referred from the configuration management folder. It becomes possible.

FIG. 18 shows a specific example. As of June 1, version 1 of the "Table of Contents" (hereinafter referred to as V1) and "1st
V2 of "Chapter", V2 of "Figure 1", and V2 of "Chapter 2" are registered. Chapter is in automatic update mode. Here, the document part “Chapter 2” was edited on June 3,
When the version is upgraded from V2 (1802) to V3 (1803), “XX Product Manual” 1801 becomes “Contents”
V1, "Chapter 1" V2, "Figure 1" V2, "Chapter 2" V3
Is updated to the state. On the other hand, "Chapter 1" referenced in the confirmation mode was edited and upgraded (V3)
However, the configuration management folder 1801 still refers to V2 of “Chapter 1”, and the status is not updated. As described above, according to the version management method of the publicly known example 2, it is possible to perform the management in which the version management of each document part and the configuration management of the compound document are linked.

[0006]

However, the conventional compound document version management method has the following problems. First, in the version control system of the well-known example 1,
Although it is possible to manage the version of each document part, it is not possible to manage the version as a compound document which is an aggregate of those document parts. For example, even if an attempt is made to restore the state of a composite document at a certain point in the past, it is not possible to restore the composite document because it is not known what kind of document component group was composed at that time.

When the version of a compound document is managed by the method of the second known example, the document structure of the compound document can be managed by registering each document component in the structure management folder. However, when the document parts are registered in the automatic update mode, when the configuration management folder is updated with the upgrade of the document parts, the configuration management folder in the state before the update is not saved. , That is, a change history as a compound document cannot be recorded. For example, as shown in FIG. 18, the configuration management folder 1801 is changed from the state on June 1 to
If the configuration management folder 1801 is updated to the state on June 3 with the version upgrade of “Chapter 2”, it is no longer possible to return the configuration management folder 1801 to the state on June 1. Therefore, there is a problem that the so-called Undo operation of returning the state of June 3 from the state of June 3 to the state immediately before (the state of June 1) cannot be performed. Here, for example, if all document parts are registered in the fixed mode and the version of the configuration management folder is manually increased every time each document part is upgraded, all the document parts associated with the version upgrade can be obtained. The history of the configuration management folder can be recorded. However, in this method, it is practically difficult to record all the histories, since there is a possibility that the user may forget to upgrade the version.

An object of the present invention is to solve the problems of the prior art as described above. In other words, when the state of a compound document itself changes due to a version upgrade of a document component constituting the compound document or a change in the document structure of the compound document, the history of the state change of the compound document is recorded and saved. It is an object of the present invention to provide a version control method for a composite document, which enables the user to grasp the editing history of the composite document itself and perform an operation of returning the state of the composite document to a version at an arbitrary point in time.

[0009]

In order to solve the above-mentioned problems, the present invention provides a function of registering a compound document composed of a plurality of document parts, a function of updating the contents of the registered compound document, A compound document version management method in a document management system having a function of managing a change history of a compound document and each document component constituting the compound document. As a process of registering the compound document, There is a step of generating configuration information including the component information of the document component, and storing the configuration information in association with the compound document.

[0010] The method further includes a step of analyzing the contents of the compound document to be registered and extracting component information of document components of the compound document.

In addition, as a process of updating the content of the compound document, when a document component is added or deleted from the compound document, the configuration information of the compound document corresponding to the state after the addition or deletion of the document component is added. Generating and registering the configuration information as a new version of the compound document.

[0012] The method may further include a step of displaying each of the registered versions as a version history of the compound document.

[0013] The method may further include a step of determining whether a document part is added or deleted from the compound document by analyzing the description content of a main document part of the compound document.

Further, as a process for updating the content of the compound document, when any one of the document parts constituting the compound document is edited and the version is updated, the state corresponding to the updated version of the document part is handled. The method further includes the step of generating configuration information of document parts of a compound document and registering the configuration information as a new version of the compound document.

[0015] The method may further include the step of displaying the registered version as a version history of the compound document.

Further, as processing for managing the version history of the compound document, the date and time of creation of the configuration information corresponding to each version of the compound document and the date and time of creation of each version of each document part held by the configuration information are compared. Detecting a document part whose version has been updated between adjacent versions in the configuration information, and generating temporary configuration information corresponding to the version update of the document part; forming a version history of the compound document; A temporary version history is created by combining the configuration information group to be combined with the temporary configuration information group corresponding to the version update of the document part in accordance with the time series of the event that caused the generation of the configuration information. And a step of displaying the temporary version history.

As a process for updating the content of the compound document, when a new version of a document component is created,
Setting an edition number indicating a version as a compound document in the document part of the version, determining which edition of the compound document the document part of the version becomes the document part of the compound document, and storing the version history of the compound document. As a managing process, when all the document parts held in the configuration information corresponding to each version of the compound document have the specified edition number, the configuration information is generated as the configuration information of the specified edition, If the configuration information corresponding to each version of the document includes a document part having an edition number larger than the specified edition number, the document part is replaced with the specified edition number of the document part. Generate the configuration information of the specified edition by replacing the latest version in the version, If the configuration information corresponding to each version of the compound document includes a document part having an edition number smaller than the specified edition number, the document part is replaced with the specified edition number of the document part. Generating the configuration information of the specified edition by replacing the oldest version in the version of the compound document, and displaying the generated configuration information as a version history for each edition of the compound document. .

In addition, as a process of registering the compound document, for each document component constituting the compound document, whether or not the version upgrade of the document component is reflected in the version upgrade of the compound document is indicated. Setting a version reflection element or a fixed version element as a version reflection type, and editing a document component in which the version reflection type is set to a version reflection element as a process of updating the content of the compound document; And when the version is updated, generating configuration information of the document part corresponding to the updated state of the document part, and registering the generated configuration information as a new version of the compound document. ing.

Further, the method further comprises the step of displaying the registered version as a version history of the compound document.

In the process of registering the compound document, for a document component expressing the schema information of the compound document, the version reflection type of the document component is set as a fixed version element and registered. .

The names of the components to be managed are as follows:
In the version update mode description configuration information table that records the name of the file storing the component, the version number of the component, and the version update mode that indicates whether the version (version) of the component is automatically updated or not Registering or updating the component name and the file name storing the same, setting or changing the version update mode of each component described in the version update mode description configuration information table, The version number of each component described in the table is set, and the component name, the file name, the version number, and the version update mode description configuration information indicating the version update mode described in the version update mode description configuration information table are stored in the table. Storing the version update mode description configuration information from the version update mode description configuration information table; Obtaining a document corresponding to the version number represented by the obtained version update mode description configuration information from the secondary storage device, displaying the document obtained in the document obtaining step, and obtaining the document in the document obtaining step After editing the document, refer to the version information table that records the version number, creator, creation date and time of each version, save the edited document as a new version in the secondary storage device, and store the new version in the version information table. Version information is stored, and the version update mode of the component corresponding to the edited document described in the version update mode description configuration information table is determined. If the version update mode is “determined mode”, the version If the version number is not updated, and if the automatic update mode is set, the version number is updated. A document configuration change information recording step of recording, as document configuration change information, information on a change in the version update mode and information on a document configuration change performed in the configuration management step; Based on the change information and the version information of each document part, a compound document version history is combined and displayed, and a compound document version history managing step is provided.

Also, the present invention is a computer-readable recording medium that records a version control program for a compound document. The version control program for the compound document generates configuration information of document parts of the compound document to be registered, and stores the configuration information. A document component configuration information registering step of associating with the compound document and registering as an original version of the compound document; a component information extracting step of analyzing content of the compound document to be registered and extracting component information; When the addition or deletion of a document part occurs, the configuration information of the document part of the compound document corresponding to the state after the addition or deletion of the document part is generated, and the structure information is registered as a new version of the compound document. Having a compound document version update step of displaying each version as a version history of the compound document To have.

Also, the present invention is a computer-readable recording medium storing a version control program for a compound document. The version control program for the compound document generates configuration information of document parts of the compound document to be registered, and stores the configuration information. A document component configuration information registering step of associating with the compound document and registering as an original version of the compound document; a component information extracting step of analyzing content of the compound document to be registered and extracting component information; When the addition or deletion of a document part occurs, the first part generates configuration information of the document part of the compound document corresponding to the state after the addition or deletion of the document part, and registers the structure information as a new version of the compound document. A new version registration step and one of the document parts constituting the compound document are edited and the version is updated A second new version registration step of generating configuration information of the document part of the compound document corresponding to the updated state of the document part and registering the structure information as a new version of the compound document; And a compound document version display step of displaying each version of the configuration information thus obtained as a version history of the compound document.

Also, the present invention is a computer-readable recording medium on which a version control program for a compound document is recorded. The version control program for the compound document generates configuration information of document parts of the compound document to be registered, and stores the configuration information. A document component configuration information registering step of associating with the compound document and registering as an original version of the compound document; a component information extracting step of analyzing content of the compound document to be registered and extracting component information; When the addition or deletion of a document part occurs, the first part generates configuration information of the document part of the compound document corresponding to the state after the addition or deletion of the document part, and registers the structure information as a new version of the compound document. A new version registration step and one of the document parts constituting the compound document are edited and the version is updated A second new version registration step of generating configuration information of the document part of the compound document corresponding to the updated state of the document part and registering the structure information as a new version of the compound document; The original version and the first new version of the registered configuration information are separately set as a first version history of the compound document, and the second new version of the registered configuration information is set as a second version history of the compound document. The document document version updating step is displayed.

[0025]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a first embodiment of the present invention will be described with reference to the drawings. This embodiment registers a configuration information table for managing the configuration of a compound document, and creates a new configuration information table when a document part is updated or a document part is added to or deleted from the configuration information table. Is registered and managed as a new version of the compound document. In each embodiment of the present invention, various types of information such as configuration information are in the form of table information. .

First, the configuration of the present embodiment is shown in FIG.
As shown in FIG. 1, the first embodiment includes a terminal device 101 and a CPU
102, a medium 103 such as a floppy disk for distributing documents, a BUS 104, a secondary storage device 109
a, 109b, 109c, and a primary storage device storing a processing program 105 for managing versions of document parts and compound documents.
Is composed of a configuration information table registration program 106, a compound document version update program 107, and a compound document version history display program 108. Also,
The secondary storage device 109a stores a configuration information table for managing the configuration of a compound document, the secondary storage device 109b stores a version information table of each document component, and the secondary storage device 109c stores each version of the document component. ing.

Next, the procedure of the configuration information table registration processing in this embodiment will be described. FIG. 2 is a flowchart illustrating a procedure of a registration process by the configuration information table registration program 106 according to the present embodiment. 5 in FIG.
A case where a compound document such as No. 1 is registered will be described as an example. First, in step 201, a main document component constituting a compound document is designated. For example, when registering a compound document such as 501 in FIG. 5, “main body.sgm” is designated as the main document component. Next, in step 202, the description content of the main document part of the compound document specified in step 201 is analyzed, and a document part group forming the compound document is extracted. In the example of 501 in FIG. 5, the document structure in which “body.sgm” refers to “chapter 1.sgm” and “chapter 1.sgm” refers to “FIG. 1.bmp” is analyzed, and “ `` Body.sgm '', `` Chapter 1.sgm '', `` Figure 1.b
mp ”is extracted. In step 203,
Designating the document parts group extracted in step 202,
A configuration information table is created and registered in the secondary storage device 109a. For example, a configuration information table 701 shown in FIG. 7 including the document part groups “body.sgm”, “chapter 1.sgm”, and “FIG. 1.bmp” extracted in step 202 is created.
Register in the secondary storage device 109a. Here, the configuration information table manages the configuration of one version of a compound document, and includes the file name of each document component,
Manage IDs and versions. Configuration information table 7 in FIG.
In the example of 01, this version of "XX Product Manual" is V1 of "body.sgm", V1 of "chapter 1.sgm", "Figure 1.bmp"
V1. In step 204, the user specifies from the terminal device 101 whether or not to end the registration of the configuration information table. When registering a new configuration information table, the process returns to step 201.

Next, the registration procedure in FIG. 2 will be described in more detail. The case where an SGML document called “XX product manual” as shown in FIG. 19 is registered will be described as an example. The SGML document in FIG. 19 is “manual.dtd”
According to the document structure defined by the DTD (Document Type Definition), "body.sgm" refers to "chapter 1.sgm",
"Chapter 1.sgm" refers to "Figure 1.bmp". First, in step 201, a document specified as a main document component constituting a compound document is read. For example,
When an SGML document as shown in FIG. 19 is registered, “main body.sgm” specified by the user is read as a main document component. Next, in step 202, the description content of the main document part of the compound document specified in step 201 is analyzed, and a document part group forming the compound document is extracted. In the case of an SGML document as shown in FIG. 19, the description content of the main document component can be analyzed by using the SGML parser. Representative SG
There is "SGMLS" as an ML parser. First, the internal DTD 1901 of “body.sgm” is analyzed.
DOCTYPE declaration (1902), and extracts that the external DTD is “manual.dtd”. Next, referring to the entity declaration (1903), “chapter 1.sgm” and “FIG. 1.bmp” are extracted as document parts referred to by “body.sgm”.

As another method, an entity declaration
After referring to (1903), the document instance (190
There is also a method in which the presence or absence of entity reference is determined with reference to 4), and only the actually referenced entity is extracted as a document part. In this case, since the entity reference 1905 refers to “chapter 1.sgm” and the entity reference 1906 refers to “FIG. 1.bmp”, “body.sgm”
The document parts referenced by "m" are "chapter 1.sgm" and "Fig.
Is extracted. As described above, “manual.dtd”, “chapter 1.sgm”, and “FIG. 1.bmp” are extracted as a document part group constituting an SGML document having “main body.sgm” as a main document part.

Next, in step 203, step 202
A configuration information table is created on the basis of the document component group extracted in step (1), and registered in the secondary storage device 109a. Further, the document part group is registered in the secondary storage device 109c. In the example shown in FIG. 19, for example, the document part groups “manual.dtd”, “body.sgm”,
A configuration information table 1907 including “Chapter 1.sgm” and “FIG. 1.bmp” is created, and the configuration information table is registered in the secondary storage device 109a, and the document component group is registered in 109c. Here, the configuration information table manages the configuration of one version of a compound document, and manages the file name, document ID, and version of each document component. In the example of the configuration information table 1907, the version with “XX product manual” is V1 of “manual.dtd” and “body.sgm”
V1 of "Chapter 1.sgm" and V1 of "Figure 1.bmp". In step 204, the user specifies from the terminal device 101 whether or not to end the registration of the configuration information table. When registering a new configuration information table, the process returns to step 201. According to the above procedure, the document component group and the configuration information table that constitute the compound document can be registered. Furthermore, a configuration information table is created by designating all the document components instead of specifying the main document components and analyzing the contents to extract the document components to create the configuration information table as described above. There is also a method that can be used.

Next, the procedure of a compound document version update process in this embodiment will be described. FIG. 3 is a flowchart illustrating a procedure of a process of updating the version of a compound document by the compound document version update program 107 according to the present embodiment. The case where the compound document shown in FIG. 5 is edited as shown in FIG. 6 and version control is performed will be described as an example.
FIG. 6 shows the version upgrade of each document part, with the horizontal axis representing the time axis. For example,
Looking at "Chapter 1.sgm", it was V1 on June 11, but it was edited on June 13 and upgraded to V2.
And it was upgraded to V3 on June 18. In “Chapter 2.sgm”, V2 was added as a document part of a compound document on June 17th. Here, the version is upgraded in units of dates, but it is also possible to make units in smaller units of time.

First, in step 301, a user edits a document part. Next, in step 302, step 30
The version information table stored in the secondary storage device 109b that manages the version name, creator, creation date and time, etc. of the document part edited in step 1 is updated. The version information table manages information such as a creator and a creation date and time for each version. For example, when "Chapter 1.sgm" is edited in step 301, "Chapter 1.sgm" is upgraded, and in step 302, the version information table is updated. As shown in FIG. 8, when the “chapter 1.sgm” is upgraded from V1 to V2, version information 802 relating to V2 is newly added to the version information table 801. In step 303, the change of the document structure of the compound document and the change of the document parts are notified. Upon receiving the notification in step 303, a new configuration information table is created in step 304 and stored in the secondary storage device 109a. For example, when the version information table of “Chapter 1.sgm” is updated, it is notified, and as shown in FIG. A new configuration information table 702, which has been updated to V2, is stored. Then, in step 305,
The terminal device 1 determines whether or not the user has finished editing the document part.
Specify from 01. If the editing of the document part is continuously specified, the process returns to step 301. Step 30
In (3), a change in the document structure of the compound document can be detected by analyzing the description contents of the main document parts constituting the compound document.

When each document part is edited as shown in FIG. 6, a configuration information table such as 901 in FIG. 9 is created with the upgrade of the document part and the addition and deletion of the document part. Note that, in FIG. 901, a configuration information table such as 902 is omitted to show only the version of each document part.

Next, the procedure of the compound document version history display processing in this embodiment will be described. FIG. 4 shows a compound document version history display program 1 in this embodiment.
10 is a flowchart showing a procedure of a compound document version history display process of the compound document 08. First step 4
At 01, a configuration information table representing the version history of the compound document is obtained from the secondary storage device 109a. In step 402, the version history of the compound document composed of the configuration information table acquired in step 401 is displayed. In step 403, the terminal device 10 determines whether or not the user has finished displaying the version history of the compound document.
Specify from 1. Step 4 if you want to continue
Return to 01. For example, a change history of the configuration information table is displayed as indicated by 901 in FIG. By the above steps,
Version control of a compound document can be performed.

That is, when the state of the entire composite document changes due to a version upgrade of the document parts constituting the composite document or a change in the configuration of the composite document,
It is considered that the version of the compound document has been increased. Each version of the compound document corresponds to a configuration information table for managing which document component is composed of which version. In other words, as indicated by reference numeral 901 in FIG. 9, a new configuration information table is created in response to a version upgrade of a document part and a change in the configuration of a compound document, so that the editing history of the entire compound document can be grasped, It is possible to return to the previous editing state in units.

Next, an example of a user operation will be described with reference to the drawings. FIG. 28 is an example of a screen showing a list of registered compound documents, in which “OO Product Manual” and “ΔSpecification” are currently registered. When the user clicks “XX Product Manual” with the mouse as in 2801, the current document configuration (2802) of “XX Product Manual” is displayed on the right screen. The latest version of the "XX Product Manual" must be composed of V2 of "Main unit.sgm", V3 of "Chapter 1.sgm", V2 of "Figure 1.bmp", and V3 of "Chapter 2.sgm" I understand.

When "XX Product Manual" is selected as shown in FIG. 29 and "Display History" is executed as shown in 2901, a list of version history of "XX Product Manual" (2902) is displayed. You. The screen of 2902 shows “○
In this example, the date and time of creation of each version of the “Product Manual” and comments are displayed.

As shown in FIG. 30, the version history list (2
902), when a certain version (3001) is selected and double-clicked, the document structure of that version can be referred to as in 3002. FIG. 30 is an example in which V3 of “XX Product Manual” is selected (3001) and the configuration is referred to. As shown in the screen 3002, V3 of “XX Product Manual” is “body.sgm” V
It can be seen that it is composed of V2 of "Chapter 1.sgm" and V2 of "Fig. 1.bmp".

Furthermore, as shown in FIG. 31, when a certain document part (3101) is selected from the document structure display screen (3002) and double-clicked, a version list of the document part is referenced as shown in 3102. be able to.
FIG. 31 selects the document part of “Chapter 1.sgm” (3101)
This is an example in which a version list is displayed (3102).
Like the screen example of 3102, the creator of each version, the creation date and time, and the like are displayed as version information. The above is the description of the first embodiment of the present invention.

Hereinafter, a second embodiment of the present invention will be described with reference to the drawings. In the present embodiment, a new version of a compound document is created only when the document structure of the compound document is changed, and for other versions of the compound document that change with the This is an example in the case of combining based on the version information of. The first embodiment is a compound document version update program 107, a compound document version history display program 10.
8 is different, and the other processes are the same. In the present embodiment, as in the first embodiment, the terminal device 101, the CPU 10
2. Medium 103 such as a floppy disk for distributing documents, BUS 104, secondary storage device 109a,
09b, 109c, and a primary storage device storing a processing program 105 for managing the versions of document parts and compound documents. It comprises a compound document version history display program 108. As in the first embodiment, a configuration information table for managing the configuration of the compound document is stored in the secondary storage device 109a.
9b stores a version information table of each document part, and the secondary storage device 109c stores each version of the document part.

Next, the procedure of a compound document version update process in this embodiment will be described. FIG. 10 is a flowchart illustrating a procedure of a compound document version update process by the compound document version update program 107 according to the present embodiment. The case where the compound document shown in FIG. 5 is edited and version control is performed will be described as an example. First, in step 301, a user edits a document part. Next, in step 302, the version information table stored in the secondary storage device 109b for managing the version name, creator, creation date and time of the document part edited in step 301 is updated. In step 1001, a change in the document structure is notified. Upon receiving the notification in step 1001, a new configuration information table is created in step 304 and stored in the secondary storage device 109a. For example, when a compound document as shown in FIG. 5 is edited as shown in FIG. 12, the document part “Chapter 2.sgm” was added on June 17 and the structure of the compound document was changed. At the time, V2 of `` body.sgm '', `` Chapter 1.sgm
A configuration information table 1202 composed of V2 of “m”, V2 of “FIG. 1.bmp”, and V2 of “Chapter 2.sgm” is created. In step 305, the user specifies from the terminal device 101 whether or not to end the editing of the document part. If the editing of the document part is continuously specified, the process returns to step 301. Also,
In step 1001, it is also possible to analyze the description contents of the main document parts constituting the compound document and detect a change in the document structure of the compound document.

Next, the procedure of the compound document version history display processing in this embodiment will be described. FIG. 11 is a flowchart showing a procedure of a composite document version history display process by the composite document version history display program 108 in the present embodiment. First, step 401
Then, the configuration information table indicating the version history of the compound document is obtained from the secondary storage device 109a. Step 11
01, the version information such as the creator and the creation date and time of each document part described in the configuration information table is stored in the secondary storage device 1.
09b. In step 1102, step 4
01, and according to the creation date and time of each document component acquired in step 1101, each time the version of the document component is increased, it is considered that the version of the composite document is increased, and the version history information of the temporary composite document is stored. Combine.

For example, in the example of FIG. 12, V1 of “body.sgm”, V1 of “chapter 1.sgm”, and V1 of “FIG. 1.bmp” as of June 11
And a configuration information table 1201 composed of
gm '' V2, `` Chapter 1.sgm '' V2, `` Figure 1.bmp '' V2, `` Chapter 2.
configuration information table 1202 composed of V2 of "sgm"
Has already been saved by the compound document version update program 107. Then, another configuration information table such as 1203 is temporarily combined based on the configuration information and the version information of each document part. For example, when focusing on June 14, the latest configuration information table at that time is 1201, “body.sgm”, “chapter 1.sgm”,
It can be seen that it consists of "Figure 1.bmp". Then, based on the version information of each document part, collecting the latest version as of June 14, each, V1 of "body.sgm", V2 of "chapter 1.sgm", "Fig. .bmp "
Can be created from the configuration information table 1204 composed of V2. Other histories are temporarily synthesized in the same manner. Then, a temporary version history is created that is arranged according to the date and time of the version upgrade of the document component that has caused the creation of each configuration information table.

Next, in step 1103, step 110
The version history information of the compound document synthesized in step 2 is displayed. In the example of FIG. 12, the history 1 created when the document structure is changed by the compound document version management program 107 is described.
201, 1202 and the temporary change history 1203 synthesized in step 1102 are displayed. In step 403, the user specifies from the terminal device 101 whether or not to end the display of the document part. To continue displaying, the process returns to step 401.

As described above, by storing the change information of the composition of the compound document, it is possible to combine and display the version history of the compound document accompanying the upgrade of the document parts and the change of the structure of the compound document. It is possible to grasp the editing history of the entire composite document and to return to the previous state in the unit of the composite document. Further, as compared with the case where a configuration information table is created every time a document component is upgraded as in the first embodiment, there is an effect that the storage capacity can be reduced. Also in the present embodiment, it is possible to display and refer to a version history list of a compound document by the use method as described in the first embodiment. The above is the description of the second embodiment of the present invention.

Hereinafter, a third embodiment of the present invention will be described with reference to the drawings. In the present embodiment, when a document part is upgraded, a user sets an edition number indicating which edition of the compound document is to be used for the version, and furthermore, the compound part composed of the set document part version is set. This is an example of combining and displaying version history information for each edition of a document. Here, the edition number is a number indicating a version of the entire compound document. For example, suppose that a compound document like 501 in FIG. 5 is co-authored by a plurality of people, and that a person in charge of each document part edited it as 1501 in FIG. The author in charge of the editing of the document parts for the "XX Product Manual" and "for the first edition" will continue to work on the document parts for the "XX Product Manual" and "for the second edition." Suppose you want to upgrade. At this time, if each version of the document part can be set to which edition part of the compound document, such as “for the first edition” or “for the second edition,” Writing can proceed at the pace of As in 1505 and 1506 in FIG. 15, the description of “first edition” and “second edition” given for each version indicates which edition of “XX Product Manual” is designated as a part of which edition. Is shown. What is the first embodiment? Compound document version update program 10
7. The processing of the compound document version history display program 108 is different, and the other processing is the same.

In this embodiment, as in the first embodiment, a terminal device 101, a CPU 102, a medium 103 such as a floppy disk for distributing documents, a BUS 104, secondary storage devices 109a, 109b, 109c, a document component And a temporary storage device storing a processing program 105 for managing the version of the compound document.
06, the compound document version update program 107,
It comprises a compound document version history display program 108. Also, as in the first embodiment, the secondary storage device 1
09a stores a configuration information table for managing the configuration of a compound document, the secondary storage device 109b stores a version information table of each document component, and the secondary storage device 109c stores each version of the document component.

Next, the procedure of the compound document version update processing in this embodiment will be described. FIG. 13 is a flowchart illustrating a procedure of a compound document version update process by the compound document version update program 107 according to the present embodiment. First, in step 301, a user edits a document part. Next, in step 302, the version information table of the document component edited in step 301 stored in the secondary storage device 109b is updated. In step 1301, a new version of the document part created in step 302 is set to which edition part of the compound document. For example, as shown in FIG.
Edit "body.sgm", upgrade from V1 to V2, and set V2 to "for first edition" (1505). In addition,
If no edition is set, the settings of the previous version are inherited. In step 303, the change of the document structure and document parts of the compound document is notified. Step 303
, A new configuration information table is created in step 304 and stored in the secondary storage device 109a. Although the configuration information table to which the edition has been added is not shown in the figure, an edition is added to the configuration information table shown in FIG. 7 to manage the file name, document ID, version, and edition of each document part. Becomes In step 305, the user specifies from the terminal device 101 whether or not to end the editing of the document part. If the editing of the document part is continuously specified, the process returns to step 301.

Next, the procedure of the compound document version history display processing in this embodiment will be described. FIG. 14 is a flowchart illustrating a procedure of a composite document configuration information display process by the configuration information display program according to the present embodiment. First, in step 401, a configuration information table representing the version history of a compound document is obtained from the secondary storage device 109a. In step 1101, version information such as the creator of each document component constituting the compound document and the date and time of creation is acquired from the secondary storage device 109b. In step 1401,
According to the configuration information acquired in step 401 and the creation date and time of each document component acquired in step 1101,
Regarding the specified edition, it is considered that the version of the compound document is increased each time the version of the document component is increased, and the version history of the temporary compound document for each edition is synthesized. At this time, if all of the document parts constituting the configuration information table have the specified edition number, the configuration information table is duplicated, and the document parts having the edition number larger than the edition number specified in the configuration information table are copied. Is included, a configuration information table is generated in which the document part is replaced with the latest version of the version having the specified edition number. In addition, when a document part having the specified edition number is prepared for the first time, a document part having the specified edition number and an old version is included in any of the document parts at this time. , A configuration information table including the old version is also generated. Then, the version history of the temporary compound document for each edition composed of the copied and generated configuration information tables is synthesized.

Here, the compound document “XX Product Manual”
15 is edited as shown by 1501 in FIG. 15, for example, a case where the version history of the edition of the first edition of the "XX product manual" is presented. Based on the configuration information table 1502 created as the version history of the compound document “XX product manual” and the version history of each document part, the version history of the edition called the first edition is created. June 1
Looking at the configuration information table 1507 as of the date, since all editions of the document parts are set for the first edition, they are copied as they are to create the configuration information table 1508 which constitutes the version history of the edition first edition. .
Also, looking at the configuration information table as of June 8, 1509, the edition of V3 of “body.sgm” and the edition of V2 of “chapter 1.sgm” are set for the first edition, but 1.bmp '' V3
The edition is set for the second edition. Therefore,
Replace with the latest version V2 of the version set for the first edition of "Fig. 1.bmp" and V of "body.sgm"
3. A configuration information table 1510 composed of V2 of “Chapter 1.sgm” and V2 of “FIG. 1.bmp” is generated. In this way, the version history 150 of the edition called the first edition composed of the copied or generated configuration information table.
3 can be synthesized and displayed. For example, "○
○ When presenting the version history of the second edition of the "Product Manual", looking at the configuration information table as of June 6, V2 of "Main unit.sgm", "Chapter 1.sg
The m2 V2 edition is set for the first edition, and the V3 edition of "Fig. 1.bmp" is set for the second edition. So June
As of the sixth day, since the second edition document component has not been completely created, the second edition configuration information table is not generated. However, as of June 13,
"Body.sgm", "Chapter 1.sgm" and "Figure 1.bmp" are all created for the second edition, "Body.sgm" is V4, and "Chapter 1.sg
"m" is V4 and "Fig. 1.bmp" is V4, but for "Fig. 1.bmp", V3 has already been created for the second edition.
"Main unit.sgm" is V4, "Chapter 1.sgm" is V4, and "Figure 1.bmp" is V3
Then, the “main body.sgm” generates the configuration information table of V4, the “chapter 1.sgm” generates the configuration information table of V4, and “FIG. 1.bmp” generates the configuration information table of V4. Then, the version history 1504 of the edition called the second edition composed of the copied or generated configuration information table can be synthesized and displayed.

In step 1103, version history information of the compound document for each edition synthesized in step 1401 is displayed. Then, in step 403, the terminal device 101 determines whether the user ends display of the document part.
Specify from. Step 40 to continue displaying
Return to 1. In step 1401, if a configuration information table having the same information as the copied or generated edition-specific configuration information table is already included in the edition-specific version history, the copied or generated configuration information table is editioned. You can also prevent it from being added to another version history. In step 1401, if the same configuration information table is included in the edition-specific version history, only one duplicated configuration information table may be displayed.

With the above steps, the version history of the compound document can be grasped in the same manner as in the first embodiment. Further, the edition of the compound document is set for each version of the document part, and the compound document for each edition is set. Can be temporarily combined and presented. As a result, each author can proceed with writing for each edition at his own pace, and can further grasp the change history of each edition of the compound document. Also,
Also in the present embodiment, the version history list of the compound document can be displayed, referenced, and the like by the use method as described in the first embodiment. The above is the description of the third embodiment of the present invention.

Hereinafter, a fourth embodiment of the present invention will be described with reference to the drawings. FIG. 16 shows the configuration of this embodiment. As shown in FIG. 16, in the present embodiment, the configuration information table registration program 106 in the configuration of the first embodiment (FIG. 1),
Together with the compound document version update program 107,
This is represented as a compound document change history management program 1603. Then, a document management method selection program 1601 and a configuration management program 1602 are added to the configuration of the first embodiment (FIG. 1). The configuration management program 1602 is a registration / change program in the known example 2,
It is composed of a reference program and an editing program, and makes it possible to manage document component version management and configuration management in cooperation. Further, the version information table for the version update mode description in the known example 2 is stored in the secondary storage device 109d.

Next, the procedure of the compound document management process in this embodiment will be described with reference to the flowchart of FIG. First, in step 1701, the document management method selection program 1601 is executed, and the user selects, from the terminal device 101, whether to perform “configuration management” or “change history management” for a compound document management method. If step 17
If "configuration management" is selected in step 01, the configuration management program 1602 is executed in step 1702 to register each document part of the compound document as a component of the configuration management folder, and link the version management and the configuration management of the document parts. Perform the management that was performed. If “change history management” is selected in step 1701, step 170
3 executes the compound document change history management program 1603, and when the state of the compound document changes due to the change of each document part or the structure of the compound document, the history of all state changes of the compound document is held. Perform management. Then, in step 1704, the user specifies from the terminal device 101 whether or not to end the management of the compound document. When the management is performed by a new method, the process returns to step 1701.

According to the above steps, there is an effect that the management method can be changed depending on the document to be managed, even for a compound document registered in the same document management system. For example, when managing documents such as legal documents that you want to keep track of when and what changes were made, select "Change History Management" to save the entire history of the compound document. can do. Further, for example, when creating a technical review memo or the like, if it is desired to perform management to reflect the latest version of each document component, this can be realized by selecting “configuration management”.
Note that the second and third embodiments can be implemented in the same manner as the present embodiment. That is, although the processing of the compound document change history management program 1603 is different, the configuration management program 1602 and the compound document change history management program 1603
The document management method selection program 1601 can be used to select which is used for management.
The above is the description of the fourth embodiment of the present invention.

Hereinafter, a fifth embodiment of the present invention will be described with reference to the drawings. In the present embodiment, when a compound document is registered, for each document part, the document part is a “version reflection element” for reflecting the version upgrade in the version upgrade of the compound document, or the version upgrade is performed. "Version reflection type" that indicates whether it is a "version fixed element" that is not reflected in the version upgrade of a compound document can be set, and only when the document part set in "version reflection element" is upgraded, the compound document Create a new version of.

This embodiment is different from the first embodiment in the processing of the configuration information table registration program 106 and the compound document version update program 107, but the other processing is the same. This embodiment is similar to the first embodiment in that the terminal device 1
01, a CPU 102, a medium 103 such as a floppy disk for distributing documents, a BUS 104, secondary storage devices 109a, 109b, 109c, and a processing program 105 for managing versions of document parts and compound documents. The program 105 includes a configuration information table registration program 106, a compound document version update program 107, and a compound document version history display program 108. As in the first embodiment, a configuration information table for managing the configuration of a compound document is stored in the secondary storage device 109a, a version information table for each document component is stored in the secondary storage device 109b, and a secondary storage device 109c is stored. Stores respective versions of document parts.

Next, the procedure of the configuration information table registration processing in this embodiment will be described. FIG. 20 is a flowchart illustrating a procedure of a configuration information table registration process by the configuration information table registration program 106 according to the present embodiment. A case where a compound document as shown in FIG. 19 is registered will be described as an example. First, in step 2001, a document component group constituting a compound document specified by a user is read. For example, when a compound document as shown in FIG. 19 is registered, “manual.dtd”, “body.sgm”, “chapter 1.sgm”
"m" and "Figure 1.bmp" are specified, and those document parts are read. Next, in step 2002, step 2001
The specified version reflection type is set for each document part registered in step. In step 2003, a configuration information table corresponding to the specified document component group is created, and the configuration information table is registered in the secondary storage device 109a and the document component group is registered in 109c. For example, as shown in FIG. 22, “manual.dtd” is “version fixed element”,
For "body.sgm", "chapter 1.sgm", and "Figure 1.bmp", set the version reflection type such as "version reflection element". Then, as shown in 2201, a configuration information table for managing the file name, document ID, version, version reflection type, and the like of each document component is created and registered. Then, in step 2004, the user specifies from the terminal device 101 whether or not to end the registration of the compound document. When registering a new configuration information table, the process returns to step 2001. In the above configuration information table registration processing,
A method is also possible in which the version reflection type of a document component expressing the schema information of a compound document such as a DTD in an SGML document is automatically set as a fixed version element and registered. For example, when registering a compound document as shown in FIG. 19, the extension of the document part to be registered is determined, and “manual.dtd” is automatically set as the version fixed element, and the other document parts (“body.sgm , "Chapter 1.sgm", "Figure 1.bmp") can be set as the version reflection element.

Next, the procedure of the compound document version updating process in this embodiment will be described. FIG. 21 is a flowchart illustrating a procedure of a version update process of a compound document according to the present embodiment. First, in step 2101, each document component constituting the compound document edited by the user is registered in the secondary storage device 109c. Next, in step 2102,
The version information table that manages the version name, creator, creation date and time of the document part edited in step 2101 is updated. The version information table is stored in the secondary storage device 109b. In step 2103,
In step 2101, it is determined whether the document configuration has been changed. If the document structure has been changed, the process proceeds to step 2104. If the document structure has not been changed, the process proceeds to step 2106.

In step 2104, it is determined whether a new document component has been added. If a new document part has been added, the process proceeds to step 2105; otherwise, the process proceeds to step 2107. In step 2105, the version reflection type of the added new document component is set in step 2101.
Set according to the user's specification in. For example, FIG.
In the editing example, when "chapter 2.sgm" is added on June 17, the document part is set as a version reflection element. In step 2106, the configuration information table is referred to,
It is determined whether the edited document part is a version reflection element. If it is a version reflection element, the process proceeds to step 2107, and if it is a version fixed element, the process proceeds to step 2108. In the case of the example of FIG.
The document parts edited and upgraded in 101
In the case of “1.sgm”, since “chapter 1.sgm” is a version reflection element, the process proceeds to step 2107 to create a new configuration information table. If the “manual.dtd” is edited, the process proceeds to step 2108 without creating a new configuration information table because “manual.dtd” is a fixed version element. In step 2107, a new configuration information table corresponding to the change of the document configuration or the upgrade of the document components is created and stored in the secondary storage device 109a.
In step 2108, it is determined whether there is another edited document. If there is another edited document, the process returns to step 2102. If no other documents have been edited,
finish.

As described above, for each document part constituting the configuration information table, the version reflection type indicating whether it is a “version reflection element” or a “version fixed element” can be set. That only the version of the document part desired by the user is reflected in the change of the version of the compound document.
That is, as shown in the example of FIG. 22, “body.sgm”, “chapter 1.sgm”, “FIG. 1.bmp”,
Create a new configuration information table when "Chapter 2.sgm" is upgraded. Then, it is possible to manage the version of the “manual.dtd” set in the version fixing element so that the version is fixed. In this embodiment, in the compound document version update program,
A new configuration information table is created every time a document configuration is changed and a document part is upgraded. However, as in the second embodiment, a new configuration information table is created only when the document configuration is changed. Is created, and the other tables can be combined later. Also in the present embodiment, it is possible to display and refer to a version history list of a compound document by the use method as described in the first embodiment. The above is the description of the fifth embodiment of the present invention.

Hereinafter, a sixth embodiment of the present invention will be described with reference to the drawings. In the present embodiment, when managing the configuration of a compound document, a change history according to the operation of changing the version update mode or changing the document configuration is synthesized. FIG. 23 shows the configuration of this embodiment. As shown in FIG. 23, in this embodiment, the configuration information table registration program 106 and the compound document version update program 10 in the configuration (FIG. 1) of the first embodiment.
7, the compound document version management program 16
03. Then, the configuration management program 1 in the fourth embodiment is added to the configuration of the first embodiment (FIG. 1).
602, configuration change record table registration / update program 2
301 is added.

Next, the procedure of the configuration change record table registration / update processing in this embodiment will be described with reference to the flowchart of FIG. First, in step 2401,
It is determined whether the configuration management program 1602 has changed the version update mode or the document configuration. If there is a change, the process proceeds to step 2402, and if there is no change, the process ends. In step 2402, the configuration change record table is created by the configuration change record table registration / update program 2301, and the change date and time, the file name, and the like are recorded. The configuration change record table is stored in the secondary storage device 109e. Here, the configuration change record table records the operation history of the change of the version update mode performed by the user or the change of the document configuration in the process of managing the configuration of the compound document. As shown in FIG.
The configuration change record table 2600 stores the configuration management folder.
It has information such as ID, configuration management folder version, date and time of change of document parts, file name, document ID, version, version update mode, and the like. In FIG. 26, the date and time information is only information in units of dates, but it is also possible to record the information in smaller units.

FIG. 27 shows the process of editing a compound document registered in the configuration management folder. Where 270
Reference numeral 1 denotes the editing status of each document part. For example, 270
Reference numeral 4 indicates that V1 of “body.sgm” is registered in the automatic update mode in V1 of the configuration management folder. It was upgraded to V2 on June 3 (270
5), V2 of “main unit.sgm” in V1 of the configuration management folder
Is registered in the confirmation mode. Reference numeral 2702 denotes the version of the configuration management folder and its change status. At the time of registration on June 1, the configuration management folder
V1 is 2706 like "body.sgm" V1 (automatic update mode), "chapter 1.sgm" V1 (automatic update mode), "Figure 1.sgm"
m ”V1 (confirmation mode), but changed as the document parts were edited. As of June 6,
V2 of “body.sgm” as in 2707 (confirmation mode),
The state has changed to V3 (fixed mode) in “Chapter 1.sgm” and V1 (fixed mode) in “Figure 1.sgm”. And
On June 8, the configuration management folder was upgraded from V1 to V2, and V1 in "Chapter 2.sgm" was added in automatic update mode. As a result, V3 (automatic update mode) of “body.sgm”, V3 (fixed mode) of “Chapter 1.sgm”, and “Fig. 1.sgm”
Configuration management folder V2 (2708) composed of V2 (automatic update mode) of "m" and V1 (fixed mode) of "Fig. 1.sgm"
Has been created. This configuration management folder V2 (270
8) is also changed as the document part is edited.

Next, how the editing status of the above-described compound document is recorded in the configuration change recording table 2600 will be described in further detail with reference to the editing example of FIG. The configuration change record table 2600 records information necessary for combining the change history of the compound document later, that is, information when the document configuration is changed and the version update mode is changed. First, when the configuration management folder is registered,
That is, the state recorded on June 1 is indicated by 26 in FIG.
01 are three rows. For all the registered document parts, the ID “0122” of the configuration management folder “XX Product Manual”, the version “V1” of the configuration management folder, the modification date and time “1999/6/1”, and the document part information As the file name, document ID, version, and version update mode. Next, when “body.sgm” is fixed to V2 in the confirmation mode on June 3, it is recorded in the configuration change record table. The three lines 2602 in FIG. 26 correspond to this, and the date and time information “1999/6/3” at the time of setting the fixed mode is recorded as the change date and time. Similarly, three rows of 2603 record the operation history of V3 of “Chapter 1.sgm” set to the confirmation mode on June 6, and four rows of 2604 are recorded on June 8 It records the operation history when V1 in "Chapter 2.sgm" was added in the automatic update mode. As described above, the version update mode and the document configuration change information are
It is recorded in the configuration change record table.

Next, a processing procedure of compound document change history synthesis in this embodiment will be described with reference to the flowchart of FIG. It should be noted that a change history of a compound document to be synthesized based on the information of the configuration change record table 2600 and the version information of the document parts as indicated by 2703 in FIG. 27 is referred to as a “synthesis log”. First, in step 2501, a line having the same configuration management folder ID, version, and change date and time is extracted from the configuration change record table. Then step 25
In step 02, a “synthetic log” of a compound document composed of the versions of the document components extracted in step 2501 is created. In the example of the configuration change record table 2600 in FIG. 26, first, three lines of the portion 2601 are extracted, and the version of the document part, that is, V1 of “body.sgm”
A composite log (2709) of a compound document composed of (automatic update mode), V1 of "chapter 1.sgm" (automatic update mode), and V1 of "FIG. 1.sgm" (confirmed mode) is created. In step 2503, of the document parts extracted in step 2501, the version of the document part that has been upgraded first is extracted from the date and time of version upgrade of the document part in the automatic update mode. In the example of FIG. 26, among the document parts extracted in step 2501, the automatic update mode is V1 of “body.sgm” and V1 of “chapter 1.sgm”.
It is. Among them, the one with the earliest version update date and time is the version upgrade to V2 on June 2 `` Chapter 1.
sgm ".

In step 2504, it is determined whether the date and time of creation of the version of the document part extracted in step 2503 is earlier than the next change date and time in the configuration change record table. If the creation date and time of the version of the document part extracted in step 2503 is earlier,
Then, the process proceeds to step 2 to create a composite document composite log in which the created date and time of the extracted document part are replaced. Also,
If it is determined that the next change date and time in the configuration change record table is earlier, the process proceeds to step 2505. For example, FIG.
Referring to the configuration change record table 2600 of FIG.
The next change date and time of "/ 6/1" is "1999/6/3", and the date and time (June 2) when "Chapter 1.sgm" extracted in step 2503 is upgraded to V2 is earlier . Therefore, the process proceeds to step 2502, where “chapter 1.sgm” is replaced with V2, “body.sgm” V1 (automatic update mode), and “chapter 1.sgm”.
m ”(automatic update mode) and“ 1.sgm ”V1 (fixed mode) composite log of compound document (2710)
Create Next, in step 2505, it is determined whether or not there is a line whose change date is later than the change date extracted in step 2501. Step 2501 if any
Go to, otherwise end.

In the example shown in FIG.
504 is repeated to combine all the histories of the document parts upgraded after “1999/6/1” before “1999/6/3”. Create a composite log of document parts that have been upgraded since "1999/6/3". With the above steps, when managing the composition of a compound document,
It is possible to acquire a change history according to the operation of changing the version update mode or changing the document structure. Also in the present embodiment, the version history list of the compound document can be displayed, referenced, and the like by the use method as described in the above-described embodiment. The above is the description of the sixth embodiment of the present invention.

[0069]

As described above, according to the version control method of a compound document according to the present invention, the version of the entire compound document is increased in accordance with the change of the document structure or the change of the document parts, so that all the change histories of the compound document can be obtained. Can be stored and managed. As a result, when,
This makes it possible to grasp which document component has been edited, or to return to the previous editing state in a unit of a compound document, and to provide a great effect in the joint writing of a large-scale compound document.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of a first embodiment of the present invention.

FIG. 2 is a flowchart illustrating a procedure of a configuration information table registration process according to the first embodiment of the present invention.

FIG. 3 is a flowchart illustrating a procedure of a compound document version update process according to the first embodiment of the present invention.

FIG. 4 is a flowchart illustrating a procedure of a compound document version history display process according to the first embodiment of the present invention.

FIG. 5 is a diagram showing an example of a compound document for performing version management.

FIG. 6 is a diagram illustrating an example of editing a document component constituting a compound document.

FIG. 7 is a diagram showing an example of a configuration information table according to the present invention.

FIG. 8 is a diagram showing an example of a version information table according to the present invention.

FIG. 9 is a diagram illustrating an example of creation of a configuration information table according to a version upgrade of a document part according to the present invention.

FIG. 10 is a flowchart illustrating a procedure of a compound document version update process according to the second embodiment of the present invention.

FIG. 11 is a flowchart illustrating a procedure of a compound document version history display process according to the second embodiment of the present invention.

FIG. 12 is a diagram illustrating an example of creating a configuration information table according to a second embodiment of the present invention.

FIG. 13 is a flowchart illustrating a procedure of a compound document version update process according to the third embodiment of the present invention.

FIG. 14 is a flowchart illustrating a procedure of a compound document version history display process according to the third embodiment of the present invention.

FIG. 15 is a diagram showing an example of presenting a version history of a compound document by edition in the third embodiment of the present invention.

FIG. 16 is a diagram showing a configuration of a fourth exemplary embodiment of the present invention.

FIG. 17 is a flowchart illustrating a procedure of a compound document management process according to the fourth embodiment of the present invention.

FIG. 18 is a diagram for describing configuration management in the related art.

FIG. 19 is a diagram illustrating an example of an SGML document for performing version management and a configuration information table.

FIG. 20 is a flowchart illustrating a procedure of a configuration information table registration process according to the fifth embodiment of the present invention.

FIG. 21 is a flowchart illustrating a procedure of a compound document version update process according to the fifth embodiment of the present invention.

FIG. 22 is a diagram illustrating an example of creating a configuration information table by setting a version reflection type according to the fifth embodiment of the present invention.

FIG. 23 is a diagram showing a configuration of a sixth example of the present invention.

FIG. 24 is a flowchart illustrating a procedure of a configuration change management process of a compound document according to a sixth embodiment of the present invention.

FIG. 25 is a flowchart illustrating a procedure of a compound document change history combining process according to the sixth embodiment of the present invention.

FIG. 26 is a diagram showing an example of a configuration change record table according to the present invention.

FIG. 27 is a diagram illustrating an example of change history synthesis of a compound document according to the sixth embodiment of the present invention.

FIG. 28 shows an example of a display screen of a compound document according to the present invention (1).
FIG.

FIG. 29 shows an example of a composite document display screen (2) according to the present invention.
FIG.

FIG. 30 is an example of a display screen of a compound document according to the present invention (3).
FIG.

FIG. 31 shows an example of a display screen of a compound document according to the present invention (4).
FIG.

[Explanation of symbols]

 101 terminal device 102 CPU 103 medium 104 BUS 105 processing program 109 secondary storage device 106 registration program 107 compound document version management program 108 configuration information display program 109 secondary storage device 1601 document management method selection program 1602 configuration management program 1603 compound document change History management program 2301 Configuration change record table registration / update program

Continued on the front page (72) Inventor Takuya Okamoto 890 Kashimada, Saiwai-ku, Kawasaki-shi, Kanagawa Prefecture Inside the Hitachi, Ltd.System Development Division (72) Inventor Yuki Aoyama 890 Kashimada, Saiwai-ku, Kawasaki-shi, Kanagawa Hitachi, Ltd. Within the headquarters (72) Inventor Yasuki Ito 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Within the Hitachi, Ltd.Software Division (72) Inventor Noriyuki Yamazaki 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Software, Ltd. F-term in business division (reference) 5B009 QA07 QB18 SA14

Claims (16)

[Claims] 1. A function for registering a compound document composed of a plurality of document parts, a function for updating the contents of the registered compound document, and a change history of the compound document and each document part constituting the compound document A compound document version management method in a document management system having a function of managing a compound document, wherein as a process of registering a compound document, configuration information including document component information of document components of the compound document to be registered is generated. A method for managing a version of a compound document, comprising the step of storing information in association with the compound document. 2. The compound document version management method according to claim 1, further comprising a step of analyzing contents of the compound document to be registered and extracting part information of document parts of the compound document. Version control method. 3. The compound document version management method according to claim 1, wherein the processing of updating the contents of the compound document includes adding or deleting a document part to or from the compound document. A compound document version management method comprising: generating composition information of a compound document corresponding to a state after deletion, and registering the composition information as a new version of the compound document. 4. The compound document version management method according to claim 3, further comprising the step of displaying each registered version as a version history of the compound document. 5. The compound document version management method according to claim 3, wherein whether or not a document part is added or deleted from the compound document is determined by analyzing a description content of a main document part of the compound document. A compound document version management method comprising: 6. The compound document version management method according to claim 3, wherein the processing of updating the contents of the compound document includes the step of: Generating version information of the document part of the compound document corresponding to the updated state of the document part, and registering the structure information as a new version of the compound document. Method. 7. The compound document version management method according to claim 6, further comprising the step of displaying the registered version as a version history of the compound document. 8. The compound document version management method according to claim 3, wherein, as the process of managing the version history of the compound document, the creation date and time of the configuration information corresponding to each version of the compound document and the holding of the configuration information Comparing the creation date and time of each version of each document part to be detected, detecting a document part whose version has been updated between adjacent versions in the configuration information,
Generating temporary configuration information corresponding to the version update of the document part; configuration information group forming a version history of the compound document; and temporary configuration information group corresponding to the version update of the document part. A compound document comprising: a step of creating a temporary version history that is synthesized and arranged in accordance with a time series of an event that has caused the generation of configuration information; and a step of displaying the temporary version history. Version control method. 9. The compound document version management method according to claim 5, wherein, as a process of updating the content of the compound document, when a new version of the document component is created, the version of the document component is added as a compound document. Setting the edition number indicating the version of the compound document, and determining which edition of the compound document the document part of the version becomes the document part of the compound document. As a process of managing the version history of the compound document, When all the document parts held by the configuration information corresponding to the version have the specified edition number, the configuration information is generated as the configuration information of the specified edition, and the configuration information corresponding to each version of the compound document inside,
If a document part having an edition number greater than the specified edition number is included, the document part is replaced with the latest version of the version having the specified edition number of the document part, and Generated configuration information of the edition, and in the configuration information corresponding to each version of the compound document,
If a document part having an edition number smaller than the specified edition number is included, the document part is replaced with the oldest version of the version having the specified edition number of the document part, and Generating a configuration information of the generated edition; and displaying the generated configuration information as a version history for each edition of the composite document. 10. The compound document version management method according to claim 3, wherein the process of registering the compound document includes: for each document component forming the compound document, A step of setting either a version reflection element or a fixed version element as a version reflection type indicating whether or not the version upgrade is to be reflected in the version upgrade of the compound document; When the document component whose version reflection type is set to the version reflection element is edited and the version is updated, the configuration information of the document component corresponding to the updated state of the document component is generated, and the generated Registering the configuration information as a new version of the compound document. Version management method of writing. 11. The compound document version management method according to claim 10, further comprising the step of displaying the registered version as a version history of the compound document. 12. The compound document version management method according to claim 10, wherein, as the process of registering the compound document, for a document component expressing schema information of the compound document, a version reflection type of the document component is set. A compound document version management method characterized by setting and registering a fixed version element. 13. The compound document version management method according to claim 3, wherein a name of a component to be managed, a name of a file storing the component, a version number of the component, and a version of the component. (Version) in the version update mode description configuration information table that records the version update mode indicating whether the status is automatically updated or not, registering or updating the component names and the file names storing them, Setting or changing the version update mode of each component described in the version update mode description configuration information table; setting the version number of each component described in the version update mode description configuration information table; Configuration element name, file name, version number, and version update mode description configuration information indicating the version update mode described in the mode description configuration information table Storing the version update mode description configuration information from the version update mode description configuration information table, and storing a document corresponding to the version number represented by the obtained version update mode description configuration information. Acquiring from the secondary storage device, displaying the document acquired by the document acquiring step, and after editing the document acquired by the document acquiring step,
Referring to a version information table that records the version number, creator, creation date, etc. of each version, saves the edited document as a new version in a secondary storage device, and saves information of the new version in the version information table Then, the version update mode of the component corresponding to the edited document described in the version update mode description configuration information table is determined, and if the version update mode is “determined mode”, the version number is updated. In the case of "automatic update mode", a configuration management step having a step of updating the version number, and information relating to a change in the version update mode and a change in the document configuration performed in the configuration management step are stored in a document configuration. A document configuration change information recording step of recording as change information; Based on the version information of each document part, to synthesize a version history of a composite document, version control method of a composite document, characterized in that it comprises a compound document version history management step of displaying. 14. A document part configuration information registration step of generating configuration information of a document part of a composite document to be registered, associating the configuration information with the composite document and registering it as an original version of the composite document, A component information extracting step of analyzing the content of the document component to extract component information; and a document component of the compound document corresponding to a state after the addition or deletion of the document component when the document component is added or deleted from the compound document. A composition document version management program having a compound document version updating step of registering the composition information as a new version of the compound document and displaying each registered version as a version history of the compound document. Computer readable recording medium. 15. A document part configuration information registration step of generating configuration information of a document part of a composite document to be registered, associating the configuration information with the composite document, and registering it as an original version of the composite document; A component information extraction step of analyzing the contents of the document component and extracting component information; and a document component of the compound document corresponding to the state after the addition or deletion of the document component when the document component is added or deleted to the compound document. A first new version registration step of generating the composition information of the compound document and registering the composition information as a new version of the compound document; and a step of editing any one of the document parts constituting the compound document and updating the version. Generating the configuration information of the document part of the compound document corresponding to the state of the document part after the version update, and converting the structure information to a new version of the compound document. A computer readable recording of a compound document version management program having a second new version registering step of registering the compound information as a version and a compound document version displaying step of displaying each version of the registered configuration information as a version history of the compound document recoding media. 16. A document part configuration information registration step of generating configuration information of a document part of a composite document to be registered, associating the configuration information with the composite document and registering it as an original version of the composite document, A component information extracting step of analyzing the content of the document component to extract component information; and a document component of the compound document corresponding to a state after the addition or deletion of the document component when the document component is added or deleted from the compound document. A first new version registration step of generating the composition information of the compound document and registering the composition information as a new version of the compound document; and a step of editing any one of the document parts constituting the compound document and updating the version. Generating the configuration information of the document part of the compound document corresponding to the updated state of the document part, A second new version registration step of registering the original configuration and the first new version of the registered configuration information as a first version history of the compound document. A computer-readable recording medium recording a compound document version management program having a compound document version updating step of separately displaying a version as a second version history of the compound document.