JPH02289084A - Document managing and processing system - Google Patents

Abstract

PURPOSE:To efficiently manage link information between plural documents, and also, to correctly execute the version management by constituting this system so that a traverse processor for determining a document of a traverse destination utilized link information and version information on a document file. CONSTITUTION:On a document file 10, link information and version information are described. That is, a setting/release processor 5 of a link executes an access to the link information, and a history management processor 6 manages the version information which generates newly the document file in accordance with a version. In this state, in the case information related to a document corresponding to some document file 10 is displayed in a terminal 9, and traversed to a display related to other related document, a traverse processor 7 determines a document file of a traverse destination, based on the link information and the version information on the document file 10. In such a way, the link information between plural documents can be managed efficiently, and also, the version management in the case updating is executed in each document can be executed correctly.

Description

[Detailed Description of the Invention] [Summary] A document processing system that stores multiple documents related by link information as document files and processes the documents efficiently manages link information between multiple documents. 2. In order to correctly perform version control when updates are made to individual documents, link information indicating other documents linked to the relevant document and link information on the document file are added to the document file. A traverse processing device determines a document to be traversed when traversing from a display state related to a document that holds version information of a document to a display state related to another document.

The link information and the virgin information on the document file are configured to be used.

[Industrial Application Field] The present invention relates to a document processing system that stores a plurality of documents related by link information as document files and processes the documents.

Documents created in the process of large-scale program development, such as specifications, design documents, and programs, have mutual dependencies, and it is required to quickly search for documents based on these dependencies. There is.

(Prior Art) In order to provide the above-mentioned dependency relationship, link information is provided to show the relationship between nine documents, and the desired document is accessed by following the link information.

Patent Application No. 176217/1983, filed by the applicant earlier, ``In the data management device J, when storing the above link information, the above link information is stored in an area different from the area where the three documents are stored. That's what I do.

[Problem to be solved by the invention] In the above-mentioned document management, individual documents may be updated one after another, and version management (
(version control) is required.

Patent application No. 63-17621 filed for the above-mentioned light? In No. 1, one document and link information were stored separately, so it is necessary to always consider the relationship between the eight documents and the vergecon while retaining the link information.

That is, when saving a version of one document, all link information that links to that document must be updated. In addition, there are cases where it is desired to use link information provided in an older version of a document, but such use has been practically difficult.

SUMMARY OF THE INVENTION In order to solve the above-mentioned problems, the present invention aims to efficiently manage link information between multiple documents and to correctly perform version control when updates are made to each individual document. .

[Means to solve the problem]

FIG. 1 shows a basic configuration diagram of the present invention. The code 1 in the diagram is 9
A secondary storage device that stores document files. Note that one document file (document file 10 described later) is 1
Compatible with two verge controllers.

3 is a main storage device into which the document file of the secondary storage device 1 is loaded. 2 is a file processing device that loads documents on the secondary storage device 1 into the main storage device 3 or conversely saves them. 4 is a document creation/modification processing device that creates or updates a document on the main storage device 3; Reference numeral 5 denotes a link setting/cancellation device that creates a link to a document on the main storage device 3 or deletes the link.

Also, when 6 saves the two documents to the secondary storage device l,
This is a history management processing device that creates version information regarding the version of the document. Reference numeral 9 denotes a terminal for inputting information regarding document processing or displaying documents and menus. Reference numeral 8 denotes a document display/menu display processing device that performs control between the terminal 9 and the main storage device 3.

Furthermore, 7 is a traverse processing device that determines a document to be traversed when traversing from a display state related to one word displayed on the terminal 9 to a display state related to another document.

Further, 10 is a document file that holds (i) a file management section; (i) document contents; (iii) link information to other documents; and (iv) version information of the document. Note that the contents of the curly brackets shown on the right side of the figure represent the respective description contents.

[For production]

Needless to say, the document file 10 is loaded onto the main storage device 3 to be processed, but as shown in FIG. 1, link information and version information are written on each document file 10. That is, the link setting/cancellation processing device 5 accesses the link information, and the i-history management processing device 6 creates a new document file and manages version information in accordance with the version.

Then, when information about a document corresponding to the document file 10 is displayed on the terminal 9 and the display is traversed to a display about another related document, the traverse processing device 7
Based on the above link information and version information, the document file to be traversed is determined.

[Example] Figure 2 is an explanatory diagram of link status, and Figure 1m3 is an explanatory diagram of version link information, which shows how link information and version information are generated and used in the case of the present invention. ing.

Each document has headers Fl, F2 . It is maintained in a linked list format. The state shown in FIG. 2 (A) is
(i) Document file 10- corresponding to the first version of document #l
1-1 is concatenated with the header Fl.

(ii) Document file to corresponding to the first version of document #2
-2-1 is linked to header F2, and (ii) document file 1 is linked by link information in document file 1m-1-1.
0-2-1 represents a linked state.

FIG. 2(B) shows the state when one document file 10-1-1 is saved in the secondary storage device 1 from the state of FIG. 2(A). In this case, document file 10-1-2 corresponding to the second version of document #l is generated on the list, document file 10-11 is described as a link destination on the version information, and document file 9 document file 10-1 Since document file 10-2-1 was held as the link destination on the link information, document file 10-2-1 was held as the link destination on the link information in document file 101-2.
1 is posted.

FIG. 2(C) shows a state when nine document files 10-2-1 are saved in the secondary storage device 1 from the state shown in FIG. 2(B). In this case, the document file 10-22 corresponding to the second version of the first document #2 is generated on the list, and the second document file 10-2-1 is described as a link destination on the version information.

The state shown in FIG. 3 is the state shown in FIG. 2(C) for each document file 10-1-1. 1m-1-2,to-
2-1 and 10-2-2 are shown. Note that "document" on each document file is omitted. In the state shown in FIG.

(A) Regarding the document file 10-1-1, in the file management section.

(file, verl (version number 1) (version verl) (link 1 inkl) is written, and the link information indicates that it was linked to the link destination ' file2. verl J on October 3rd.

(linkl (date October 3rd) (link destination fi le2. verl) is written, and the version information should indicate that it was created on October 1st.

(verl (84cm October 1st) (link destination)
file, verl) are described.

(B) Regarding the document file 10-1-2, to the file management section.

(file, ver2 (version number 2) (version verl ver2) (link
1inkl) is written, and the link information indicates that it was transcribed from document file 10-1-1 on October 3rd.

(l 1nkl (84 sun October 3rd) (link)
file2. verl) is written, leaving the information transcribed from the 1-document file 10-1-1 as the version information, and indicating that the second version was created on October 4th.

(verl (84cm October 1st) (link destination)
file, verl) (ver2 (84cm October 4th) (link)
f 1le1. version 2) is described.

(C) Document file 10 In the file management section, (file2. To represent it, (verl (84 cm October 02) (link destination file2.verl) is written.

(D) Document file 10 In the file management section, (file2. To preserve the transcribed information and to indicate that the second edition was created on October 5th.

(verl (84cm October 2nd) (link)
file2. verl) (ver2 (date October 5th) (link destination file2.ver2) is described.

From the state shown in Figure 3, you can find out the date each document file was created, the date it was linked to other documents, the linked document files, and how many older versions exist than the own file. be able to.

FIG. 4 shows the save menu and operation flow.

FIG. 4(A) shows a menu when accessing a document file, and after displaying the menu as shown in FIG. 4(A) on the display (not shown) of the terminal 9, select ``rNewFile''. or rMerge J or rOverwrite J.

FIG. 4(B) shows the operation flow in the case of 'New File'. "rNew File" corresponds to the process for creating a new document file (for example, 10-1-2 shown in FIG. 2).

Process ■: Version number rlJ and document file name rfile of 9 document file 10-1-1 from the file management section (not shown)
1. ``Verl''.

Process ■: Set the version number to "2".

Process ■: Copy the entire list for document #1.

Processing ■: Set the version number of the file management section to "2" and set the file name to r file, ver2 J.

Process (2): Secure a storage area for the document file 10-1-2 for the second edition.

Processing ■: Describe each content of text file 0-1-2.

Processing fl ■ About document file 10-1-2 File name rfile1. ver2” is registered.

Process ■: Herada F1 shown in Figure 2 is the document file 10-
Make it point to 1-2.

FIG. 4(C) shows the operation flow in the case of r Merge J. rMerge J supports processing when only version information is changed without changing the file name. Also, Fig. 4 (D) shows “0vers+ri
The operation flow when te is 1 is shown.

rOverwriLe J supports the process of modifying only the contents without changing the file name or version information.

What are the processing in FIG. 4(C) and the processing in FIG. 4(D)?

Since this process is similar to the process shown in FIG. 4(B), a detailed explanation thereof will be omitted.

Figure 5 shows the version menu.

For example, when accessing the document file related to document #1 shown in FIG. 2 (document file linked to header F1), the menu shown in FIG.
display on the display, and then instruct which document file to access (01, 0 as shown).
2, etc.).

FIG. 6 shows a version display flow, and represents the flow for displaying a document file designated by the menu in FIG.

Process (6-1): Obtain link destination in version information of document file specified in menu 9 For example, document file 10-1- related to document #l shown in FIG.
2 is specified, as shown in FIG.

"rfile, ver. 2" as a link destination in the version information is obtained. Furthermore, if the document file 10-1-1 is specified, as shown in Figure 3, rfile is specified as the link destination in the version information.
l, verl J is obtained.

Processing (6-2): In the above example, (i)
rfile.

If yer2 J is obtained, the process proceeds to step (63), but (ii) 'file1. verl" is acquired, the process proceeds to step (6-4).

Process (6-3): In this case, the contents of the storage area (not shown) storing the time mark T are deleted.

Processing (6-4): In this case, the date rlo month 4th when the second version was created in the storage area that stores time mark T.
Store. That is, in the case of 2 "file, verl J, it is the first version, so the date on which the second version of the first version was created is stored.

Process (6-5): In this state, the specified document file is loaded and displayed.

Figure 7 shows the traverse menu.

For example, document file 10 regarding document #l shown in FIG.
-9 document files 10- from 1-1, 10-1-2, etc.
2-1, a menu as shown in FIG. 7 is displayed on the display of the terminal 9, and the user instructs which document to traverse.

In other words, traverse the document "Specifications/Menu Processing Function" shown in the two diagrams, or display the "Summary Design Document/Function Group Configuration Diagram".
Indicates whether to traverse display documents.

Figure 8 shows the link destination display flow.
The flowchart shows a flow when performing traverse display on the document file 10-2-1.

Process (8-1): If the document specified in the menu shown in FIG. 7 is, for example, document #2, the header F2 of document #2 is known.

Process (8-2): In this case, check whether the original document file for which document #2 is to be traversally displayed is the latest version. That is, if the original document file is document file to-1-2, it is the latest version, and the process proceeds to step (8-5). If the original document file is document file 10-1-1, the process proceeds to step (8-3).

Processing (8-3): Load the document file 10-2-2 regarding header F2 of document #2.

Processing (8-4): Store the date “October 5th” in the version information in the document file to-2-2 first linked to Lada F2 and the above time mark (see Figure 8). The current date [October 4th] is compared. That is, in this case, since the two original document files were document files 1O 1-1, "October 4th" is stored as the time mark T in FIG. (see explanation regarding).rl on the 9th.

The date "October 4th" is compared with the date "October 4th". Since the date ``5th day of the month'' is newer than the date of the time mark T, the date of the latest version that is older than the 14th day of the time mark T ``1044 days'' is acquired. In the present case, as can be seen from the contents of the document file 102-2 shown in FIG. 3, the date "October 2nd" is obtained. and.

Document file 10-2-1 is header F It will be pointed from 2 onwards.

Process (8-5) If the original document file above is document file 10-1-2, process so that the newest document file linked to header F2 can be loaded (pointed to by header F2). do.

Processing (8-6): The document file pointed to from the ladder F2 at that time is loaded and displayed. That is, in the case from process (8-4), three document files 10-2-1 are displayed. Further, in the case of processing from step (8-5), one document file to-2-2 is displayed.

Note that the reason for performing the above process (8-4) is to prevent documents created after the original document file is updated from being traversed displayed. That is.

If the original document file is document file 10-1-1, 5 document files 10-1 after October 4th, which is the date when the document file 10-1-1 was updated.
Document file 1 (1-2) created in connection with -2, etc.
This is to avoid using -2.

〔Effect of the invention〕

As explained above, according to the present invention, the traverse processing device 7 can determine the traverse destination by looking at the contents of the document file, and also takes into account the date on which the original document file for displaying the traverse was updated. You can select the document file to be traversed and displayed.

[Brief explanation of drawings]

Fig. 1 is a diagram of the principle configuration of the present invention, Fig. 2 is an explanatory diagram of link status, Fig. 3 is an explanatory diagram of version/link information, Fig. 4 is a save menu and operation flow, and Fig. 5 is a diagram of version/link information.
6 shows the version display flow, FIG. 7 shows the traverse menu, and FIG. 8 shows the link destination display flow. In the figure, l is a secondary storage device, 2 is a file processing device, 3 is a main storage device, 4 is a document creation/correction processing device, 5 is a link setting/cancellation device, 6 is a history management processing device, and 7 is a A traverse processing device, 8 a document display/menu display processing device, 9 a terminal, and 10 a document file.

Claims (1)

[Claims] In a document processing system that stores a plurality of documents related by link information as document files and processes the documents, the document file (10
) is stored in the secondary storage device (1), a main storage device (3) into which the document file of the secondary storage device (1) is loaded, and a main storage device (3) into which the document file of the secondary storage device (1) is stored. Storage device (3)
A file processing device (2
), a document creation/modification processing device (4) that creates or updates a document on the main storage device (3), and a link to the document on the main storage device (3), or a link to the document. a link setting/cancellation device (5) for deleting the link; and a link setting/cancellation device (5) for deleting the
A history management processing device (6) that creates version information regarding the version of the document, a terminal (9) that performs input related to document processing or displays documents and menus, and the terminal (9) and the main storage device ( 3), a document display/menu display processing device (8) that performs control between the terminal (
a traverse processing device (7) that determines a traversal destination document when traversing from a display state related to one document displayed in 9) to a display state related to another document; The document file on the storage device (1) and the main storage device (3) is configured to hold link information indicating other documents linked to the document and version information of the document. The traverse processing device (7) processes the document file (
10) A document management processing method characterized by reading the link information and the version information above to determine the document to be traversed.