JPH05241932A - Information managing system - Google Patents

Abstract

PURPOSE:To enable information management manually executed in organizations by providing first-third data base (DB) interface groups and managing the right of access corresponding to the state of opening information. CONSTITUTION:Three kinds (unopened, undecided/opened and decided/opened) of DB interfaces 6 are provided. Namely, three kinds of DB interfaces 6 are displayed on a display device 1, these DB interfaces 6 are displayed by an information managing mechanism 7, and users perform access through these interfaces 6 to a DB 8 on any one work station (WS). These three kinds of DB interfaces 6 receive the state of opening information from users and based on the state of opening the respective information the information managing mechanism 7 performs access to the information. Thus, the right of access (reference/update) can be managed corresponding to the state of opening information.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information management system suitable for use in a collective decision support system, a conference support system, a monitoring system, a virtual experiment system, etc. constructed on a computer network. Participants in decision-making, meetings, monitoring, experiments, etc. span various departments and positions within the organization, and also perform work individually and as a team. In such a business form, information is handled not only as personal information but also as organizational information. In addition, the management of information is actively performed by the creator and the owner. What is particularly noticeable in the information management system according to the present invention is the "publicity state" and "authorization" of information within an organization. The present invention relates to an information management system suitable for realizing a method of managing access and distribution of information suitable for such characteristics of information.

[0002]

2. Description of the Related Art Information handled in a company can be roughly classified into organizational information and personal information. Conventionally, much of the organization information taken in by a computer system has been shared as a basic database. On the other hand, the personal information is information that the person in charge has collected or created. This is not normally disclosed to others, but it may be given to others depending on the situation. The following is known as a conventional information management method. Database management system (DBMS): Management of security and privacy for backbone databases Data items are managed individually. Since it is premised on widespread sharing, it is normally not possible for each department in charge to input / update specially and to be updated by other departments or individuals. UNIX file management: file management for a small group For each file, the owner and the group manager set the read / write authority for the owner and the group to which the owner belongs. Workstation (WS) high-level interface: A file management environment for a rather large group. Basically, it is limited to two types, a shared cabinet and a private cabinet, to avoid the trouble of setting read / write permissions. Regarding this, for example, by J. Martin,
The description in "Realization and Management of Database Environment" by Sakamoto et al. (Nikkei McGraw-Hill, 1987) is helpful.

[0003]

As described above, a computer network is used for collective decision making, meetings, monitoring,
There is a system that supports experiments. Participants cover various departments and positions within the organization, and also perform their work both individually and as a team. In the process, information of various kinds of documents, figures, graphs, etc. is created, modified, circulated and approved. It can be said that the information circulated or approved is organization information. Further, in creating or modifying, one person may be involved in one piece of information. In such a business form, the following items are important for information management. (a) Participants of information Owner, creator, referenceable person, transfer destination (passing the entity) and distribution destination (passing the duplicate), etc. Circulation is a destination sequence. (b) Information openness status Regarding whether or not the information owner presents the information to others, it can be organized into the following three statuses. Private status Undetermined / public status Fixed / public status

Then, the owner does not intend to disclose the information. For example, the information during the kneading (half boiling) is included in this state. The owner can freely update the information in this state. When updated, its owner joins the creator of the information. , The owner intends to disclose the information to those who can refer to it. However, the owner can freely update the information without contacting the referenceable person. In fact, depending on the situation, it may be unavoidably necessary to present half-boiled information. In some cases, half-boiled information is actively presented. Moreover, even if the information is updated after being presented, it is not obligatory to notify the referrer to that effect. If you want to present the updated one after the presentation again, you will present it again. When updated, its owner joins the creator of the information. Then, as the confirmed information, the owner intends to disclose the information to those who can refer to it. However, once the information is fixed, the creator is basically not allowed to update the information. In case of change, new information will be submitted as separate information or necessary procedures will be taken.

(C) Authorization of information The creator of information approves the information within the organization, that is,
It is to be accepted as organizational information. Simply put, it means to stamp the job. In the context of the open state mentioned above, it will act as a trigger for a state transition. In other words, the information of the above state is set to the state of
The information of the state of will be the state of. The above matters are widely observed as a way of managing information in organizations and people. However, only the above-mentioned (a) is considered at most in the above-mentioned prior art, and none of the above-mentioned (b) and (c) has been considered in the meaning as described above. Therefore, it has been difficult to directly apply to a system that supports collective decision making and meetings using computer networks. The present invention has been made in view of the above circumstances, and its object is to:
An object of the present invention is to provide an information management system that solves the above-mentioned problems in the conventional technology and realizes the information management method that is actually performed by humans in an organization. In particular, the feature is that it provides an information management system having three open states.

[0006]

The above object of the present invention is to provide non-public information in an information management system for accessing (referring / updating) information in a database (DB) on a computer network using a user name. A first DB interface for storing and managing, a second DB interface for storing and managing unconfirmed / public information, and a confirmed / confirmed
This is achieved by an information management system characterized in that a third DB interface group for storing and managing public information is provided and three types of DB interface groups are provided to realize access authority management corresponding to the public state of information. ..

[0007]

In the information management system according to the present invention, 3
Equipped with DB interfaces of types (non-public, unconfirmed / public, confirmed / public), these three types of DB interfaces accept the openness state of information from the user, and the information management mechanism makes the publicized state of each information and confirmed. Permission management of access (reference / update) to information is performed based on the status. As a result, access (reference / update) authority management can be realized in response to the openness state of information.

[0008]

Embodiments of the present invention will be described in detail below with reference to FIGS. FIG. 1 is a block diagram of an embodiment of an information management system according to the present invention. A plurality of workstations (WS) are electronically connected by a communication path 5.
Each WS has a display device 1, a computing device 2, a storage device 3, and an input device 4. An information management mechanism 7 is mounted on the computing device 2. A database (DB) 8 is installed in the storage device 3. The main functions of the information management mechanism 7 are management of access to the DB 8, management of interaction with the user via the display device 1, management of information exchange with other WS, and the like. Display device 1
Three types of DB interfaces 6 are displayed on the top.
This DB interface 6 is displayed by the information management mechanism 7, and the user accesses the DB 8 on any WS via this interface. Figure 2
FIG. 4 shows details of an embodiment of the interface displayed on the display device 1. As the DB interface 6, three types of buttons are displayed. Private data access button 21 and unconfirmed / public data access button 2 respectively
2, a confirmation / public data access button 23. In addition to these, a received data display button 24, another site data access button 25, a new creation button 26, and an end button 27 are also displayed.

FIG. 3 shows an example of the structure of data targeted by the information management system according to the present invention. The data structure includes a data item name 31, various name lists 38, and a data body 37. The name list 38 includes a creator name 32, a mark 33, a referenceable person name 34, and a distributor name 3.
5 and destination name 36. Creator name 32 and mark 33
Are treated as a pair. These names are used for determining the access authority of the user who accesses the data and automating the distribution and movement. The processing is performed by the information management mechanism 7. FIG. 4 is an embodiment for realizing the function of the information management mechanism 7. Dialog management unit 42, DB access management unit 43, data exchange management unit 46 between other WS, e-mail transmission / reception management unit 48, other WS connection management unit 44, data path switch 41, mark registration unit 47, other WS communication index 45. Consists of. The dialogue management unit 42 manages the dialogue with the user via the display device 1, analyzes the input command, and activates the appropriate management unit. The DB access management unit 43 manages access to the DB and management of information distribution and movement. The other WS data exchange management unit 46, the electronic mail transmission / reception management unit 48, the other WS connection management unit 44, and the other WS communication index 45 are for the management function of information exchange with other WS.

The other WS-to-WS communication index 45 contains identification numbers and addresses necessary for designating the other party when transferring data or files using the communication path 5 or sending electronic mail. Store. In the mark registration unit 47, the confirmed mark and the unconfirmed mark for each user are read by an image scanner and stored. The data path switch 41 includes a display device 1, an input device 4, and a dialogue management unit 4.
2, the data flow between the DB access management unit 43 and the data exchange management unit 46 between other WS is switched. There are four modes of data flow. 3 of them
The two modes are shown in FIG. Mode A includes the display device 1 / input device 4, the dialogue management unit 42, and the DB access management unit 43.
Put a data path between and. Mode B is for display device 1
A data path is established between the input device 4 and the other-WS data exchange management unit 46. In mode C, a data path is established between the other WS data exchange management unit 46, the dialogue management unit 42, and the DB access management unit 43. The fourth mode is an off state in which no path is set up for any of them. Mode A is
Used when accessing the DB of your site. Mode B and mode C are used in combination when accessing the DB of another site.

A DB 8 which is a management target of the information management mechanism 7 is mounted on the storage device 3. As shown in FIG. 6, the DB 8 is constituted by the first group file 61, the second group file 62, the third group file 63, the reception data file 6
It is 4. The first group file 61 stores private data, the second group file 62 stores unconfirmed / public data, the third group file 63 stores fixed / public data,
The reception data file 64 temporarily stores the data received from another WS. Next, an outline of processing of each management unit will be shown. The dialogue management unit 42 is composed of three programs. First
Is a dialogue management program A, the second is a dialogue management program B, and the third is a received data processing program. The dialogue management program A is used when the DB is accessed from the own WS, and the dialogue management program B is used when data is accessed from another WS. Further, the dialogue management program A is initially activated when the information management mechanism 7 is activated. The received data processing program is a subroutine of the dialogue management program.

FIG. 7 shows a processing flow of the dialogue management program A. First, set the data path switch 41 to mode A.
(Step 105). As a result, a path is established between the display device 1 or the input device 4 and the dialogue management unit 42 or the DB access management unit 43. Next, the menu screen for own site is displayed (step 110). What is displayed here is the screen shown in FIG. Then wait for the menu button to be clicked (step 115). When the button is clicked, the processing corresponding to the button is performed (step 120). If the clicked button is as follows, set the processing mode as follows.
In case of private button 21, private data processing mode
(Step 125), unconfirmed / public data processing mode for the unconfirmed / public button 22 (step 130), confirmed / public data processing mode for the confirmed / public button 23
(Step 135), in the case of the new creation button 26, the new creation mode (Step 140) is set. After setting the processing mode in this way, the DB access program is activated in the mode (step 165). When the clicked button is the received data display button 24, the received data processing program is started (step 145), and when it is the other site data button 25, the other site connection program A is started (step 150). When the end button 27 is pressed, the menu is erased (step 155) and the data path switch 41 is turned off (step 160).

FIG. 8 shows a processing flow of the dialogue management section program B. First, display the menu screen for other sites
(Step 205). The menu screen for other sites has the new creation button 26 and the received data display button 24 from the screen of FIG.
The other site data button 25 is excluded. Then wait for the menu button to be clicked (step 210).
The following processing is performed according to the clicked button. When it is the private button 21, it is private data processing mode (step 220).
In the public data processing mode (step 225), when the confirmation / public button 23 is selected, the confirmation / public data processing mode (step 230) is set, and the DB access program is activated in this mode (step 240). When the end button 27 is pressed, the menu is erased (step 235). FIG. 9 shows a processing flow of the received data processing program. First, the name of the user in use is input (step 305). Next, the data sent to the user is retrieved from the received data file and displayed as a list (step 310). The user selects and specifies one of the data (step
315). Display selected data (step 32)
0). After the display, it is determined whether there is a storage request (step 325). If there is a storage request, the following check is performed (step 330). In other words, if the user name of the user is included in the creator name column of the data and the confirmation mark is written or if this condition is not satisfied, the data is stored in the first group file 61 (step 335), when the condition is satisfied, the data is stored in the third group file 63 (step 340).

The DB access management unit 43 comprises a DB access processing program. This can be activated from the dialog management programs A and B. At startup, the processing mode is passed as a parameter from those programs. DB in FIG. 10 and FIG.
The processing flow of an access processing program is shown. First, the user's name is input (step 405). If the processing mode is the new creation mode, jump to step 445 (step 410). In the case of other processing modes, that is, private data processing mode, unconfirmed / public data processing mode,
In the case of the fixed / public data processing mode, next, the access type is input (step 415). There are two types of access, update and reference. Depending on the input user name, access type, and processing mode described above, conditions are divided in steps 470a to 470f to search for accessible data from the corresponding nth group file.
(Steps 420a-f). The details of the search process will be described below. When the access type is updated in the private data processing mode, the user name in the data in the first group file 61 is the creator name 32 of the name list 38 or the distributor name 35.
Alternatively, the data appearing in the destination name 36 is selected (step 420a). When the access type is reference in the private data processing mode, the user name in the data in the first group file 61 is the creator name 32 of the name list 38, the referenceable person name 34, or the distributor name 35. Alternatively, the data appearing in the destination name 36 is selected (step 420b).

When the access type is updated in the undetermined / public data processing mode, the user name in the data in the second group file 62 is the creator name 32 of the name list 38.
Alternatively, the data appearing in the distributor name 35 or the destination name 36 is selected (step 420c). When the access type is reference in the undetermined / public data processing mode, the user name in the data in the second group file 62 is the creator name 32 of the name list 38, the referenceable person name 34, or the distribution. Person name 35
Alternatively, the data appearing in the destination name 36 is selected (step 420d). When the access type is updated in the confirmed / public data processing mode, the user name in the data in the third group file 63 is the distributor name 35 in the name list 38.
Alternatively, the data appearing in the destination name 36 is selected (step 420e). Further, when the access type is reference in the confirmed / public data processing mode, the user name in the data in the third group file 63 is the creator name 32 of the name list 38.
Or referable person name 34, distributor name 35, destination name 3
The data appearing in No. 6 is selected (step 420f). What should be noted here is that the third group file is not permitted to be updated even by the creator of the data. Next, the above-mentioned accessible data list is displayed (step 425). The user selects one data from the list (step 430). Hereinafter, different processing is performed depending on the access type. If the access type is reference, display the selected data (step
465) and jump to step 460. Incidentally, in step 465, the aforementioned unconfirmed or confirmed mark is also displayed.
When the access type is update, the following series of processing is performed.

First, the creator name 32 and the mark 33 of the data are copied into the work area and temporarily stored (step
440). This is to protect the creator name 32 from being changed. Next, the editing program is activated to update the data (step 445). In addition, step 4
In 45, the mark is also displayed together with the data to be processed by the editing program. At the same time, the various name list 38 is updated (step 450). After the end of the editing program, in step 440, the temporarily stored creator name 32 and mark 33 are restored in the name list (step 445).
At this time, if the processing mode is the non-public mode or the unconfirmed / public mode, the user name read in step 405 is added to the creator name list 32. Finally, store the data
(Step 460). FIG. 12 shows the details of the storage process. First, the storage destination is input (step 505). The storage destination is either private data, undetermined / public data, or fixed / public data. The following processing is performed for each. In the case of private data, the same check as in step 330 in the received data processing program is performed (step 515), and it is stored in the first group file 61 (step 520) or the third group file 63 depending on the condition. (Step 525). In the case of undetermined / public data, the same check is performed (step 530), and depending on the condition, it is stored in the third group file 63 (step 550) or the following processing is performed.

First, a marking request is input, and if there is a request, an unconfirmed mark is copied from the mark registration section 47 and written in the mark column in each name 38 (step 53).
Five). At this time, if the distributor column is not empty, a copy of the data is transmitted to those distributors (step 540). Following this, the data is stored in the second group file 62.
(Step 545). Further, in the case of the confirmed / public data, a marking request is input, and if there is a request, the confirmation mark is copied from the mark registration section 47 and written in the mark column in the various names 38 (step 555). If the distributor field is not empty, then a copy of the data is transmitted to those distributors (step 560). If the destination is not empty (step 565),
The data is transmitted to the destination (step 575), or stored in the third group file 63 (step 570). Other W
The S connection management unit 44 is composed of two programs, another WS connection management program A and another WS connection management program B. These programs on different WS coordinately set the data path switch 41 so that the DBs of other WS can be accessed. FIG. 13 shows a processing flow of the other WS connection management program A, and FIG. 14 shows a processing flow of the other WS connection management program B. The other WS connection management program A first accepts the input of the owner name of the DB 8 to be accessed (step 605). Based on the input name, the mail address of the owner is retrieved from the other WS communication index 45 and a DB access request mail is sent (step 610). This email is a W
It causes the S connection management program B to be activated (the electronic mail reception management program described later).

Next, it waits for a reply mail from the other party (step 615). The other WS connection management program B returns the response mail to the request source (step 635) and sets the data path switch 41 to the C mode (step 640). When the reply mail arrives, the other WS connection management program A sets the data path switch 41 to the B mode (step 620). At this point, the display device 1 and the input device 4 of one WS (the other WS connection management program A is running) and the other WS (the other W)
The dialog management unit 42 (when the S connection management program B is running) and the DB access management unit 43 are connected for access.
When the DB access ends, the other WS connection management program B sends a DB access end mail to the request source (step 650) and turns off the data path switch 41 (step 660). The other WS connection management program A waits for a DB access end mail from the other party (step 625), and sets the data path switch 41 to A mode when the mail arrives.
(Step 630). At this point, the access connection between the two WS is canceled. The electronic mail transmission / reception management unit 48 includes an electronic mail transmission management program and an electronic mail reception management program. FIG. 15 shows a processing flow of the electronic mail transmission management program.

The electronic mail transmission / reception management unit 48 first waits for an electronic mail transmission request from a program of another management unit.
(Step 705). When an outgoing request comes, a header corresponding to the request is added (step 710). The header is "Distribute / Move",
“Other WS access request”, “reply” or “other WS access end” and the like. Next, referring to the inter-WS communication index 45, the mail address is determined from the destination user name.
(Step 715) and make a call (Step 720). The processing flow of the electronic mail reception management program is shown in FIG. First, wait for the arrival of the email (step 725). Processing is divided as follows according to the header of the arrived mail (step 730). In the case of "distribution / movement", the mail is stored in the received mail file (step 735). In the case of "other WS access request", the other WS connection management program B is started (step 740). In case of "Reply", send the email to another W
Pass it to the S connection management program A (step 745). "Other W
In the case of "S access end", the mail is passed to the other WS connection management program A (step 750).

According to the above-described embodiment, it is possible to realize an information management system which can appropriately cope with each of the three states of the information state, that is, the non-disclosure state, the unconfirmed state, the disclosure state, the confirmed state and the disclosure state. More specifically, the creator or owner explicitly specifies in data units such as who created it, who should give it, and who can show it to the user. Person, creator, etc.) easily and flexibly. Management of access authority to information is performed based on the openness state of three types of information, and these three types are the same as information management performed by humans in daily business. It is easy for the creator and owner to specify the access authority, and it is possible to avoid useless operations when using the system. In general, humans make various judgments as to whether the obtained information is undetermined or confirmed.
Here, by clarifying this distinction on the system,
The referrer or the person who receives the distribution / movement can make the same judgment as in reality.

Here, three types of information openness states are prepared. Since this number is not unnecessarily large, it can be expected that the user's judgment error is small. The above-mentioned three types of states are the same as information management performed by humans in daily work. It can be expected that the user will feel little resistance in using the product. When applied to a collective decision support system, a conference support system, etc., it is possible to devote itself to the original decision-making work or conference due to the above reasons. It is needless to say that the above embodiment is an example of the present invention and the present invention should not be limited to this. For example, by using the image data of the job stamp as the above-mentioned confirmation mark, it is possible to give the user a further sense of reality. Further, in the above embodiment,
By configuring the files of the first to third groups in the DB, the data is stored in a form corresponding to the three types of interfaces, but it is not necessary to have such a form. For example, if the DB access management unit has a file management table and manages the correspondence between file names and openness states,
A unified file structure may be used in B.

[0022]

As described above in detail, according to the present invention, it is possible to realize a remarkable effect that an information management system capable of managing information actually performed by humans in an organization can be realized. ..

[0023]

[Brief description of drawings]

FIG. 1 is a hardware configuration diagram of an information management system showing an embodiment of the present invention.

FIG. 2 is an interface screen of the embodiment.

FIG. 3 is a diagram illustrating a data structure according to an embodiment.

FIG. 4 is a conceptual configuration diagram of an embodiment.

FIG. 5 is a diagram illustrating paths of a data path switch according to the embodiment.

FIG. 6 is a configuration diagram of files in a DB in the embodiment.

FIG. 7 is a process flow diagram of a dialogue management program A in the embodiment.

FIG. 8 is a process flow diagram of a dialogue management program B in the embodiment.

FIG. 9 is a processing flow chart of a received data processing program in the embodiment.

FIG. 10 is a part of a processing flow chart of a DB access processing program B in the embodiment.

FIG. 11 is another part of the processing flow chart of the DB access processing program B in the embodiment.

FIG. 12 is a processing flowchart of a storage processing program according to the embodiment.

FIG. 13 is a WS connection management program A according to the embodiment.
It is a processing flow diagram of.

FIG. 14 is a WS connection management program B according to the embodiment.
It is a processing flow diagram of.

FIG. 15 is a process flow diagram of an electronic mail transmission management program in the embodiment.

FIG. 16 is a process flow diagram of an electronic mail reception management program in the embodiment.

[Explanation of symbols]

1: Display device, 2: Computing device, 3: Storage device, 4: Input device, 6: DB interface, 7: Information management mechanism,
8: DB, 21: Private data button, 22: Not confirmed ・
Public data button, 23: Confirm / Publish button, 38: Various name list, 43: DB access management unit.

 ─────────────────────────────────────────────────── ─── Continuation of front page (72) Inventor Nihei Tate 5-2-1 Omika-cho, Hitachi-shi, Ibaraki Prefecture Hitachi Ltd. Omika factory

Claims (15)

[Claims] 1. A user name is used to access information in a database (DB) on a computer network (see
In the information management system to be updated), the first DB interface for storing and managing non-public information, the second DB interface for storing and managing unconfirmed / public information, and the management for storing fixed / public information Third to do
An information management system characterized by providing three kinds of DB interface groups, which are the DB interfaces, to realize access authority management in response to information disclosure and decision state correspondence. 2. The creator, wherein the first DB interface is a list of user names of users who are involved in creating (updating and editing) information for each information that can be operated using the interface. A name list is added and only the information access of the users in the creator name list is permitted,
The second DB interface does not permit information access from a user who is not in the creator name list, and the second DB interface operates on the interface, and for each information, the creator name list and the reference name Add a list and allow information access to the users in the creator name list,
Moreover, only the information reference is permitted to the users in the referrer name list, and the third DB interface is
The creator name list and the referrer name list are added to each piece of information that can be operated using the interface, and the users in the creator name list are allowed to refer to the information only, and The information management system according to claim 1, wherein information reference is permitted to a user in the referrer name list. 3. The information which can be operated using the second DB interface is added with an unconfirmed mark indicating that the information is unconfirmed in the form of a pair (pair) with the creator name. The information management system according to claim 2, wherein the information is presented to the creator and the referrer. 4. The information that can be operated using the third DB interface is added with a confirmation mark that means that the information has been confirmed, in the form of a pair (pair) with the creator name. The information management system according to claim 2, wherein the information is presented to the creator and the referrer. 5. The unconfirmed mark according to claim 3 and claim 4.
The information management system according to claim 2, wherein the confirmation mark described is presented to the creator and the reference person. 6. When a user displays access information,
The information management system according to any one of claims 3 to 5, wherein the unconfirmed mark or the confirmed mark indicating whether the information is unconfirmed or confirmed is also displayed. 7. A distributor name list, which is a user name list of distribution-destination user groups, is added to each of the information that can be operated using the second DB interface,
For information stored using the second DB interface, if the distributor name list of the information is not empty, the information is duplicated including various additional name list groups of the information, and the duplicated information An undetermined mark indicating that the information is undetermined is added to the distributor name list in the form of a pair (pair) with the creator name and transmitted to the users in the distributor name list. Information management system described in 2. 8. A move that includes a distributor name list, which is a user name list of a distribution destination user group of the copy information, and a transfer destination user name of the information entity, for each of the information that can be operated using the third DB interface. If the distributor name list of the information is not empty with respect to the information stored by adding the destination name list and using the third DB interface, the information including additional various name list groups of the information is included. Is duplicated, a confirmation mark indicating that the information has been confirmed is added to the duplicated information in the form of a pair (pair) with the creator name, and then transmitted to the users in the distributor name list. And, if the destination list of information is not empty,
To the information, add a confirmation mark that means that the information has been confirmed in a pair (pair) with the creator's name, and then add the name list group of the information to the destination name. 3. The information management system according to claim 2, further comprising the step of transmitting the information to the users on the list. 9. The information management system according to claim 2, further comprising the transmission step according to claim 7 and the transmission step according to claim 8. 10. The transmitted information, if the user name of the user is included in the creator name list of the information, and the confirmation mark is added as the pair, the first 3 as the information operated by the DB interface. In other cases, the first D is stored.
The information management system according to any one of claims 7 to 9, wherein the information is stored as information operated by a B interface. 11. A user who has received distribution or transfer, when displaying transmitted information, also displays an unconfirmed mark or a confirmed mark indicating whether the information is unconfirmed or confirmed. The information management system according to any one of claims 7 to 10, which is characterized. 12. The updater is added as a creator when information is updated using the first DB interface or the second DB interface, according to any one of claims 2 to 11. Information management system described in crab. 13. When the information is updated using the first DB interface or the second DB interface, the updating person is added as a creator, and in other cases, the creator is added. The information management system according to any one of claims 2 to 11, wherein updating of the list is not permitted. 14. An information management system according to claim 4, 5, 8 or 9, wherein a confirmation mark peculiar to each user is used. 15. The information management system according to claim 14, wherein image data of a job stamp is used as the confirmation mark.