JP2002183182A - Document diversion method, decision-making support system and document management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system which can easily divert a document from the other job and can easily be associated with the other system such as a data warehouse. SOLUTION: The system is provided with a relational database for storing a plurality of document elements constituting a plurality of documents to be made correspond to each other in a plurality of tables, a client terminal 12 performing an operation for calling the document from the relational database and an HTTP server 13 which is installed between the relational database and the client terminal 12, extracts at least one element in the documents with respect to the relational database based on an operation command from the client terminal 12, and composites the extracted data to generate the new document.

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, a document diversion method, and a decision support system suitable for managing a large-volume document of several tens to several hundreds of pages composed of text data and graphic data. About.

[0002]

2. Description of the Related Art A conventional document management system of this type manages a large number of documents as tables of an RDB (relational database).

Such a conventional system manages a small-capacity document of about one page such as a form using a table, and targets a large-capacity document of several tens to several hundreds of pages composed of text data and graphic data. It wasn't.

[0004] Accordingly, large-volume documents such as design documents and issued documents created by specific word processing software widely used at present are managed by the above-described system. For example, the documents are diverted to other work. In this case, specific application software is required, and it may be difficult to cooperate with another system such as a data warehouse.

[0005]

SUMMARY OF THE INVENTION It is an object of the present invention to manage large-volume documents which can be easily diverted from other tasks and which can easily cooperate with other systems such as a data warehouse. It is to provide a suitable document management system.

[0006]

In order to achieve the above object, according to the first aspect of the present invention, a document is diverted using a document management system in which the document is stored and managed in a relational database. A management table for managing attribute information in the method;
Storing a document in the relational database as a configuration including a definition table for defining a data structure and a data table for storing data defined by the definition table; and diverting the document stored in the relational database. At the stage of prompting you for the required document search criteria,
Performing a search in accordance with the entered search conditions and displaying the results, prompting the selection of the diverted source document, and updating the information in the management table of the selected diverted source document to create the diverted destination document Correcting the row by correcting the data stored in the definition table of the diverted document, and correcting the description content by correcting the data stored in the data table of the diverted document And a document diversion method comprising the steps of:

According to another aspect of the present invention, there is provided an image processing apparatus comprising: a management table for managing attribute information; a definition table for defining a data structure; and data for storing data defined by the definition table. A relational database stored as a configuration having a table, and a data warehouse that extracts data from the relational database, performs aggregation / analysis processing, and displays the result. Decision support system.

According to a third aspect of the present invention, there is provided a relational database which stores a plurality of documents in association with a plurality of tables and a plurality of document elements constituting each of the documents. A client terminal that performs an operation for calling the document from the relational database, interposed between the relational database and the client terminal, and the relational database based on an operation command of the client terminal. And a server that extracts at least one element in the document and combines the extracted data to generate a new document.

According to a fourth aspect of the present invention, there is provided means for totalizing numerical data in the plurality of documents stored in the relational database according to the third aspect, and performing at least one of analysis and processing of the totaled data. Is further provided.

According to the present invention, by managing a plurality of document elements constituting a document by each of a plurality of tables of a relational database,
Regardless of the specific application, it is easy to divert documents from other tasks, and because the documents are also converted to a relational database, it is easy to summarize numerical items in the documents, and it is easy to link with other systems such as data warehouses Cooperation becomes easy.

[0011]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, a first embodiment of a document management system according to the present invention will be described with reference to the drawings.

FIG. 1 shows a document management system according to the present embodiment. The system includes a diversion source relational database (diversion source RD) having a diversion source table.
B) 11, the client terminal 12, and the HTTP (Hype
rtext Transfer Protocol) server 13, an application server 14, and a diversion destination relational database (diversion destination RDB) 15 having a diversion destination table.

The relational database 11 stores a plurality of documents. This document includes a large document of several tens to several hundreds of pages, such as a design document or a published document created by specific word processing software or table creation software.

In the present embodiment, the following method is used to store the above-described documents in the relational database 11. That is, each document is decomposed into a plurality of document elements constituting the documents, and each of the plurality of document elements is stored in association with a table.

The client terminal 12 gives an instruction to the relational database 11 for calling a document or the like. The client terminal 12 serves as an application for screen browsing or the like, for example, WWW (WWW).
or Old Wide Web) browser, and the browser allows the document to be diverted as desired by the operator.
A, a document diversion destination screen 12B can be displayed.

The HTTP server 13 is interposed between the relational database 11 and the client terminal 12, extracts at least one document element in the document from the relational database 11 based on an operation command of the client terminal 12, and extracts the document element. A new document is generated by synthesizing data.

The application server 14 is a server for executing an application for document processing performed by the document management system of the present embodiment. For example, as described later, the application server 14 extracts necessary data from a document, Are tabulated according to the purpose, and processing such as graphing and displaying the tabulated data is performed.

Under such a configuration, the user operates the PC client terminal 12 to operate the WWW browser screen 12.
A or 12B is displayed. Application server 14
Is an H that exchanges data between the WWW browser in the PC client terminal 12 and the application server 14.
Divert source RDB 11 based on conditions obtained from TTP server 13
And returns the result to the HTTP server 13. Next, the user selects a diversion source document from the list of the diversion source RDB 11, and presses a document diversion button of the PC client terminal 12. Next, each table of the source document is copied to each table of the destination RDB 15.

Next, as a document management method in the document management apparatus according to this embodiment, RDB has already been used.
An example will be described in which a large-capacity document registered in is used for another business. FIG. 2 shows a layout example of the table 30 in the diversion source RDB 11.

As shown in FIG. 2, the table 30 includes, as records, a "document management table" 31, a "heading management table" 32, and a "data table (character)" 3.
3, a "data table (numerical value)" 34, a "data table (date)" 35, and a "data table (image)" 36.

The items of the "document management table" 31 are "document number" 37 and "revision number".
38, “document name” 39, and “status” 40
, “Creator affiliation” 41, “creator name” 42, and “system date” 43.

The "document management table" 31 is 1
Created as one document record. here,
“Document No.” 37 and “Revision No.” 38 are primary keys. "Document Name" 39
Represents the name of the document. "Status" 40
Indicates the status of the document, that is, editing or creation completed. “Author affiliation” 41 indicates the affiliation of the person who created the document. The “creator name” 42 indicates the name of the document creator. The “system date” 43 indicates the date when the document was created.

Further, the items of the “heading management table” 32 include “document number” 44 and “revision number” 45
, “Record No.” 46, “Heading Level” 47,
It is composed of a “serial number within a level” 48, a “heading name” 49, a “parent heading record number” 50, a “data code” 51, and a “data number” 52. Here, the “heading management table” 32 is a table in which a plurality of records are created for one document, and is a table that defines the data structure of the document.

In the “heading management table” 32, “document number” 44 and “revision number” 45 are external keys that refer to the “heading management table” 32. “Document No.” 44 and “Revision No. 4”
5 and “Record No.” 46 are primary keys of the “heading management table” 32. Further, the “heading level” 47 indicates a heading hierarchy. The highest level (chapter) is “1”, the next level (section) is “2”, and each time the level goes down, it increases by 1. The “intra-level serial number” 48 indicates the display order in the headline. . The “heading name” 49 indicates the name of the heading. The “parent heading record number” 50 indicates the heading record number of the parent hierarchy. If there is no parent hierarchy, a NULL value is stored. For example, as the parent heading record number in section 1-3-2, the record number of the heading in section 1-3 is stored. The “data code” 51 stores the data type (character, numerical value, date, image) of the data to be actually stored. “Data NO” 52 is a pointer to a table in which actual data is stored—a data table. If there is no data, a NULL value is stored.

The item names of the "data table (character)" 33 are "document number" 53, "revision number" 5
4, "Data No." 55, "Data Serial Number" 56, and "Data Content" 57. This "data table (character)" 33
Is a table stored when the data is characters.

The "data table (numerical value)" 34, the "data table (date)" 35 and the "data table (image)" 36
Have the same item names as the “data table (character)” 33. "Data table (numerical value)" 33
This is a table that is stored when data is a numerical value.

In the "data table (character)" 33,
The “document number” 53, the “revision number” 54, and the “data number” 55 are external keys that refer to the “data table (character)” 33.

"Document No." 53, "Revision No." 54, "Data No." 55, and "Data Serial Number" 56
Are the primary keys of the "data table (character)" 33. The “data serial number” 56 stores the row number of the table when the data is in a table format. If not in table format, zero is stored. “Data content” 57 indicates a value of data.

The "data table (numerical value)" 34 is a table stored when the data is a numerical value, and the "data table (date)" 35 is a table stored when the data is a date. , "Data table (image)" 36 is a table stored when the data is image data such as a figure or a photograph.

FIG. 3 shows a data structure diagram of the RDB, which illustrates the relationship between the tables in FIG. 2. The "document management table" 31 is located in the upper layer, and the "heading management table" is located in the middle layer. 32, and “data table (character)” 33, “data table (numerical value)” 34, “data table (date)” 35, and “data table (image)” 3
6 is constituted.

FIG. 4 shows the diversion source RDB 11 shown in FIG.
1 shows an example of the original document 100 to be stored in the document. The original document 100 shown in FIG. 4 includes a “document management table” 31, a “heading management table” 32,
“Data table (character)” 33, “Data table
(Numerical value) "34," data table (date) "35, and" data table (image) "36. An example of a table in the case of storing is shown in FIG. Each data of the document 100 shown in FIG. 6 has a “document management table” 31, a “heading management table” 32, a “data table (character)” 33 in the lower layer, and a “data table” in accordance with the arrangement condition shown in FIG. (Numerical value) ”34,“ data table (date) ”35 and“ data table (image) ”36.

Here, a specific example of document editing will be described. The diversion source screen 12A is displayed on the PC client terminal 12 by a user operation. At the time of this display, a search condition of a document to be diverted is input (step S
1) Press the search button (step S2). As a result, a list of applicable documents is displayed (step S
3). Select the document to be diverted (Step S
4). Next, the document number, document name, revision number, creator affiliation, and creator name of the diverted destination are input (step S5), and a document diverting button is pressed (step S6), whereby a diverted source document is obtained.

Next, an example of copying the specific record of the diverted source document to the specific record of the diverted destination document will be described with reference to FIGS.

The diversion source record 101 shown in FIG. 7 is copied to the diversion destination record 102. Here, only the contents of the items of the document management table 31 in the diverted document are replaced with the contents of the items of the same document management table 31 in the diverted document, and the other tables in the diverted document are the same as the diverted document.

The edited destination document thus edited is shown as a document edit screen 103 in FIG. Since the diverted data is displayed on this screen 103, the user can edit necessary parts.

As described above, in the present embodiment, even if a special application is not used, a general application such as a WWW browser mounted on the PC client terminal 12 can be used to store records, items, and the like constituting a document. For each element, it is possible to divert from one document to another document.

Further, in the present embodiment, by adopting a data structure in which the above-mentioned document is divided into elements such as records, it is possible to add / modify / add to the document items.
If there is a deletion, the change can be made easier than before.

For example, in the conventional data structure in which the columns and the format of the table are determined according to the data items, additional processing such as adding a section to a certain chapter occurs as an addition of the data items. In that case, adding a column to the table requires a change in the table structure. Similarly, since the table structure changes, data migration occurs. In other words, a complicated processing operation of creating a new table with added columns, copying data from the old table to the new table, and renaming the new table is required.

On the other hand, in the present embodiment, since a general-purpose data structure is provided, it is not necessary to change the data structure for adding a data item. In other words, the addition of data items only requires the correction and addition of data (rows) in the heading management table, so that there is no need to change the table structure. Also,
Since data migration does not change the table structure, only the operation of copying old rows to new rows is required, and the work of creating, copying, and renaming tables is not required.

(Second Embodiment) In the second embodiment, the RDB
This is an example of linking an RDB and a data warehouse system in order to analyze numerical data registered in the RDB and analyze the data using a graph creation tool, and to support manager / manager decision-making.

FIG. 10 shows a conceptual diagram of the cooperation between the RDB 200 and the data warehouse 20. The data warehouse 20 extracts the data of the RDB 200, totals the data according to the purpose in the calculation unit 201, and displays the data in a graph on the monitor unit 202.

In FIG. 10, at step T1, RD
The necessary data is extracted from B200 so as to be easily tabulated. Step T2 shows an example of the extraction source data, which is stored in the data warehouse 20. In step T3, in the data warehouse 20,
The data extracted by the calculation unit 201 is totalized according to the purpose, and total data shown in step T4 is obtained.

In step T5, data is analyzed by the monitor unit 202 having a graph creation tool, and the aggregated data is processed by the graph creation tool so as to be easily analyzed, and a graph as shown in step T6 is displayed. I do.

Here, an example of data display in FIGS. 112 to 13 will be described. This is an example of analysis by slice & dice which is a data warehouse analysis method.
The RDB to be analyzed is the table shown in FIG.

FIG. 11 shows the result of analysis by slice & dice. This is the result of comparing and analyzing the actual productivity by department in the first half of 1999. The section-specific actual productivity is a value obtained by dividing the actual number of steps by the actual man-hours and summing up the average for each section. (A) shows the productivity by sector in the first half of 1999. (B) represents a value obtained by totaling the productivity of each section in the first half of 1999 for those whose actual number of development steps is less than 100 ks. By comparing (a) and (b), it can be seen that the overall productivity is highest in the third part of the system development, but that of the small-scale property is the highest in the first part of the system development.

FIG. 12 shows how to obtain the actual productivity for each department. Step U1 represents creation of extraction source data. From the document management table, heading management table, and data table (numerical value), the status is “1” (completed) and the creation date is September 01, 1999 to March 31, 2000.
The date data is combined to create the extraction source data in step U2. Step U3 represents creation of total data. From the extraction source data in step U2, the average actual productivity ((actual step number / actual man-hour) / record number per set) is determined for each department, and the total data in step U4 is created. When the tabulated data of step U4 is graphed, the result is as shown in step U5.

FIG. 13 shows the actual productivity by section (small-scale property).
Here's how to find it. Step V1 represents creation of extraction source data. The status is '1' from the document management table, heading management table, and data table (numerical value)
(Completed) and the creation date is from September 01, 1999 to 200
Combine the data of the questions on March 31, 009, and go to Step V2
Create extraction source data for

Step V3 represents the creation of total data. From the extraction source data in step V2, for a small-scale property (the number of development steps is less than 100ks), the average actual productivity ((actual steps / actual man-hours) / number of records per division) is calculated for each department, and tabulated in step V4 Create data. If the total data of step V4 is graphed, it becomes like step V5.

As described above, it is possible to assist the manager or the manager in making a decision by totalizing the document data and analyzing the data from various aspects.

[0050]

As described above, according to the present invention, a plurality of document elements constituting a document are managed by each of a plurality of tables in a relational database.
Documents can be easily diverted from other tasks, and the documents can be converted into a relational database, which makes it easier to summarize numerical items in documents and facilitates linkage with other systems such as data warehouses. It is possible to provide a possible document management system.

[Brief description of the drawings]

FIG. 1 is an exemplary view showing a document management system according to a first embodiment of the present invention in connection with document diversion.

FIG. 2 is a diagram showing an RDB table layout according to the first embodiment of the present invention.

FIG. 3 is a data structure diagram of an RDB according to the first embodiment of the present invention.

FIG. 4 is a view showing an example of an original document according to the first embodiment of the present invention.

FIG. 5 is a diagram showing contents of a table in FIG. 4 according to the first embodiment of the present invention.

FIG. 6 is a view showing a document diversion screen according to the first embodiment of the present invention.

FIG. 7 is a diagram showing a diversion source record to be copied according to the first embodiment of the present invention.

FIG. 8 is a view showing a copied diversion destination record according to the first embodiment of the present invention.

FIG. 9 is a diagram showing an example of document diversion according to the first embodiment of the present invention, showing a document editing screen.

FIG. 10 is a view showing the concept of data warehouse cooperation according to the second embodiment of the present invention.

FIG. 11 is a view showing an example of a slice & dice according to a second embodiment of the present invention.

FIG. 12 is a view showing a method for obtaining the actual productivity of each section of slice and dice according to the second embodiment of the present invention.

FIG. 13 is a view showing a method of obtaining the actual productivity of each section of slice and dice according to the second embodiment of the present invention.

[Explanation of symbols]

 11 diversion source RDB 12 PC client terminal 13 HTTP server 14 application server 15 diversion destination RDB

Claims (4)

[Claims] 1. A method for diverting a document using a document management system in which a document is stored and managed in a relational database, wherein a management table for managing attribute information and a definition table for defining a data structure Storing a document in the relational database as a configuration including a data table for storing data defined by the definition table; and, in diverting the document stored in the relational database, a Prompting the input of search conditions, performing a search according to the input search conditions and displaying the results, prompting the selection of the diversion source document, and updating the information in the management table of the selected diversion source document To create a repurposed document And correcting the row by correcting the data stored in the definition table of the diverted document, and correcting the description by correcting the data stored in the data table of the diverted document. Performing the document diversion. 2. A management table for managing attribute information, a definition table for defining a data structure,
A relational database stored as a configuration including a data table that stores data defined by a definition table, and data that extracts data from the relational database, performs aggregation / analysis processing, and displays the results. A decision support system comprising a warehouse. 3. A relational database in which a plurality of documents are stored in association with a plurality of tables with a plurality of document elements constituting each of the documents, and an operation for calling up the documents from the relational database. A client terminal that performs at least one element in the document, which is interposed between the relational database and the client terminal, and extracts the at least one element in the document from the relational database based on an operation command from the client terminal. A document management system, comprising: a server that combines data to generate a new document. 4. The apparatus according to claim 1, further comprising: means for totalizing numerical data in said plurality of documents stored in said relational database, and performing at least one of analysis and processing of said total data. 3. The document management system according to item 3.