JP2006268703A - Document management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a document management system, capable of executing a workflow while simplifying job execution in status change such as "three copy printing of a collection approval document" or "mail delivery to the following worker", and providing a function enabling a user to find in which work of the workflow (which status) a document is at a glance. <P>SOLUTION: In this document management system, job information within the system is added to an annotation as additive information, and when the annotation is added to a document, the job is executed. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a document management system that centrally manages image documents and code documents.

  In such an office environment, a document management system is constructed by arranging a device that can read a document, a server that manages the document, and a client such as a PC for using the document on the same network (for example, Patent Documents). 1).

  In the document management system described above, images in various formats are registered, and registered image documents are taken out from the document management server and used.

  A function for restricting access for each document for each user accessing the document management system is also generally known.

  A function for displaying annotation information such as annotations and memos managed by a document management system in a superimposed manner on a document is also generally known.

Also, in the document management system, for example, a specific operation (job) such as printing three copies of a document or e-mail notification to a specific user is registered in advance, and the registered job is selected. A function that can easily execute a job simply by executing it is also generally known.
JP-A-6-305200

  However, in the conventional document management system, when an image such as an image in BMP format that tends to be large is stored, the amount of memory and processing time required for display, printing, image processing, and the like are large. .

  In addition, when performing access restriction for each document for each user who accesses the document management system, a document is selected, a setting screen is displayed, and access setting is performed for the user who sets the access restriction. It is necessary to repeatedly perform the complicated operation of performing each operation for each document, which may increase the burden on the administrator. In addition, there is a possibility that the access control information of the document managed in this way may be difficult for a general user to understand.

  In addition, in order to determine whether or not a job registered in the document management system has been executed, it is only possible to determine from a management information log in the document management system, which may be difficult for general users to understand.

  SUMMARY An advantage of some aspects of the invention is that it provides a document management system capable of performing image conversion in an image conversion format corresponding to an image format of a document to be registered.

  It is another object of the present invention to provide a document management system capable of extracting a document in an image format according to the purpose of use of the document.

  To achieve the above object, the present invention sets an image conversion method for each image format in a document management system capable of registering, managing and extracting at least two types of image documents in a database. A setting unit that performs determination, an analysis unit that can determine the format of the image file, and an image conversion unit that converts the image file, and performs image conversion according to the image format of the document to be registered, It is characterized by registering.

  In document management systems, there has been a demand for simplification of document access control. In addition, there is a need for a function that allows users to know at a glance what access rights are set for a document.

  In order to achieve the above object, according to the present invention, in a document management system capable of registering, managing and extracting an image document in a database, a storage means for storing document access control information as document management information, and a document A storage means for storing the access control information of the document as management information for the added annotation, and a management means for restricting the access of the document by the access restriction information are provided. The document access restriction is performed using the access restriction information in the annotation instead of the access restriction information.

  In addition, in the document management system, there has been a demand for a function that can tell at a glance what kind of job has been executed for a document.

  In a document management system capable of registering, managing, and extracting image documents in a database, a storage unit that stores job information, a storage unit that stores job information as management information for annotations added to the document, and a job An execution means for executing a job according to information is provided, and when an annotation is added to a document, the job in the annotation management information is executed.

  According to the present invention, in a document management system capable of registering, managing, and extracting at least two or more types of image documents in a database, setting means for setting an image conversion method for each image format; By providing an analysis unit that can determine the format of the file and an image conversion unit for converting the image file, the document can be registered by performing image conversion according to the image format of the document to be registered. This makes it possible to save documents efficiently.

  Further, according to the present invention, in a document management system capable of registering, managing, and extracting image documents in a database, storage means for storing document access control information as document management information, and annotations added to the document A storage unit that stores document access control information as management information and a management unit that restricts document access using access restriction information. If an annotation is added to a document, it is not the access restriction information in the document. Using the access restriction information in the annotation, the document access can be restricted.

  In a document management system capable of registering, managing, and extracting image documents in a database, a storage unit that stores job information, a storage unit that stores job information as management information for annotations added to the document, and a job Execution means for executing a job according to information is provided, and when an annotation is added to a document, the job in the annotation management information can be executed.

  Hereinafter, the best mode for carrying out the present invention will be described in detail with reference to examples.

[First embodiment]
A first embodiment of the present invention will be described below with reference to the drawings.

  FIG. 1 is a diagram showing system blocks of a document management system according to the present invention.

  The document management system according to the present embodiment is a client (1000) / server (1100) type application that runs on the OS of a personal computer. The document management system captures a document from a device such as a scanner or a file on the OS and manages the document. The purpose is that.

<Document input / output processing section>
First, a processing unit that performs document input / output and operations will be described.

  Reference numeral 1001 denotes a user interface unit. The user performs operations such as document registration, document acquisition from the document server, and document search via the user interface unit.

  Information operated from the user interface unit is analyzed by the command control unit 1002, and appropriate processing is performed. If necessary, a command for communicating with the server is created here.

  A device such as a scanner is controlled by a device control unit 1003. Here, processing is performed to download document data from the device side or receive data transmitted from the device side.

  A document file saved on an OS such as a file server can be input-processed by a file control unit 1004 in a form of importing document data. Also, a process for exporting a file managed on the document management server onto the OS is performed here.

  Reference numeral 1005 denotes an external module communication unit that communicates with an external application, passes a document in the document management server to the external application, and receives a document from the external application. For example, a process of passing a document managed by the document management server to a mailer corresponding to MAPI is performed here.

<Client system internal processing unit>
Next, various processing units arranged in the client system will be described.

  Reference numeral 1006 denotes a document management control unit, which is the heart of the client. Here, processing is performed in accordance with an image or command passed from the input / output processing unit.

  Reference numeral 1007 denotes an internal data storage unit for storing temporary data. This is a place for temporarily storing data created in the process of image processing, data created in the process of communication with the server, and the like.

  A file analysis unit 1008 determines whether the registered document is a document that can be handled as an image. If it is a document that can be handled as an image, image processing is performed as required by the image document processing unit 1010, and if it is a code document that cannot be handled as an image, processing is performed by the code document processing unit 1009. Although the code document is rarely processed on the document management server, the code document processing unit performs thumbnail creation processing for the code document, income of document attributes, and the like. A preview image creation operation is also performed by the image document processing unit 1010.

  Reference numeral 1011 denotes a communication control unit that performs control for communicating with the server 1100. The communication control unit of this embodiment performs only control specialized for the processing of the document management server, and the communication itself such as TCP / IP is controlled using what is prepared in the OS.

<Server system internal processing unit>
Next, various processing units arranged in the server system will be described.

  A communication control unit 1101 performs control for communication with the communication control unit 1011 of the client. However, the communication control unit of the server can communicate simultaneously with the communication control units of many clients.

  Reference numeral 1102 denotes a search control unit which performs processing for searching requested by a client or processing for creating an index for searching registered documents.

  Reference numerals 1103, 1104, and 1105 denote a file analysis unit, a code document processing unit, and an image document processing unit. The main function is the same as that of the client, but the server performs a process of extracting a search index from the document according to the registered document. That is, the type of the file registered in the file analysis unit is determined, and if it is a code document, the index data is extracted using the code document processing unit. If it is an image document, image processing is performed by an image document processing unit, and index data is extracted using an OCR engine 1106.

  A document management control unit 1107 distributes all processes related to document management.

<Database processing part>
Next, the database processing unit will be described.

  A database control unit 1108 creates data to be stored in the database, and performs processing for storing documents and information corresponding to the volume database, attribute database, and full-text search database. In addition, in response to a request from the client, data is extracted from each database and processing for creating a document to be passed to the client is performed.

  A volume database 1109 is a database in which image documents and code documents themselves are stored. Annotation image data is also saved.

  Reference numeral 1110 denotes an attribute database in which information relating to attributes such as a document name, creation date, and comments is stored. In addition, information about a user who uses the document management system and various setting data are also stored in 1110. Also, annotation management information is stored.

  Reference numeral 1111 denotes a full-text search database, in which text data is extracted from a registered document, and data converted into index information is registered. When full-text search is performed on the client, the full-text search database is searched.

  FIG. 2 is a diagram showing a flow in the server and client of document registration processing, which is the basic operation of the document management system of the present invention.

<Client side document registration process>
First, document registration processing on the client side will be described.

  In step S2001, the file is loaded into the application. In this process, the device control unit (1003), file control unit (1004), and external module control unit (1005) are used to manage files existing on the OS, images from the scanner, and documents from external applications. Import into the application.

  In step S2002, processing for analyzing the captured file is performed. This processing is performed by the file analysis unit 1008, and processing such as determination as to whether the captured document can be handled by the document management system or capturing of attribute information of the file itself is performed.

  In step S2003, it is determined whether the analyzed document is an image document or a code document. This determination is also made by the file analysis unit 1008. When registering a document in the document management server, it is necessary to register a thumbnail displayed for confirming the document on the client at the same time as the actual document. In the document management server of this embodiment, this thumbnail creation processing is performed on the client side. Therefore, it is necessary to analyze the contents of the file, and as a result, the module to process the file is changed.

  If it is determined as a code document, the process proceeds to S2004, and a code document process is performed. This processing is performed by the code document processing unit 1009, and a thumbnail to be displayed on the client from the code document is created, and attribute information stored in the code of the code document is extracted.

  If it is determined as an image document, the process proceeds to S2005, and image document processing is performed. This processing is performed by the image document processing unit 1010 to create thumbnails and the like. At this time, a file may be temporarily stored in the temporary folder 1007.

  In S2006, it is determined whether or not the image document to be registered is converted and saved, and if necessary, the image document is converted in S2007.

  In S2008, processing for transmitting thumbnails and document data to the server is performed. In this embodiment, TCP / IP is used as a communication protocol, and basic processing related to TCP / IP is performed by the OS.

  The above is the document registration process in the client.

<Server-side document registration process>
Next, document registration processing on the server side will be described.

  In S2101, processing for receiving data transmitted from the client is performed. Here, as with the client, the basic processing related to TCP / IP is performed by the OS.

  In step S2102, the received file is analyzed. This processing is performed by the file analysis unit 1103 in response to an instruction from the search control unit 1102.

  In step S2103, it is determined whether the analyzed document is an image document or a code document. This determination is also made by the file analysis unit 1103. In order to search for a document registered in the document management server, it is necessary to extract index data for document search from the document. Therefore, it is necessary to analyze the contents of the file, and as a result, the module to process the file is changed.

  If it is determined as a code document, the process proceeds to S2104, and a code document process is performed. This process is performed by the code document processing unit 1104, and search index data is extracted from the code document.

  If it is determined that the document is an image document, the process advances to step S2105 to perform image document processing. This processing is performed by the image document processing unit 1105 to perform image conversion of the document. The image conversion performed here is for processing for obtaining an image suitable for OCR, and the document actually received from the client is registered as it is for the image actually registered in the database.

  In step S2106, OCR is performed on the image converted in step S2105, and search index data is extracted.

  In step S2107, the document data received from the client is stored in the volume database 1109. The data stored in the volume database is the received document data itself and thumbnail data.

  In step S2108, processing for registering search index data extracted from the document data in the full-text search database 1111 is performed.

  In step S 2109, the document attribute data, the document data ID registered in the volume database, and the search index data ID registered in the full-text search database are registered in the attribute database 1110. Thereby, the data registered in the attribute database, the volume database, and the search database are associated with each other.

  The above is the document registration process in the server.

  FIG. 3 is a conceptual diagram of the data structure of data registered in the attribute database 1110. Although it has a tree structure as a concept to the last, it does not have to be a tree structure.

  Reference numeral 3001 denotes a root of the attribute database, and data registered in all documents is child data of the root.

  Reference numeral 3002 denotes folder data, which is folder data for the user to store data. The folder data is composed of a folder ID and folder attribute information. Since a plurality of folders can exist, the uppermost folder is registered as child data that is connected directly below the root as many as 3003.

  Reference numeral 3004 denotes document data, which exists as child data of the stored folder. The document data includes a document ID, document attribute information, and additional information. Data such as a document name, update date and time, and comment data are stored as the document attribute information. The additional information stores access right information of each user managed by the document management system added to the document. Since a plurality of document data can exist under the folder, the document data is registered as many as 3005.

  Further, it is possible to have a folder in a hierarchical structure by making another folder exist under the folder. In this case, it is registered as 3006.

  Reference numeral 3007 denotes page data, which stores information about each page of a registered document. The page data includes a page ID, page attribute information, a search index ID, and a volume data ID. The search index ID is an ID of information stored in the full-text search database, and the volume data ID is an ID registered in the volume database. Information can be extracted from each database from each ID.

  Information such as page number and page file format is stored in the page attribute information. The page data can exist as many as the number of pages, and is registered as 3008. However, since the code document cannot be divided and stored for each page, it is treated as a document having only one page, and there is only one page data.

  Reference numeral 3010 denotes annotation data, which stores information related to annotations added to registered documents by an annotation pasting operation described later. The annotation data consists of an annotation ID, position, and size information. Annotation ID is an annotation ID managed in an annotation data table in the attribute database, which will be described later. Based on this ID, various types of annotation information can be acquired from the annotation data table. Information such as the size of the annotation and the position of the annotation is stored, and when displaying page data based on such information, the annotation can be synthesized and displayed.

  FIG. 5 is a conceptual diagram of the data structure of the annotation data table registered in the attribute database 1110.

  Reference numeral 5001 denotes an annotation data table in the attribute database 1110. The data of each annotation is arranged and stored on the table.

  Reference numeral 5002 denotes individual annotation data in the annotation data table, which includes an annotation ID, attribute information, additional information, and volume data ID. The attribute information is an annotation name and this annotation pasted for each user managed by the document management system. Various kinds of information such as whether the operation is permitted (or prohibited), and the additional information is document access right information when this annotation is added for each user managed by the document management system, The volume data ID is an ID registered in the volume database 1109. Based on this ID, the volume information of the annotation can be extracted from the volume database.

  FIG. 6 is a diagram showing an example of a dialog screen for setting annotations in the document management system of the present invention.

  S6001 is a dialog for displaying an annotation list, and the names of the annotations are arranged on the list. On this dialog, annotations can be added and deleted, and the settings of the annotation selected on the list can be changed.

  S6002 is an annotation setting dialog that is opened when the [Add] button in S6001 or an arbitrary annotation on the list is selected and the [Set] button is pressed. In this dialog, you can change the annotation name. It is also possible to open a dialog for selecting an annotation diagram, selecting a user who is permitted or prohibited, and setting an access right for a document with this annotation.

  S6003 is a dialog for selecting an annotation diagram from an OS file, which is opened when the [Select Diagram] button is pressed in S6002. The figure file can be selected by entering the figure file name in the text box or selecting the figure file on the general file selection dialog (not shown) opened by clicking the [Browse] button. .

  S6004 is a dialog for setting, for each user, permission or prohibition of the annotation pasting, which is opened when the “select user to use” button is pressed in S6002. Users who can be pasted and users who are prohibited from pasting are displayed in the allow list and the prohibit list, respectively, and the user moves from the list by selecting the user on the list and pressing the arrow button.

  S6005 is a dialog for setting the access right of the annotated document that is opened when the [Document Access Right Setting] button is pressed in S6002. On the list, the user names managed by the document management system and the access rights of “none”, “read only”, and “change” to the user's document are displayed. By selecting a user name on the list and selecting an access right from the right drop-down list, the access right of the selected user can be changed.

  FIG. 4 is a diagram showing the flow in the server and client of the document display process, which is the basic operation of the document management system of the present invention.

<Server-side document display processing>
First, document display processing on the server side will be described. It is assumed that the selection and display instruction for the document to be displayed on the client side have already been performed before the processing on the server side.

  In step S4001, processing for receiving a command transmitted from the client is performed.

  Analysis processing of the command received in S4002 is performed, and processing is distributed based on the analyzed result. Since this flow is a document display instruction, the ID of the document to be displayed included in the command information is included in the command.

  In step S4003, it is checked whether the document has an annotation. If there is an annotation, the access right information of the document is acquired from the additional information of the annotation (S4004).

  It is checked whether there is a document access right from the access right information acquired in S4005. If there is no access right, warning information is transmitted to the client (S4014).

  In step S4006, the access right information of the document selected from the additional information of the document is acquired.

  It is checked whether there is a document access right from the access right information acquired in S4007. If there is no access right, warning information is transmitted to the client (S4014).

  In step S4008, attribute information is extracted from the attribute database based on the document ID.

  In S4009, the volume data corresponding to the volume ID stored in the attribute data is acquired and converted into a form to be transmitted to the client.

  In step S4010, it is determined whether there is an annotation from the page ID based on the document ID. If there is an annotation, the annotation attribute information is extracted (S4011), and volume data corresponding to the annotation volume ID is acquired in the same manner. The data is converted into a form to be transmitted to the client (S4012).

  A process of transmitting the data created in S4013 to the client is performed.

  The above is the document display process in the server.

<Client-side document display processing>
Next, document display processing on the client side will be described.

  In S4101, processing for receiving data transmitted from the server is performed.

  The information received in S4102 is analyzed.

  If the information received in S4103 is warning information that there is no access right, a warning message is sent to the user interface unit 1001 for display (S4110).

  In S4104, the document data is expanded into memory as 1070 temporary data for display data creation.

  In step S4105, the document data is converted for display from the data developed in the memory.

  If there is annotation data in S4106, the annotation size and position information is acquired from the added attribute data, and the annotation data is combined with the display data (S4107).

  In step S4108, the memory data expanded in step S4104 is deleted.

  In step S4109, the display data created in step S4105 is sent to the user interface unit 1001 for display.

  The above is the document display process in the client.

  FIG. 7 is a diagram showing a flow in the server and client of the annotation pasting process to the document in the document management system of the present invention.

<Annotation pasting and saving process>
The annotation pasting process is explained. The document is displayed as shown in the flowchart of FIG.

  In step S7001, the annotation list display for the user to paste the annotation is supported.

  In step S7002, the client side requests a list of available annotations on the server side.

  In S7003, select annotations permitted to the user who is currently opening the document from the annotation pasting permission / prohibition information in the annotation attribute information in the annotation data table registered in the attribute database 1110 on the server side, Information such as each annotation name and annotation volume is sent to the client side.

  In step S7004, the annotation list is displayed based on the annotation information received from the server.

  In S7005, the user selects an annotation.

  The annotation image selected in S7006 is displayed.

  In step S7007, the annotation image pasting position is moved with the pointing device to determine the position, and then an operation for saving the annotation is performed.

  In step S7008, the selected annotation and position information are sent to the server side as annotation information.

  In step S7009, the sent annotation information is additionally stored in the data table of the currently displayed document.

  The above is the annotation pasting process to the document.

  FIG. 8 is a diagram showing a flow of access right control based on the additional information of the annotation of the present invention.

  In the document management system, “administrator”, “user A”, “user B”, and “user C” are created.

  In S8001, the administrator creates an annotation “approval” on the annotation setting screen shown in FIG. In this annotation, it is assumed that pasting permission is given only to the user A as management information, and a document modification right is given to the user A and a document reading right is given to the user B as additional information.

  In S8002, user B registers document X according to the flow shown in FIG.

  In step S8003, the user A displays the document X according to the flow shown in FIG. 4, inspects the contents, and then pastes the “approval” annotation created in step S8001 according to the flow shown in FIG. Register according to the flow shown.

  In step S8004, when the user X tries to display the document X, the user A has the change right to display the document in order to follow the access right of the additional information of the “approval” annotation. If the user C tries to display the document, he / she has the right to read, so that the user C has the right to read.

[Second Embodiment]
The second embodiment of the present invention will be described below with reference to the drawings.

  FIG. 9 is a conceptual diagram of the data structure of the annotation data table registered in the attribute database 1110.

  9001 is an annotation data table in the attribute database 1110, and data of each annotation is arranged and stored on the table.

  9002 is individual annotation data in the annotation data table, which includes an annotation ID, attribute information, additional information, and volume data ID. The attribute information is an annotation name and this annotation pasted for each user managed by the document management system. Various information such as whether operation is permitted (or prohibited), and additional access right information is the access right of the document when this annotation is added for each user managed by the document management system The information and job addition information are information of a job to be executed when an annotation is added, and the volume data ID is an ID registered in the volume database 1109. Based on this ID, the volume information of the annotation is extracted from the volume database. Bets are possible.

  FIG. 10 is a diagram showing an example of a dialog screen for setting annotations in the document management system according to the second embodiment of the present invention.

  S10001 is an annotation setting dialog that is opened when the [Add] button in S6001 or an arbitrary annotation on the list is selected and the [Set] button is pressed. In this dialog, you can change the annotation name. Opens a dialog for selecting annotation diagrams, selecting permitted or prohibited users, setting access rights for documents with this annotation, and selecting jobs to be executed when this annotation is added to documents. be able to.

  S10002 is a dialog for selecting a job to be executed when this annotation is added, which is opened when the [Select Job] button is pressed in S10001. A job can be selected using a drop-down list box. In addition, a dialog for adding, deleting, and setting a job can be opened.

  S10003 is a dialog that is opened when the [Job List] button is pressed in S10002 to display jobs managed by the document management system, and to add, delete, and set jobs. The name of the currently set job is displayed on the list. Clicking the [Add] button opens a dialog for adding a new job. Select a job name on the list and press the [Set] button to open a dialog for setting the selected job. You can delete a job by selecting the job name on the list and clicking the [Delete] button.

  S10004 and S10005 are dialogs for setting a job that is opened when the [Add] button or the [Set] button is pressed in S10003. In this embodiment, as an example, it is possible to set the document printing operation and the mail notification operation, and the document printing setting and the mail notification setting are displayed separately in tabs.

  In step S10004, the document print tab of the job setting dialog is displayed, a check box for selecting whether to print the document, an edit box for setting the number of copies of the document, and at the time of printing the document. There is a check box for selecting whether to add an annotation.

  In step S10005, a mail notification tab of the job setting dialog is displayed, a check box for selecting whether to perform mail notification, a list for displaying a user to whom the mail notification is sent, and a user for mail notification There are [Add] and [Delete] buttons for adding and deleting, and radio buttons for setting mobilization for sending a document when sending mail. The user who notifies the mail can be selected from the users managed by the document management system, and is actually sent to the mail address stored in the user information in the document management system.

  FIG. 11 is a conceptual diagram of the data structure of the job data table registered in the attribute database 1110.

  11001 is a job data table in the attribute database 1110, and the data of each job is arranged and stored on the table.

  11002 is individual annotation data in the job data table, which includes a job ID, attribute information, document print information, and mail notification information. The attribute information is various information such as a job name, and the document print information is a document print information. Various information about the printing operation of the document, such as whether to perform printing, the number of copies, whether to add annotations when printing the document, etc. The email notification information is whether to notify the email, the destination of the email, the attachment of the document Various information about mail notification operations such as settings.

  FIG. 12 is a diagram showing a flow in the server and client of annotation pasting processing and job execution processing to a document in the document management system of the present invention.

<Annotation pasting and saving process>
The annotation pasting process will be described. The document is displayed as shown in the flowchart of FIG.

  In step S12001, the annotation list display for the user to paste the annotation is supported.

  In step S12002, the client side requests a list of available annotations on the server side.

  In S12003, select annotations permitted to the user who is currently opening the document from the annotation pasting permission / prohibition information in the annotation attribute information in the annotation data table registered in the attribute database 1110 on the server side, Information such as each annotation name and annotation volume is sent to the client side.

  In step S12004, an annotation list is displayed based on the annotation information received from the server.

  In S12005, the user selects an annotation.

  The annotation image selected in S12006 is displayed.

  In step S12007, the annotation image pasting position is moved with the pointing device to determine the position, and then an operation for saving the annotation is performed.

  In step S12008, the selected annotation and position information are sent to the server side as annotation information.

  In S12009, the sent annotation information is additionally stored in the data table of the currently displayed document.

  In step S12010, whether there is a job to be executed on the client side is determined from the job additional information of the annotation. If there is a job to be executed on the client side (document printing in this embodiment), the job is executed according to the job setting. (S12011).

  In step S12012, whether there is a job to be executed on the server side is determined from the job additional information of the annotation. If there is a job to be executed on the server side (e-mail notification in this embodiment), the job is executed according to the job setting. (S12013).

  The above is annotation pasting to a document, saving, and job execution processing.

  FIG. 13 is a diagram showing a flow of access right control based on additional information of an annotation according to the present invention.

  In the document management system, “administrator”, “user A”, “user B”, and “user C” are created.

  In S13001, the administrator creates an annotation “approval” on the annotation setting screen shown in FIGS. Only the user A is permitted to paste this annotation as management information. As access right additional information, a user A is given a document change right and a user B is given a document read right. A job for notifying user B of mail as job additional information is stored.

  In S13002, user B registers document Y according to the flow shown in FIG.

  In step S13003, the user A displays the document Y according to the flow shown in FIG. 4, inspects the contents, and pastes the “approval” annotation created in step S13001 according to the flow shown in FIG. Register according to the flow shown.

  In step S13004, the mail notification job is executed for the user B according to the flow shown in FIG. 12, so that the user B receives the mail and confirms that the document registered by the user B is approved by the user A.

  In step S13005, when the user X tries to display the document X, the user A has the change right to display the document in order to comply with the access right of the additional information of the “approval” annotation. If the user C tries to display the document, he / she has the right to read, so that the user C has the right to read, and if the user C tries to display the document, he / she does not have the right to access the document.

It is the figure which showed the system block of the document management system. It is a figure which shows the flow in a server and a client of a document registration process. It is a data structure conceptual diagram of the data registered in the attribute database. It is a figure which shows the flow in a server and a client of a document display process. It is a data structure conceptual diagram of the annotation data table registered in the attribute database. It is a figure which shows an example of the dialog screen for performing the setting of the annotation in a document management system. It is a figure which shows the flow in a server and a client of the annotation paste process to the document of a document management system. It is a figure which shows the flow of access right control by the additional information of an annotation. It is a data structure conceptual diagram of the annotation data table registered in the attribute database according to the second embodiment of the present invention. It is a figure which shows an example of the dialog screen for performing the setting of the annotation in the document management system of 2nd Example of this invention. It is a data structure conceptual diagram of the job data table registered in the attribute database. It is a figure which shows the flow in a server and a client of the annotation sticking process to the document of the document management system of 2nd Example of this invention. It is a figure which shows the access right control by the additional information of the annotation of 2nd Example of this invention, and the flow of job execution.

Explanation of symbols

1001 User interface unit 1002 Command control unit 1003 Device control unit 1004 File control unit 1005 External module communication unit 1006 Document management control unit 1007 Internal data storage unit 1008 File analysis unit 1009 Code document processing unit 1010 Image document processing unit 1011 Communication control unit 1101 Communication control unit 1102 Search control unit 1103 File analysis unit 1104 Code document processing unit 1105 Image document processing unit 1106 OCR engine 1107 Document management control unit 1108 Database control unit 1109 Volume database 1110 Attribute database 1111 Full text search database

Claims (6)

  In a document management system capable of registering, managing and extracting at least two types of image documents in a database, setting means for setting an image conversion method for each image format, and determining the format of an image file A document management system comprising: an analyzing unit capable of converting an image file; and an image converting unit for converting an image file, wherein the document is registered by performing image conversion according to an image format of the document to be registered.   At least two or more document extracting means and means for setting the image format of the document to be extracted for each means are provided. The document extracting means sets the image conversion format of the document, and the document is extracted according to the setting. 2. The document management system according to claim 1, wherein   The document management system according to claim 2, further comprising an attachment process to a mailer as one of the document extraction units.   2. The document management system according to claim 1, wherein when the image analysis unit determines that the image cannot be converted, the registered document is handled as a code document.   In a document management system capable of registering, managing, and extracting image documents in a database, storage means for storing document access control information as document management information, and document management information as annotation management information added to a document A storage unit that stores access control information and a management unit that restricts access to the document using the access restriction information. If an annotation is added to the document, access restriction in the annotation is used instead of the access restriction information in the document. A document management system that restricts access to a document using information.   In a document management system capable of registering, managing, and extracting image documents in a database, a storage unit that stores job information, a storage unit that stores job information as management information for annotations added to the document, and a job A document management system comprising execution means for executing a job according to information, and executing a job in the annotation management information when an annotation is added to the document.