JPH06266591A - Document managing method - Google Patents

Abstract

PURPOSE:To realize a version management by a relational data base by performing document-management of plural tables having an indispensable field and an aribitrary field by relating the with each other. CONSTITUTION:The relational data base is used for a data base, and broadly classifying there are five tables A-E existed. The tables A-C are the indispensable tables, and the tables D and E are the arbitrary tables to be added as necessary. Then, the table A is the table for specifying a document or the kind of the document, and for example, in the case of the document of a document ID 'SK001', the kind of the document 'A', document name 'product A', and symbol 'HMBA' are correspondingly stored. Therefore, in the table A, the kind of the document or the like can be specified by specifying the document by the document ID.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of managing various documents having a plurality of pages, and more particularly to a document management method using a relational database of digitized documents.

[0002]

2. Description of the Related Art In recent years, companies, government agencies, etc., have strengthened document management such as company-wide sharing of documents and information and paperlessness of documents by digitizing business documents for the ever-growing information. Many attempts have been made. In particular, when one document is repeatedly changed and rewritten and changed, or when the document is used across multiple departments, it is desired to collectively manage and share the document. In addition, it has been earnestly desired that the information written in the document itself should be searched in various ways to retrieve the necessary information as needed.

Under such a demand, in the conventional systemization of documents, an existing document is directly read as image information using an optical file or the like, and information is managed by assigning a key for retrieval to each information, The search form was common.

[0004]

However, in the conventional method as described above, not only a very large storage capacity is required for storing a document, but it is also impossible to search the content of the document, There was a problem such as not being able to associate the contents of each other. Especially in the case of documents that describe technical contents such as standard documents and standard documents, the contents cannot be retrieved, so the conventional method cannot always be said to be an effective document management method.

On the other hand, in order to solve such a problem, the document is not taken in as image information, but the information may be divided into items so that they have a relationship with each other. Was also considered to use a database system with a relational structure. However, most general documents are aggregates of multiple pages, and if you make this a database,
Combined with the fact that one page is made up of multiple types of information, a common relational database that processes multiple documents, each of which has multiple types of information, has the structure. It was too complicated to implement. In addition, it has been extremely difficult to process these multiple versions in the case where the revisions and rewritings are performed and the relation between documents and pages and the issue of documents change from moment to moment. Also, in terms of confidentiality of information, a method that only a specific user can use a specific program, a method that allows only a specific terminal to use the database, and a database use qualification is specified by the user. Although a method of restricting by referring to the entry has been proposed, it was not possible to set the usage right in detail for each data unit.

The present invention solves the above-mentioned conventional problems and efficiently uses a relational database for various documents including a plurality of pages having a plurality of types of information and having several versions of the document. The purpose is to provide a method for document management.

[0007]

To achieve the above object, the present invention according to claim 1 provides a table storing document data and predetermined item data, and management processing means for managing the table. The table is composed of a relational database provided, and the table has a first mandatory field for storing item data specifying a document and an optional field for storing item data corresponding to the document. A required field for storing a table, item data for associating with the first table and a document version corresponding to the number of revisions of the document, and an optional field for storing item data corresponding to the document version.
A second table having a field, the item data for associating the second table with the second table, the document version and the logical page number indicating a specific portion collected as the document content, and the logical page number. A third table having a mandatory field for storing a page version indicating the number of revisions and an optional field for storing item data related to the logical page corresponding to the document version. The management processing means updates the contents of the document version, the page version and the logical page of the necessary tables among the first to third tables according to the creation and revision of the document as necessary. However, a new record relating to the document is created and added.

[0008]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a system configuration of a first embodiment according to the present invention, and FIGS. 2 to 12 are diagrams showing examples of respective tables of a database 1 used in document management according to the present invention. The present invention grasps one document for each document type as an aggregate of parts (hereinafter referred to as logical pages) that are collected as contents of product specifications, standards, handling rules, etc., and the document type and revision information , And the contents before and after revision are managed using a relational database. In this case, the system according to the present embodiment, as shown in FIG.
In addition to the above, it comprises a document designation means 2 as a document management means, a table of contents display means 3, a revision execution means 4, a command control 5, a display input means 6, and the like. In this embodiment, first, the table structure in the database 1 will be described.

A so-called relational database is used as the database 1 of this embodiment. Then, as shown in FIG. 2 to FIG.
There are five tables. Of these, tables A to C
Is an essential table in the present invention, and D and E are arbitrary tables added as needed. Also, FIG.
The symbols in the upper left of FIG. 12 are the names of each table, the first line is the name of the fields that make up the table, and the second and subsequent lines are 1
Each line represents one record, and the characters in each line indicate the data of each field and record. Note that the tables A, B, C, and D are common tables regardless of the document type, but the table E is, for example, E11.
1, E112 is the logical page S-01 of the document of document type A
, E211 is a table constituting the logical page K-01 of the document of the document type C, and the document type and the logical page corresponding to each table are predetermined.

First, the table A is, as shown in FIG.
This is a table for specifying a document and a document type. The mandatory field has a name or number (a1) that can specify the document, and the optional field has an item that can specify the document type and an item related to the document entity regardless of the page or the revised version. It is stored. In this embodiment, as shown in FIG. 2, a document ID, a document type, a document name, and a symbol are arranged in each field. On the other hand, each record stores the document type or the like corresponding to the document ID. That is, for example, for the document with the document ID “SK001”, as can be seen from FIG. 1, the document type “A”, the document name “Product A”, and the symbol “H”.
"MBA" is stored correspondingly. Therefore, in the table A, the document type and the like are specified by specifying the document by the document ID.

Next, the table B is as shown in FIG.
This is a table for storing the data related to the revised version (hereinafter referred to as the document version) when the document is partially updated as necessary (hereinafter referred to as the document revision) and the revised version is created. . Therefore, in this table B, as many records as the document versions are generated for the document specified by one record in the table A. In this table B, the required fields include a name or number (b1) for associating with the table A, and a document version (b2) generated every time the document is changed and revised. Will be distributed. As a result, in the table B, a document having a plurality of versions stored in a plurality of records is specified by its document number and document version. Further, in the arbitrary field, items related to the document version, for example, items such as the issue date, issue department, issuer, etc. are arranged regardless of the page. That is, taking FIG. 3 as an example, the document ID is specified as “SK001” and further specified as the document version “2”, so that the document name “Product A” is clarified by the table A. The revised version of document version 2 is "1991 10
Code "012454" in "Technology" on "March 2"
It can be seen that it was issued by someone.

On the other hand, the table C is updated in units of logical pages forming a document (hereinafter referred to as page revision),
When a revised version is created, it is a table for storing data relating to the revised version (hereinafter referred to as page version). Therefore, in this table C, as many records as the number of logical pages are generated for the document specified by one record in table B. In this table C, the required fields include the name or number (C1) for associating with the table B, the document version (C2), the page number or symbol (C3) for specifying the page, and A page version (C4) designating the version of each logical page is arranged. As a result, in the table C, the revision data for a document stored in a plurality of records is specified by the document number or the like. Further, in the arbitrary field, an item relating to the page of the document version, for example, information such as whether or not the page is revised in the revision up to the version is arranged. That is, taking FIG. 4 as an example, the document ID is specified as “SK001”,
Further, when the document version is specified as "2" and the logical page code is specified as "S-01", the "Product A" clarified by the tables A and B is described in "1991 10
Logical page “S-01” of the document revised on “March 2”
Indicates that the page version is "2" and that there has been a revision this time.

Further, in this embodiment, in addition to the above-mentioned tables A to C, tables D and E are provided. These tables D and E are arbitrary tables which are not necessarily required to carry out the method unlike the above tables A to C. Table D is the above-mentioned table A
Various data relating to revisions, etc., which could not be stored in C to C are stored. In the present embodiment, in particular, the one storing the revision date information is adopted, and this is shown in FIG. Show. In this embodiment, a name or number (d1) for associating with the table C, a logical page code (d3), and a page version (d4) are arranged as the indispensable fields. Then, in the arbitrary field, an item related to the page version, that is, a revision date in this embodiment is arranged. Therefore,
In the table D, for example, the document ID is “SK00
Regarding the logical page "S-01" of the document "1", the revision of the page version "2" is "October 2, 1991".
It will be understood that it was done in.

On the other hand, the table E stores specific data of various logical pages such as items such as "weight" and "substance name" for each page version of a certain document. Therefore, this table E is
One or more is required for each logical page. For example, even if the same document ID “SK001” is used, as shown in FIGS. 6 to 12, “weight”, “substance name”, “material”, etc. for each logical page. Will exist. In this table E,
In the required field, a name or number (en1) for associating with the table C, a page version, a page revision number, etc. (en2) are arranged. Further, in the arbitrary field, an item that is the substantial content of each logical page related to the page of the page version is arranged. That is, taking FIG. 6 as an example, the document ID “SK001”
Table E for page version "2" of
The weight and the like of the product is stored in 111, and in this case, it is "100", and it can be seen that the product is "for domestic use". When it is desired to obtain the substance name and weight, the substance names are “NaCl”, “HCl”, and “KOH” and the weights are “9 kg” and “0.5 cc” according to the table E112 shown in FIG. It can be seen that three types of substances, "," and "5 g," are used. Furthermore, FIG.
Regarding the apparatus to be used and the test method by using the table E211 shown in FIG. 5, the page revision number "2" of the document ID "SK020" uses "apparatus BC" and "developing solution B".
You will get the data that the test "1 ml of data ..." was performed using 100 ml of. As described above, the table E specifies and manages specific contents in each logical page by the document ID, page version, and the like. In addition, various data such as standard values and inspection information can be stored in this table E as shown in FIGS.

Next, the display of the table-of-contents information when searching for a document managed by this embodiment will be described. 13 and 14 are diagrams showing examples of display screens in that case. In this case, when the user first specifies the document name or the like using the document specifying means 2, the table A is searched from the database 1 and a list of the document names is displayed on the display / input means 6 by a user interface (not shown). )
Output above. Next, the user specifies a specific document from the displayed list. As a result, the document ID and the document version information of the designated document are passed to the index display means 3 via the command control means 5. Then, the table-of-contents display means 3 retrieves the table-of-contents data corresponding to the given document ID and document version from the tables A to D, and obtains the display screens such as the display screen examples shown in FIGS. 13 and 14. Become.

This will be specifically described with reference to the case shown in FIG. 13, for example. First, the user first operates the document designating means 2. This retrieves table A,
A list of document names such as the product A and the test method T is displayed on the screen. Next, the user selects and inputs the document name of the desired document data, for example, "Product A". At the same time, the document version of the document to be obtained, for example, "2" is input. As a result, the document ID and the document version of the product A are specified. By searching the table B, the issue date and the like are obtained, and by searching the tables C and D, the data such as the page code and the revision date are obtained. can get. A screen display of this is shown in FIG. Note that the portion surrounded by a frame in FIG. 13 is a value fetched from the data in the table, and other portions related to the screen configuration and the like are fixedly displayed by the program. The screen display example of FIG. 14 is also derived by the same method as in FIG.

Next, the case of displaying the contents of a logical page in this embodiment will be described. 15 to 18
Is an example of screen display in that case. in this case,
The user first specifies a specific page from the table of contents information as shown in FIGS. 13 and 14 output on the user interface. By this designation, the document ID of the document of the designated page, the page version, and the information of the logical page code are passed to the corresponding page display means 7 and the like via the command control means 5. Then, the page display means displays the document data corresponding to the given data in the tables A, C and E.
Search from n. As a result, the screen display as shown in FIG. 15 to FIG. 18 in which the data such as the composition and the packaging method, etc. is taken in is displayed.

Here, taking FIG. 15 as an example, when the user specifies the logical page S-01 from the table of contents screen as shown in FIG. 13, from the viewpoint of "composition", the page display means 7 of S-01 is displayed. In addition to Tables A and C, E11
1, E112 is searched, and in addition to the weight and domestic use, the substance name, its amount, unit, etc. are displayed. Similarly, in the screen display example of FIG. 16, tables A, C, and E12
1 by the page S-02 display means 8, and in FIG. 17, tables A, C, E221, and E222 are page K-.
The 02 display means 9 retrieves the tables A, C, E221, and E222 in FIG. 18 by the page K-02 display means 9 to obtain the display screen as shown in the figure.

On the other hand, in this embodiment, the revision of the document is executed as follows. 19 to 34 are diagrams showing the configuration of each table when the revision is performed once, and FIG.
42. FIG. 42 is a diagram showing the structure of each table when the revision is performed twice.

In this case, first, the document designating means 12 is used to retrieve the table A from the database 1, and a list of document names is output to the user interface using the display / input means 6. Next, the user specifies a specific document from the displayed list. As a result, the document ID and the document version information of the designated document are passed to the revision execution means 4 via the command roll means 5. Then, the revision executing means 4 sends a database rewriting command for revision corresponding to the given document ID and document version to D.
Issued to the BMS 10 to insert / update data.

Regarding the insertion / update of this data, the document version as the product A is currently 1 to 3, the document version as the test method T is 1, and the document version as the test method X is 1 or 2. Regarding the document, the configuration of each table will be described with reference to the drawings in the case of creating the document for the first time, once revised, and revised twice. First, when the document of the product A is created for the first time, as shown in FIG.
Then, a record in which the data corresponding to each field of the document ID, the document type, and the symbol is stored is created. Next, in table B, as shown in FIG. 20, "December 5, 1990" is set in each field of the document version ("1" when the document is first created), issue date, issue department, and issuer.
Create a record that stores data such as. Similarly, as shown in FIGS. 21 to 26, records relating to the products A are stored in each field while being associated with each other by the document ID, the document version, and the page version for the tables C to E.

Next, the case where this document is revised once will be described. In this revision, logical pages S-01 and S-03
Is changed, and the contents of S-02 are not changed. Therefore, the page version of the logical pages S-01 and S-03 becomes "2" by this revision, but the page version of S-02 remains "1".

That is, according to this revision, the table in which the document version and the page version are stored is revised as shown in FIG. Looking at this in detail,
First, in table A, since the versions are irrelevant, there is no change from that of FIG. 19 as shown in FIG. However, since the document is revised in the table B, the document ID "SK00" as shown in FIG.
The record of the document version (Ver) “2” is added to “1”. Further, in the table C, records for all logical pages corresponding to the document version “2” are added, and at that time, the contents of the pages S-01 and S- are changed.
For page 03, the next higher page version is attached and the data "2" is stored, and the revision F is displayed accordingly. In this case, S-
For page 02, the previous page version “1” is stored.

On the other hand, in the table D, in this embodiment, since the table D has the role of storing the changed data, only the record of the logical page corresponding to the changed page is shown in FIG. Is added. That is, the page version and the revision date data are stored only for pages S-01 and S-03. Further, in the table E, various changes are made depending on the stored data. That is, for example, there is no change in the table related to the data related to the logical page S-02, but the version "2" record is added to those related to the logical pages S-01 and S-03. Therefore, the table E11 shown in FIG. 31, FIG. 32, and FIG.
A new record is added for items such as 1, E112, E131, etc. that change due to changes in the document weight or page version, such as product weight, amount of constituent substances, standard values, and standard substances. To be done.

A case where the revision is performed again will be described. Also in this case, as in the previous case, the record of each table is added as the content is changed. In this revision, the logical pages S-01 and S-02 have been changed.
It is assumed that there is no change in 03. Therefore, after this revision, the page version of the logical page S-01 is "3",
S-02 is "2" and S-03 is "2".

Even in this revision, the table A is shown in FIG.
As shown in FIG. 5, there is no change from that of FIG. Further, as shown in FIG. 36, a record corresponding to the new version 3 is added to the table B as the document is revised. Further, in the table C, records for all logical pages corresponding to the document version 3 are created as shown in FIG. In this case, S-01 that changed the page,
For the S-02 page, the next higher page version is added, and "3" and "2" are stored respectively. In addition, the revision F is also displayed. For the S-03 page that has not been changed, the previous page version “2” is stored.

On the other hand, in the table D, as shown in FIG. 38, only the record of the logical page corresponding to the changed page is added at the same time as the case of the one-time revision.
Data is added only for page S-02. Also in the table E, as shown in FIGS. 39 to 42, as in the case of the one-time revision, for example, E111 and E11 shown in FIGS.
2, records are added to the table such as E121, and the unrelated table such as E131 shown in FIG. 42 does not change. In this revision, unlike the first revision, page S-02 was revised and S-03 was not revised, so unlike the previous example,
The E121 in FIG. 41 changes due to the record addition, and
There is no change in E131. As described above, according to the document management method of the present invention, of the logical pages forming the document, the content of only the page changed by the document revision is rewritten.

Next, a second embodiment according to the present invention will be described. This embodiment is the database 1 of the first embodiment.
The table has a structure in which a node number that has a plurality of the same logical pages is added as an essential field. 43 to 50 are diagrams showing the configuration of each table in the present embodiment (only the product A is described). At the time of the document version 1 of the present embodiment, it is assumed that the logical page has S-01, S-02 has one section, and S-03 has two sections.

In this embodiment, since the logical page has a plurality of clauses, the tables A and B are first.
Has the same configuration as that of the first embodiment as shown in FIGS. On the other hand, the table C is a logical page having a plurality of nodes as shown in FIG. 45, for example, S- in the present embodiment.
On page 03, there are a plurality of records with node numbers “1” and “2” corresponding to the increased required fields, which is different from the first embodiment. Note that FIG.
Indicates that the document has been revised twice. First, in document version “2”, section 1 of logical page S-01 and section 2 of S-03 are changed to page version “2”, and Section 2 is added to page S-01, and the other logical pages are revised without changing. Further, in the document version “3”, section 1 of the logical page S-01
Is changed to page version “3” and section 1 of S-02 and section 1 of S-03 are changed to page version “2”, and section 2 of S-01 and section 2 of S-03 are not changed. It is being revised. The revising method is the same as that of the first embodiment, and the description thereof is omitted.

The tables D and E are similar to the table C, and the node number is added as an essential field to the tables D and E as shown in FIGS. Therefore, in the table D, as shown in FIG. 46, in the page version "1", records of sections "1" and "2" exist for S-03. Also, in page version "2", S
A new record of section “2” is added for -01. On the other hand, also in the table E, the number of records increases as the section number increases. For example, according to FIG. 47, the page version configurations of the sections “1” and “2” are different even for the same logical page. Even if the page version has the same content and weight, there are 1
It can be seen that it is different from 10 ”and“ 120 ”. Similarly from other FIGS. 48 to 50, it can be seen that different data is stored due to the difference in the nodes.

Next, the display of the table of contents information in this embodiment will be described. Also in this embodiment, almost simultaneously with the first embodiment, the table A is searched from the database 1 using the document designating means 2 and the list of document names is output on the user interface using the display inputting means 6. Start from. Then, when the user designates a specific document from the list, the information of the document ID and the document version is displayed through the command control means 5 and the index display means 3
And the table-of-contents data corresponding to the document ID and the document version given to the table-of-contents display means 3 are stored in tables A to D
It is possible to obtain a display screen as shown in FIG.

With such a handling, for a specified version of a certain document, the item determined by the document of the document type such as the document name and the document symbol, the issue date, the issuing department, the issue regardless of the document type. It is possible to know the items determined by the document version and section of the person, and the configuration of the document such as page code and page version. That is, referring to FIG. 51, the document version “2” with the document name “Product A” is “October 2, 1991.
Is issued and the logical page S-03 with the section number “1” is the page version “1” created on “December 5, 1990”. You will understand.

On the other hand, the display of the logical page contents in this embodiment is performed as follows. That is, first, the user specifies a specific page including the section number from the table of contents information output on the user interface. As a result, the information of the document ID, page version, logical page code, and section number of the document of the designated page is passed to the display unit 7 of the corresponding page via the command control unit 5. And
The page display means 7 and the like retrieve the document data corresponding to the given document ID, page version, and section number from the tables A, C, and En, and display a screen as shown in FIG. FIG. 52 is a screen display example of the logical page S-01 of the document version 1 of the product A with the section number 1, and accordingly, the tables A, C, E111, and E1.
12 is searched, and the data on the weight and the substance name are displayed.

Further, a third embodiment according to the invention will be described. FIG. 53 is a block diagram showing the system configuration of the third embodiment. This embodiment has a configuration in which a document status check means 11 and a page status check means 12 are added to the configuration of FIG. Further, with respect to the database 1, the status items of the document and the page can be added to the field to manage the state of the document page in addition to that of the first embodiment. That is, in this embodiment, the information indicating whether or not the designated page of the designated document is in the issued status is acquired from the table D, and the change of the data of the table En is determined based on the information. Is to
Program the status of documents and pages so that the next revision can be executed only for the versions of documents that have been published, and that the contents of published pages cannot be changed. It made it possible.

In this embodiment, the document and page status information is stored in tables B and D as shown in FIGS. That is, the document status and page status are added to the tables B and D as indispensable fields, and the status such as "issued" or "in preparation" is stored therein for each record. Therefore, the status of the document or page can be easily obtained by searching the tables B and D. In this embodiment, the tables A, C and E are not related to the status, and therefore have the same configuration as the previous embodiment as shown in FIGS. 54 and 56.

Here, the management of document revision in this embodiment is performed as follows using the status information. That is, first, the table A is searched from the database 1 by using the document designating means 2, and a list of document names is output by the display / input means 6 on the user interface. Then, according to the user's document designation, the document ID and the document version information are passed to the document status check unit 11 via the command control unit 5. The document status check means 11 determines whether the status given from the table B is "issued". Then, the command is issued to the revision executing means 4 only when it is "issued". Revision execution means 4 receiving this command issues a database rewriting command for revision corresponding to the given document ID and document version to DBMS 10 to insert / update data, and document revision ends.

On the other hand, in the present embodiment, the page status information can be used so that the contents of the page being created cannot be displayed. In this case, the document ID of the document specified by the user, the page version,
Information on the logical page code is passed to the status check means 12 via the command control means 5. The status check means 12 determines whether or not the status given from the table D is "creating". Then, when it is "under creation", the page display means 7 is controlled so as not to be activated. When the status is "issued", the page display means 7 for each page retrieves document data corresponding to the given document ID and page version from the tables A, C, En and displays it on the screen. .

In addition, a fourth embodiment according to the present invention will be described. The present embodiment is a document management method capable of performing so-called security management in which specific documents, specific versions, and individual pages can be freely restricted. FIG. 58 is a block diagram showing the system configuration of this embodiment. In the present embodiment, the database 1 and the display input means 6 and the like are formed almost in the same manner as the other embodiments. However, in the present embodiment, in particular, the confidentiality check means 21 to 23 are provided. It is different from the one. Here, the first aspect of the table configuration is shown in FIGS. In the present mode example, the table S is newly added as an essential table in addition to the tables A to E of the other embodiments, and the table S performs security management for restricting use depending on the type of document.

In this case, the table A is similar to that of the other embodiments, but in this embodiment, the table A is as shown in FIG.
Of these, the document type item is a required item in the field. Then, the correspondence between the symbol of the document type stored therein and the attribute of the user is stored in the table S shown in FIG.
In this table S, the user's attribute is assumed to be the user's ID number. For example, for the document type “A”, the user's ID numbers “001”, “002”, “00”.
3 "and" 004 "correspond. Therefore, if the user requests to display a document of document type "A",
The confidentiality check unit 21 called from the command control unit 5 checks the ID number and document type of the user using the table S, and issues a display command to the document designation unit 2 only when the ID number is applicable. . Therefore, only the person with a specific ID number can use this system.

Next, another embodiment of this embodiment will be described with reference to FIGS.
3 shows. In this embodiment, as shown in FIG. 61, a confidential type field is added as an indispensable item to the database B, and usage restriction is applied to each document and its version. Further, in this example, as shown in FIG.
2, a table T that defines the correspondence between confidential type symbols and department names stored therein, and a table U that defines the correspondence between user ID numbers and department names, as shown in FIG.
Is added as an essential table. In the case of this example,
The confidentiality check means called from the command control means 5 retrieves the tables T and U and extracts the corresponding department name from the confidentiality type and the user ID number. Then, it is determined whether or not there is a match in the department name obtained from each of the records in each table,
The index display means 3 is called only when there is a match.

That is, as shown in FIGS. 61 to 63, for example, for the document version “1” of the document ID “SK001”, since the confidential type is “A”, “Production” from the table T, Only the "packaging", "research", and "sales" departments can use it. Then, the user ID number indicated by the user is confirmed by the table U. For example, when the ID number is "001", the corresponding department name is "research", which is consistent with the data obtained from the table T.
Confirms the match and calls the index display means 3. As a result, a person without rights cannot specify a document or version that he / she does not have the right to use, and cannot see the contents of the table of contents.

A further aspect of this embodiment will be described with reference to FIGS.
It shows in FIG. In the present example, as shown in FIG. 64, a field of confidential type is added to the database D as an essential item, and usage limitation is applied to each page of each document. Further, in this example, as shown in FIG.
5, a table T defining correspondence between confidential type symbols and department names and a table U defining correspondence between user ID numbers and department names are added as essential tables.

In the case of this example, the user designates a specific page from the table of contents displayed by the table of contents display means 3 through a process of displaying a list of document names and the like. According to the designation by the user, each data of the document ID, the page version, and the logical page code of the designated page is passed to the confidentiality check means 23 via the command control means 5. The confidentiality check unit 23 searches the tables T and U, and determines whether or not there is a record in which the obtained departments match each other, similarly to the above, based on the confidentiality type and the user ID number. Then, the page display means 7 or the like is called only when there is a matching record. As a result, the page without the right to use cannot be specified to the person without the right, and the content cannot be viewed.

[0044]

According to the document management method of the present invention, the relational database is provided with a plurality of tables each having a required field and an optional field, and these tables are associated with each other to manage the document. Thus, there is an effect that page management of various documents having a plurality of pages and version management corresponding to the revision can be realized by a relational database. Therefore, even different types of documents can be handled in common on one system, and the documents specified by the search, the document version table of contents information, and the content information of the logical page can be obtained collectively. Even if a document is revised, its status can be easily grasped, and it is not necessary to have duplicate page data that is unchanged.

Further, according to the present invention of claim 2, by providing an indispensable field for storing a section number for designating a plurality of the same logical pages, a document having a plurality of logical pages of the same kind although different in content is provided. The effect is that you can manage all of them, including version management.

Further, according to the present invention of claim 3, by providing an indispensable field for storing the document status symbol indicating the state of the document, the status of the document or page is managed (being created, issued, etc.). be able to.

In addition, according to the present invention of claim 4, by providing an indispensable table for defining the document type and the confidential type corresponding to the user's ID number, the specific document, version and page can be specified. The effect is that the right to use them can be specified freely.

[Brief description of drawings]

FIG. 1 is a block diagram showing a system configuration of a first embodiment according to the present invention.

FIG. 2 is a diagram showing a configuration of a table A used in the first embodiment according to the present invention.

FIG. 3 is a diagram showing a configuration of a table B used in the first embodiment according to the present invention.

FIG. 4 is a diagram showing a configuration of a table C used in the first embodiment according to the present invention.

FIG. 5 is a diagram showing a configuration of a table D used in the first embodiment according to the present invention.

FIG. 6 is a diagram showing one configuration of a table E used in the first embodiment according to the present invention.

FIG. 7 is a diagram showing one configuration of a table E used in the first embodiment according to the present invention.

FIG. 8 is a diagram showing the configuration of one of tables E used in the first embodiment according to the present invention.

FIG. 9 is a diagram showing the configuration of one of tables E used in the first embodiment according to the present invention.

FIG. 10 is a diagram showing one configuration of a table E used in the first embodiment according to the present invention.

FIG. 11 is a diagram showing one configuration of a table E used in the first example according to the present invention.

FIG. 12 is a diagram showing one configuration of a table E used in the first example according to the present invention.

FIG. 13 is a diagram showing a screen display example of table-of-contents information related to a document of document version 2 for product A according to the first embodiment of the present invention.

FIG. 14 is a diagram showing an example of a screen display of table-of-contents information relating to a document of document version 2 for test method X according to the first example of the present invention.

FIG. 15 is a diagram showing a screen display example of a logical page S-01 of document version 1 for product A of the first embodiment according to the present invention.

FIG. 16 is a diagram showing a screen display example of a logical page S-02 of document version 2 for product A according to the first embodiment of the present invention.

FIG. 17 is a diagram showing a screen display example of a logical page K-02 of document version 1 regarding the test method X according to the first embodiment of the present invention.

FIG. 18 is a diagram showing a screen display example of a logical page K-02 of document version 2 for the test method X according to the first example of the present invention.

FIG. 19 is a diagram showing a configuration of a table A when a document of a product A is created for the first time according to the first embodiment of this invention.

FIG. 20 is a diagram showing a configuration of a table B when a document of the product A is created for the first time according to the first embodiment of this invention.

FIG. 21 is a diagram showing a configuration of a table C when the document of the product A is created for the first time according to the first embodiment of this invention.

FIG. 22 is a diagram showing a configuration of a table D when a document of a product A is created for the first time according to the first embodiment of this invention.

FIG. 23 is a diagram showing the configuration of one of the tables E when the document of the product A is created for the first time according to the first embodiment of the present invention.

FIG. 24 is a diagram showing the configuration of one of the tables E in the case where the document of the product A is created for the first time according to the first embodiment of the present invention.

FIG. 25 is a diagram showing the configuration of one of the tables E in the case where the document of the product A is created for the first time according to the first embodiment of the present invention.

FIG. 26 is a diagram showing the configuration of one of the tables E in the case where the document of the product A is created for the first time according to the first embodiment of the present invention.

FIG. 27 is a diagram showing a configuration of a table A when the revision of the first embodiment according to the present invention is performed once.

FIG. 28 is a diagram showing a configuration of a table B when the revision of the first example according to the present invention is performed once.

FIG. 29 is a diagram showing a configuration of a table C when the first embodiment according to the present invention is revised once.

FIG. 30 is a diagram showing a configuration of a table D when the first embodiment of the present invention is revised once.

FIG. 31 is a diagram showing the configuration of one of the tables E when the first embodiment of the present invention is revised once.

FIG. 32 is a diagram showing the configuration of one of the tables E in the case where the revision of the first example according to the present invention is performed once.

FIG. 33 is a diagram showing the configuration of one of the tables E when the first embodiment of the present invention is revised once.

FIG. 34 is a diagram showing the configuration of one of tables E in the case where the revision of the first example according to the present invention is performed once.

FIG. 35 is a diagram showing a configuration of a table A when the revision of the first embodiment according to the present invention is performed twice.

FIG. 36 is a diagram showing a configuration of a table B when the first embodiment according to the present invention is revised twice.

FIG. 37 is a diagram showing a configuration of a table C when the revision of the first example according to the present invention is performed twice.

FIG. 38 is a diagram showing a configuration of a table D when the first embodiment according to the present invention is revised twice.

FIG. 39 is a diagram showing the configuration of one of tables E when the first embodiment of the present invention is revised twice.

FIG. 40 is a diagram showing the configuration of one of the tables E in the case where the revision of the first example according to the present invention is performed twice.

FIG. 41 is a diagram showing the configuration of one of tables E when the first embodiment of the present invention is revised twice.

FIG. 42 is a diagram showing the configuration of one of the tables E when the first embodiment according to the present invention is revised twice.

FIG. 43 is a diagram showing a configuration of a table A used in the second example according to the present invention.

FIG. 44 is a diagram showing a configuration of a table B used in the second example according to the present invention.

FIG. 45 is a diagram showing the structure of a table C used in the second example of the present invention.

FIG. 46 is a diagram showing the structure of a table D used in the second embodiment of the present invention.

FIG. 47 is a diagram showing one configuration of a table E used in the second example according to the present invention.

FIG. 48 is a diagram showing the configuration of one of the tables E used in the second example of the present invention.

FIG. 49 is a diagram showing one configuration of a table E used in the second example according to the present invention.

FIG. 50 is a diagram showing one configuration of a table E used in the second example according to the present invention.

[Fig. 51] Fig. 51 is a diagram showing a screen display example of the table-of-contents information related to the document of document version 2 for the product A according to the second embodiment of the invention.

FIG. 52 is a diagram showing a screen display example of logical page S-01 section number 1 of document version 1 for product A of the second example according to the present invention.

FIG. 53 is a block diagram showing a system configuration of a third example according to the present invention.

FIG. 54 is a diagram showing the structure of a table A used in the third embodiment of the present invention.

FIG. 55 is a diagram showing the structure of a table B used in the third embodiment of the present invention.

FIG. 56 is a diagram showing the structure of a table C used in the third example of the present invention.

FIG. 57 is a diagram showing the structure of a table D used in the third embodiment of the present invention.

FIG. 58 is a block diagram showing a system configuration of a fourth example according to the present invention.

FIG. 59 is a diagram showing a configuration of a table A used in the first mode of the fourth example according to the present invention.

FIG. 60 is a diagram showing the structure of a table S used in the first mode of the fourth example of the present invention.

FIG. 61 is a diagram showing the structure of a table B used in the second mode of the fourth example according to the present invention.

FIG. 62 is a diagram showing the structure of a table T used in the second mode of the fourth example of the present invention.

FIG. 63 is a diagram showing the structure of a table U used in the second mode of the fourth example of the present invention.

FIG. 64 is a diagram showing the structure of a table D used in the third mode of the fourth example according to the present invention.

FIG. 65 is a diagram showing the structure of a table T used in the third mode of the fourth example according to the present invention.

FIG. 66 is a diagram showing the structure of a table U used in the third mode of the fourth example of the present invention.

[Explanation of symbols]

 1 database 2 document designation means 3 table of contents display means 4 revision execution means 5 command control means 6 display input means 7 page S-01 display means 10 DBMS 11 document status check means 12 page data status check Means 21 Confidence Check Means 22 Confidence Check Means 23 Confidence Check Means

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Akito Kobayashi 1705-6 Miyagawa, Hikari-cho, Sago-gun, Chiba Prefecture

Claims (7)

[Claims] 1. A relational database comprising a table storing document data and predetermined item data, and a management processing means for managing the table, wherein the table stores item data specifying a document. A first table comprising a mandatory field to be stored and an optional field to store item data corresponding to the document, and item data to be associated with the first table and the number of revisions of the document. A second table having an essential field storing the corresponding document version and an optional field storing the item data corresponding to the document version, and the association with the second table. Item data to be performed, the above-mentioned document version, and the number of the logical page indicating a specific part that is collected as the document content and the revision of the logical page A mandatory field that stores the page version that indicates the number of times
Field, and a third table having an optional field for storing item data related to the logical page corresponding to the document version. The management processing means responds to the creation and revision of the document. , For the necessary tables among the first to third tables, the contents in the document version, the page version and the logical page are updated as necessary, and a new record for the document is created. A document management method characterized by being added. 2. An indispensable field for storing item data for associating with the third table, the logical page number and the page version, and item data for a logical page corresponding to the page version. Corresponding to the above-mentioned page version, and a fourth table having an optional field, an indispensable field for storing the item data for associating with the third or fourth table, and the page version, respectively. A fifth table comprising an optional field for storing document data of a logical page, and the management processing means stores the first to fifth tables in accordance with creation and revision of the document. Of the necessary tables, update the above document version, page version, and contents in the logical page as needed. New record according to the document - creating de, document management method according to claim 1, characterized by being added. 3. The essential field of the third table further stores item data for specifying one of a plurality of logical pages of the same type. Document management method. 4. The indispensable fields of the third to fifth tables further store item data for identifying one of a plurality of logical pages of the same type. Document management method described in. 5. The document management method according to claim 1, wherein item data indicating a processing status of a document to be stored is further stored in an essential field of the second table. 6. The essential field of the second table further stores item data indicating the processing status of the document to be stored, and the logical page to be stored in the essential field of the fourth table. 3. The document management method according to claim 2, wherein item data indicating a processing status of is stored. 7. An item field for specifying a document type or a confidential type of the document is stored in an essential field of the first table, the second table or the fourth table, and is used together with the item data. 7. The document management according to claim 1, further comprising another table that defines a relationship with a user's attribute, and limiting use of a document or a document version or a logical page according to the user's attribute. Method.