JPH1031668A - Meeting record managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a user managing system for disabling the change of a non-authorized section in the document data of one cell concerning a document processing system for preparing, registering and managing a document in the system format of a database (such as RDB) for managing information in the format of table. SOLUTION: Each cell is composed of a code containing authority information and document data. A password inputted in advance is compared with the authority information of the code and the presence/absence of authority is decided (S3503 and S3506). Concerning the non-authorized section, the relevant section is compared before and after editing so that the rightness of edited contents can be judged (S3509). Corresponding to the presence/absence of authority and the discriminated result of rightness in contents, the update of the data base is controlled.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document processing system for creating, registering, and managing a document in a text format in a database (RDB, etc.) for managing information in a tabular format. The present invention relates to a user management method for judging the presence / absence and correctness of contents and controlling updating to a database.

[0002]

2. Description of the Related Art Conventionally, a method of allocating a file for each user, judging the correctness of the contents and the presence or absence of authority for each file, and controlling the execution of processing is disclosed in Japanese Patent Application Laid-Open No.
No., published in Japanese Unexamined Patent Publication No.

[0003]

In a database handling a large number of records, when a plurality of users create, register, or change a document in each record, as a first method, a document cell is created for each user. A method of managing the assignment authority can be considered. However, in this method, when the number of users to be used differs for each record, it is necessary to estimate the number of users to be used in advance and create a cell in the database. Then, when the number of users exceeds the estimate, an operation of adding a cell to the database occurs. In addition, since a plurality of document cells can be provided, a separate management system is required in a case where unified management of documents is desired, such as arranging documents created by the user by date, for example.

[0004] As a second method, a user creates a document.
It is also conceivable to unify the cells to be registered / changed into one and manage the authorized and non-authorized parts in the cell. In this method, authority can be managed regardless of the number of users until the maximum number of characters that can be written in the cell is reached. In addition, since there is only one cell for documents, uniform management is possible as documents.

[0005] In the prior art, an RDB managed in a table format is used.
In such a DB, since the document data can be read only in units of cells, the presence or absence of authority and the correctness of the contents can be determined only in individual cells. Therefore, there is a problem that it is not possible to determine an authorized part and a non-authorized part in a cell as in the second method.

[0006]

According to the present invention, there is provided a document processing system for creating, registering, and managing a document in a text format in a database (RDB or the like) for managing information in a table format. The structure of the document data of each cell of the database is assumed to be a code including one or more pieces of authority information and original data of the document. Then, the user is required to input a password before editing the document, and when editing the document, the code is generated from the password and inserted into the document data each time the document is added, deleted, or corrected. After the document is edited, the password and the code are compared. The document data is divided into an authorized part and a non-authorized part, and for the unauthorized part, in order to determine whether the contents are correct, the document data before the editing of the part and the document of the part after the editing are determined. It is determined whether the data match, and if so, the content is correct and the document data is updated in the database.

[0007]

BEST MODE FOR CARRYING OUT THE INVENTION

(Embodiment 1) FIG. 1 is a diagram showing a system configuration of this embodiment.

[0010] Reference numeral 10 denotes a database (RDB or the like) for managing information in a table format.
1 cell.

Reference numeral 20 denotes a main memory constituted by a RAM or the like, which includes an input ID 21, a storage document 22 for temporarily storing document data before change, a delimiter A23, a delimiter B24, a comparison A25, a comparison B26, and the like. Is stored, and has various work areas such as document editing.

Reference numeral 30 denotes a console, which includes a device (for example, a keyboard) for inputting to a computer, a device (for example, a CRT) capable of displaying a response from the computer, and the like.

Next, the data structure of this embodiment will be described.

FIG. 6 shows an example of one unit of document data.
A, B, and C are start characters including the ID of each person, and are examples of the document data before editing and the archive document 22. The start character is the character that indicates the start of the part (for example, “* kaisi *”) and the ID
, And the end character is composed of a character (for example, “* syuryou *”) representing the end of the part.

FIGS. 7 and 8 show examples of document data after an editing operation such as a change. When a document creator with an ID of A works, FIG. Represents the addition of document data.

Next, the flow of the processing of this embodiment will be described.

FIGS. 3 to 5 are flowcharts.

First, in step S31, the document creator inputs an ID using the console 30, and the input ID is stored in the ID 21.

Next, in step S32, the document creator reads the document data 11 into the work area of the memory, and in step S33, copies the document data in the work area to the stored document 22 in the memory. The stored document 22 is kept as it is until the editing work of the document data in the work area is completed and the check processing described later is completed.

In step S34, the document creator creates and edits a document using the console 30.

A check process is performed in S35. This check processing will be described with reference to FIG.

The check process starts from S3501.

In step S3502, the next start character of the document data is stored in the delimiter character A23.

At S3503, ID 21 and delimiter A
The IDs included in 23 are compared. If they match, the process returns to S3502, and if they do not match, the process proceeds to S3504.

In S3504, the document data from after the start character to before the next end character is stored in the comparison A25.

In step S3505, the next start character of the stored document is stored in the delimiter B24.

At S3506, ID 21 and delimiter B
The IDs included in 24 are compared. If they match, the process returns to S3505, and if they do not match, the process proceeds to S3507.

In step S3507, the document data from after the start character to before the next end character is stored in the comparison B26.

In step S3508, the delimiter character A23 and the delimiter character B24 are compared. If they match, the process proceeds to S3509. If they do not match, the process proceeds to S3511.

In step S3509, the comparison A25 and the comparison B26 are compared. If they match, the process proceeds to step S3510 as renewable.
If they do not match, it is determined that updating is not possible, and the check processing ends in S3512.

In step S3510, it is determined whether the end of the document data has been reached. If it is the last, the check processing ends in step S3512. If not, the processing returns to step S3502, and the check processing is repeated.

In the example shown in FIG. 7, when the document creator with the ID A works, the ID including the delimiter is corrected in the portion C, and the portion outside the authority is corrected. This is S35
At 09, they do not match and cannot be updated.

In the check process of S35, it is determined whether the update is possible or not. If the update is possible in S36, the process proceeds to the update process in S37. If the update is not possible, an error message is displayed in S38 and the main process ends. .

An update process is performed in S37. This updating process will be described with reference to FIG.

In step S3701, a start character is created from ID21.

In step S3702, a start character is added after the last end character of the document data, and an end character is added at the end of the document data. As a result, when the document data is added as shown in FIG. 8, a start character and an end character including an appropriate ID are added.

In step S3703, the document data is updated, and the main processing ends.

(Embodiment 2) In this embodiment, a start character including an ID and an end character are added before and after a portion to be edited each time an edit operation of addition, correction and deletion is performed.
Since the start character does not continue twice except for the part having the authority, it is determined whether the editing operation has been performed on the part other than the authority.

FIG. 2 is a diagram showing a system configuration of this embodiment.

Reference numeral 10 denotes a database (RDB or the like) for managing information in a table format.
One cell is included.

Reference numeral 20 denotes a main memory constituted by a RAM or the like, which stores an input ID 21, a delimiter A23, and the like, and has various work areas such as document editing.

Reference numeral 30 denotes a console, which includes a device (for example, a keyboard) for inputting to a computer, a device (for example, a CRT) capable of displaying a response from the computer, and the like.

Next, the data structure of this embodiment will be described.

FIG. 13 is an example of one unit of document data. A, B, and C are start characters including the ID of each person, and are examples of the document data before editing and the archive document 22. The start character is composed of a character (eg, “* kaisi *”) indicating the start of the part and an ID, and the end character is composed of a character (eg, “* syuryou *”) indicating the end of the part.

FIGS. 14 to 16 show examples of document data after editing work such as change. FIG. 14 shows a case where a document creator having an ID A works, and FIG. Deletion of a part other than the authority, and FIG. 16 shows addition of document data.

Next, the flow of processing in this embodiment will be described.

FIGS. 9 to 12 are flowcharts.

First, in step S91, the document creator inputs an ID using the console 30, and the input ID is stored in the ID 21.

Next, in step S92, the document creator reads the document data 11 into the work area of the memory.

At S93, a process at the time of editing the document data is performed. This processing will be described with reference to FIG.

In step S9301, a start character composed of a character indicating the start (for example, “* kaisi *”) and the ID 21 is created from the ID 21.

In step S9302, the user adds document information.
When an editing operation for correction / deletion is performed, a start character and an end character (for example, * syuryou * ”) are added before and after the editing operation.

At S94, a check process is performed. This check processing will be described with reference to FIG.

From S9401, the following processing is repeated until the end of the document data or until it is determined that updating is impossible.

First, in S9402, the next delimiter character (start character or end character; the same applies hereinafter) of the document data is stored in the delimiter character A23.

In S9403, ID 21 and delimiter A
The IDs included in 23 are compared, and if they match, the process proceeds to S9404, and if they do not match, the process proceeds to S9405.

In S9404, a nesting process is performed. The nesting process is performed when the start character and the end character are arranged in a nested state, such as when the corrected part is corrected again (FIG. 17).
Reference). The nesting process is described in FIG.
This will be described with reference to FIG.

In FIG. 12, since the nesting state ends when the number of start characters matches the number of end characters, the number of start characters and end characters is determined using the variable “Ncnt” as an example. When it is "0", the nesting process has been completed.

In step S9404.1, “1” is set to Ncnt.

In S9404.3, the delimiter is stored in the delimiter A23, and in S9404.4, it is determined whether the delimiter A23 is an end character. If the delimiter is a terminator,
“1” is subtracted from Ncnt, and the flow advances to S9404.9. If the delimiter is a start character, ID21 is determined in S9404.6.
And the ID included in the delimiter character A23, and if they match, add “1” to Ncnt and proceed to S9404.9.
If they do not match, it is determined that updating is not possible, and the nesting process ends.

In S9404.9, it is determined whether Ncnt is "0". If "Ncnt" is "0", the nesting process is terminated. If not, the process returns to S9404.3 and repeats the nesting process. .

In S9409, it is determined whether or not the result of the nesting process cannot be updated. If the result cannot be updated, the checking process is terminated.
If updating is possible, the process returns to S9402.

In S9405, the next delimiter of the document data is stored in the delimiter A23.

In S9406, it is determined whether or not the delimiter character A23 is an end character. If it is a start character, the flow advances to S9407 to determine that updating is not possible and ends the check processing. If it is the end character, the flow advances to S9407 to determine the end of the document data. If it is the last, the check processing ends. If it is not the last, the flow returns to S9402 to repeat the check processing.

In the examples of FIGS. 14 and 15, S9402 and S9
The start character continues twice at 405 and cannot be updated at S9406.

[0064]

As described above, according to the present invention,
In textual document information of a database managed in a table format, the cell is divided into a plurality of parts, regardless of the unit of cell, and the contents of each part are rewritten for each part. You can check whether you are authorized and control database updates. As a result, in document information that is difficult to be divided into cells, it is possible to determine rewriting by an unauthorized user for each part of the document information and control updating of the database.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of a first embodiment.

FIG. 2 is a system configuration diagram of a second embodiment.

FIG. 3 is a flowchart of a main process according to the first embodiment.

FIG. 4 is a flowchart of a check process according to the first embodiment.

FIG. 5 is a flowchart of an update process according to the first embodiment.

FIG. 6 is a diagram showing an example of the document data of FIG. 3;

FIG. 7 is a diagram illustrating an example of data of an unauthorized modification according to the first embodiment;

FIG. 8 is a diagram illustrating an example of additional data of the first embodiment.

FIG. 9 is a flowchart of a main process according to the second embodiment.

FIG. 10 is a flowchart of a process at the time of editing document data according to the second embodiment.

FIG. 11 is a flowchart of a check process according to the second embodiment.

FIG. 12 is a flowchart of a nesting process according to the second embodiment.

FIG. 13 is a diagram illustrating an example of document data before editing according to the second embodiment.

FIG. 14 is a diagram illustrating an example of an unauthorized modification according to the second embodiment;

FIG. 15 is a diagram illustrating an example of unauthorized deletion according to the second embodiment;

FIG. 16 is a diagram showing an additional example of the second embodiment.

FIG. 17 is a diagram illustrating an example of a modification of the second embodiment.

[Explanation of symbols]

10: a database managed in a table format; 11: document data in a text format; 20: a main memory;
21: ID, 22: Archived document (stores the document before editing), 23: Delimiter A, 24 ... Delimiter B, 25
... Comparison A (stores delimiters contained in document information), 26. Comparison B (same as above), 30. Console.

Claims (2)

[Claims] 1. A database (R) for managing information in a table format.
A document processing system for creating, registering, and managing a document in a text format (DB, etc.), a data acquisition unit for acquiring document data from a cell of a database, a storage unit for storing document data before editing, Input means for inputting a password, editing means for generating a code from the input password and inserting the code when editing the document data, code extracting means for searching the edited document data and extracting the code, Password comparing means for comparing the password included in the code and the password input by the input means, first control means for controlling the processing according to the result of the password comparing means, and edited by the editing means. Document comparison means for comparing the document data with a predetermined portion of the document data stored by the storage means, and responding to the result of the document comparison means. A second control means for controlling the processing Te, database update means for writing the document data edited in the database, and the user management apparatus characterized in that a combination of means for realizing them. 2. Acquiring document data from a cell of a database, classifying the document data for each editing authority, determining whether an unauthorized portion has been edited, and if the unauthorized portion has not been edited, 2. The user management device according to claim 1, wherein said document data is updated in a database.