JP2013178802A - Document management device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mechanism which, when managed documents are browsed in cooperative work of a plurality of persons, excludes documents already browsed and used by others to preferentially display documents which have not been browed by anybody.SOLUTION: A document management device connected to a client terminal so as to be able to communicate with the client terminal stores therein document data uniquely associating each document with distinction information capable of showing that the document has been browsed. When receiving a next document display request for display of documents having not been browsed, from the client terminal, the document management device selects one piece of the document data from the stored document data and determines whether the one selected piece of document data stored in document storage means has distinction information or not and, when the one selected piece is determined to not have distinction information, determines the one selected document data as document data which the client terminal from which the next document display request has been received is instructed to display.

Description

  The present invention relates to a document management apparatus, a control method, and a program.

  In recent years, the digitization of documents has progressed, and along with this, the task of checking the contents of digitized documents has occurred. In addition, it is considered that a digitized document is browsed by a plurality of users as a shared document.

  As one of them, Patent Document 1 discloses a document management method and apparatus for performing exclusive control that does not allow updates from users other than the viewing user when browsing an electronic document. As a feature, when a document is browsed from a certain user, the corresponding document is subjected to exclusive control that does not allow update from other users, and the exclusive state can be canceled only by the viewing user.

JP 2009-9240 A

  However, the document management method and apparatus described in Patent Document 1 allow exclusive control in units of documents, but do not take into account a business mode in which a large number of electronic documents are continuously confirmed. In particular, when viewing a large number of electronic documents, it is necessary to store what the user has browsed what documents for multiple users to confirm at the same time, it lacks that point.

  The invention of the present application is a mechanism that, when browsing a managed document by a collaborative work of a plurality of people, eliminates a read document occupied by another person and preferentially displays an unread document that no one has seen The purpose is to provide.

The present invention is a document management apparatus that is communicably connected to a client terminal, and stores, for each document, document data that uniquely associates a document with information that can identify that the document has been viewed. The document storage means, the next document display request receiving means for receiving a next document display request for displaying an unread document from the client terminal, and the document storage means storing the next document display request when the next document display request is received. A document reading unit for selecting one document data from the document data to be checked, and a browsing for determining whether or not the identifiable information exists in the selected one document data stored in the document storage unit When it is determined that there is no information determination unit and the browsing information determination unit, the selected one document data is instructed to be displayed to the client terminal that has received the next document display request. Characterized in that it comprises the unread determination means for determining a document data.
Further, the identifiable information is user information for viewing a document.

  The unread document display request receiving means further receives user information from the client terminal together with the next document display request, and the unstored document determination means determines the document data to be displayed when the unread document determination means determines the document data to be displayed. It further comprises browsing information registration means for registering the received user information as the identifiable information in the determined document data stored in the means.

  In addition, a previous document display request receiving unit that receives a previous document display request including user information to display a browsed document from the client terminal, and the document storage unit when the previous document display request is received. The already-read document selecting means for selecting one document data from the document data stored in the memory and the one document data selected by the read document selecting means stored in the document storage means can be identified. It is determined that the determination result of the first read user determination unit that determines whether the information and the user information included in the previous document display request match and the determination result of the first read user determination unit match In such a case, the already-read document determination means for determining one document data selected by the read document selection means as document data to be displayed on the client terminal that has received the previous document display request. When, and further comprising a.

  Further, when the browsing information determination means determines that there is the identifiable information, the identifiable information of one document data selected by the unread document selection means stored in the document storage means, The apparatus further comprises second read user determination means for determining whether or not the user information received by the previous document display request reception means matches, and the unread document determination means includes the second read user determination means. When it is determined that they match, one document data selected by the unread document selection unit is determined as document data to be displayed on the client terminal that has received the next document display request.

Further, the document data in the document storage means further stores the document and past browsing history information uniquely associated with each other, and the browsing information determination means determines that there is no identifiable information, and determines the unread document determination. The browsing history determination means for determining whether or not the browsing history information is present in the document data determined by the means, and when it is determined that there is the browsing history determination means, the fact that the document is an unread document having a browsing history Notification means for notifying the client terminal that has received the document display request;
Is further provided.

  Further, the document data of the document storage means further stores the document and the number assigned to the document uniquely associated with each other, and the ordered number is selected when the unread document selection means selects one document data. It is characterized by selecting according to.

  In the present invention, when a managed document is browsed by a collaborative work of a plurality of people, a mechanism that can preferentially display an unread document that no one else has seen, excluding a read document occupied by another person Can be provided.

It is a figure which shows the structure of an account application form image processing system. It is a figure which shows the hardware constitutions of the various terminals in an account application form image processing system. It is a figure which shows the login flow of an account application form image processing system. It is a figure which shows the unregistered search flow of an account application form image processing system. It is a figure which shows the unregistered search flow (2) of an account application form image processing system. It is a figure which shows the unregistered search flow (3) of an account application form image processing system. It is a figure which shows the browsing document determination flow of an account application form image processing system. It is a figure which shows the registration status confirmation flow of an account application form image processing system. It is a figure which shows the front image display flow of an account application form image processing system. It is a figure which shows the next image display flow of an account application form image processing system. It is a figure which shows the browsing unregistered confirmation flow of an account application form image processing system. It is a figure which shows the same condition re-search flow of an account application form image processing system. It is a figure which shows the login screen of an account application form image processing system. It is a figure which shows the main menu screen of an account application form image processing system. It is a figure which shows the unregistered search condition input screen of an account application form image processing system. It is a figure which shows the document image screen of an account application form image processing system. It is a figure which shows the registration status confirmation screen of an account application form image processing system. It is a figure which shows the browsing unregistered document presence notification screen of an account application form image processing system. It is a figure which shows the same condition re-search notification screen of an account application form image processing system. It is a figure which shows the search condition applicable screen of an account application form image processing system. It is a figure which shows the login failure screen of an account application form image processing system. It is a figure which shows an example of the user table (login user management table) of an account application form image processing system. It is a figure which shows an example of the document table (document information management table) of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a figure which shows an example of multiple user simultaneous use of an account application form image processing system. It is a modification of the document table of FIG. It is a modification of the processing of the document management apparatus when the next image button is pressed. It is a modification of the processing of the document management apparatus when the previous image button is pressed. This is a process of the document management apparatus when the end of browsing is pressed.

  Referring to FIG.

FIG. 1 shows a document management server (document management apparatus) 100 suitable for a document management system (account application form image processing system) according to the present invention, a user A client terminal 200, and a user B client terminal 201 connected to be communicable. 1 is a system configuration diagram of a document management system configured as described above. FIG.
Reference numerals 202 and 203 denote employees (hereinafter referred to as user A and user B, respectively) who are users of this system, and use different client terminals.

A client terminal 200 is used by the user A 202 to use the account application form image processing system. The client terminal 200 can transmit / receive data to / from the document management server 100 via the network.
Similarly, another terminal 201 can transmit and receive data to and from the document management server 100 via the network.
FIG. 2 will be described.
FIG. 2 is a diagram illustrating a hardware configuration of the document management server 100, the client terminal 200, and the client terminal 201.

  In FIG. 2, 401 is a CPU that comprehensively controls each device and controller connected to the system bus 404. Further, the ROM 402 or the external memory 411 is necessary to realize a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS) that is a control program of the CPU 401 and a function executed by each server or each PC. Various programs to be described later are stored.

  Reference numeral 403 denotes a RAM which functions as a main memory, work area, and the like for the CPU 401. The CPU 401 implements various operations by loading a program necessary for execution of processing from the ROM 402 or the external memory 411 into the RAM 403 and executing the loaded program.

  An input controller 405 controls input from a keyboard (KB) 409 or a pointing device such as a mouse (not shown). A video controller 406 controls display on the display unit 410. The display unit 410 is not limited to the CRT but may be another display such as a liquid crystal display. These are used by the administrator as needed. Further, the display unit may include a touch panel function in which the user specifies a target position in the display screen with a finger, a pen, or the like.

  Reference numeral 407 denotes a memory controller, which is connected via an adapter to a hard disk (HD), flexible disk (FD), or PCMCIA card slot for storing a boot program, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 411 such as a compact flash (registered trademark) memory.

  Reference numeral 408 denotes a communication I / F controller that is connected to and communicates with an external device via the network (communication line) 300, and executes communication control processing in the network. For example, communication using TCP / IP is possible.

  Note that the CPU 401 enables display on the CRT by executing, for example, outline font rasterization processing on the display information area in the RAM 403. In addition, the CPU 401 enables a user instruction with a mouse cursor (not shown) on the CRT.

Various programs to be described later for realizing the present invention are recorded in the external memory 411 of the document management server 100, and are executed by the CPU 401 by being loaded into the RAM 403 as necessary. Further, a data file and a data table used when the above program is executed are also stored in the external memory 411 or the storage means of the document management server 100, and a detailed description thereof will be described later.
Next, various processing flows of the account application form image processing system will be described with reference to FIGS.

As described above, the client terminal 200 and the document management server (hereinafter referred to as a server) 100 are connected to each other via a network. Then, the client terminal 200 executes various processes via various operation screens that the server 100 instructs to display.
FIG. 3 will be described.

  FIG. 3 shows a process in which a user sends a login request (1303 in FIG. 13) to log in to the account application form image processing system of the present invention from the client terminal after the login screen (FIG. 13) is displayed on the client terminal. Is the details.

In FIG. 3, when the login screen of FIG. 13 is displayed on the client terminal 200, a login request (1302 in FIG. 13) is sent from the client terminal 200 to the document management system, and the document management server 100 sends the main menu to the client terminal. This is a process for instructing display on the screen (FIG. 14).
In step 1001, the client terminal 200 transmits a login screen (FIG. 13) display request to the server 100.
In step 1002, the server 100 receives the login screen (FIG. 13) display request transmitted from the client terminal 200.
In step 1003, the server 100 transmits a login screen (FIG. 13) to the client terminal 200.

  In step 1004, the client terminal 200 receives the login screen (FIG. 13) transmitted from the server 100, and displays the login screen (FIG. 13) on the display unit. The login screen (FIG. 13) includes a user ID input unit (1301), a login button (1302), and an end button (1303).

In step 1005, the client terminal 200 inputs the user ID of the user 202 from the client terminal 200 to the user ID input unit (1301) on the displayed login screen (FIG. 13), and the login button (1302). ) Is pressed.
In step 1006, the client terminal 200 transmits a user ID (user information) to the document management server 100.
In step 1007, the server 100 receives the user ID transmitted from the client terminal 200.

  In step 1008, the server 100 collates the received user ID with a user ID (2202) in a user table (FIG. 22) registered in advance that can log in to the document management system of the present invention.

  In step 1009, if the user corresponding to the user ID received from the client terminal 200 does not exist in the user table (FIG. 22), the server 100 transmits a login failure screen (FIG. 21) to the client terminal 200.

In step 1010, the client terminal 200 receives the login failure screen (FIG. 21) from the server 100 and displays the login failure screen (FIG. 21). The login failure screen (FIG. 21) includes a message indicating that the login has failed and an OK button (2101).
In step 1011, after the OK button (2101) is pressed on the client terminal 200, the user ID is input again.

  In step 1012, if a user corresponding to the user ID received from the client terminal 200 exists in the user table (FIG. 21), the server 100 transmits a main menu screen (FIG. 14) to the client terminal 200.

In step 1013, the main menu screen (FIG. 14) is received from the server 100, and the client terminal 200 displays the main menu screen (FIG. 14) on the display unit. The main menu screen (FIG. 14) includes an unregistered search button (1401) and a registered search button (1402).
FIG. 4 will be described.

  FIG. 4 shows the details of the processing for transmitting an unregistered image search request (1503 in FIG. 15) from the client terminal after the unregistered search condition input screen (FIG. 15) is displayed on the client terminal.

In step 2001, the client 202 presses an unregistered search button (1401) from the client terminal 200 on the main menu screen (FIG. 14) displayed on the client terminal 200. When the unregistered search button (1401) on the main menu screen (FIG. 14) displayed by the client terminal 200 is pressed, a display request for an unregistered search condition input screen (FIG. 15) is transmitted to the server 100.
In step 2002, the client terminal 200 transmits a display request for an unregistered search condition input screen (FIG. 15) to the server 100.
In step 2003, the server 100 receives a display request for an unregistered search condition input screen (FIG. 15).
In step 2004, the server 100 transmits an unregistered search condition input screen (FIG. 15) to the client terminal 200.

  In step 2005, the client terminal 200 receives the unregistered search condition input screen (FIG. 15) from the server 100, and the client terminal displays the unregistered search condition input screen (FIG. 15) on the display unit.

  The unregistered search condition input screen (FIG. 15) includes a financial institution code input unit (1501), a data status selection unit (1502), a search button (1503), and a return button (1504).

In step 2006, the client terminal 200 displays the unregistered search condition input screen (FIG. 15) displayed on the client terminal 200 by the user 202 from the client terminal 200 to the financial institution code input unit (1501), and the data status is displayed. The data status selection unit (1502) is selected, and the search button (1503) is pressed. The data status selection section can be selected from “unregistered” or “unconfirmed (unread)”.
In step 2007, the search condition is transmitted to the server 100. In the data status selection section, “unconfirmed (unread)” is selected and transmitted.

  In step 2008, when “unconfirmed (unread)” is selected and transmitted, the server 100 receives “unconfirmed (unread)”, which is a data status search condition transmitted from the client terminal 200.

  Further, when “unregistered” is selected and transmitted, the server 100 receives “unregistered” and user information that are data status search conditions transmitted from the client terminal 200.

In step 2009, the server 100 collates the document that matches the received search condition with the financial institution code (2303) and the data status (2304) in the document table (FIG. 23). First, the financial institution code in the document table (FIG. 23) is collated with the received financial institution code. When there is no input in the financial institution code input part (1501), it is not collated.
Next, the data status selected by the data status selection unit is collated with the data status in the document table (FIG. 23).
Hereinafter, there are two cases of search conditions transmitted from the client terminal and received by the server 100: “unregistered” and “unconfirmed (unread)”.

  In the first case, when the received data status is “unregistered”, the data status in the document table is “unconfirmed (unread)”, “viewing (read)”, “viewed (read)” This means that it matches the document of document NO (document NO). 5, 6, 7, 8, 11, and 12 will be described when the received data status is “unregistered”. “Unregistered” used in the search condition means that the confirmation button (1607 in FIG. 16) is not pressed and the data status in the document table is not “confirmed”.

  In the second case, when the received data status is “unconfirmed (unread)”, this means that the data status in the document table matches the document NO document with “unconfirmed (unread)”. 9 and 10 will be described in the case where the received data status is “unconfirmed (unread)”.

  That is, when the received data status is “unconfirmed (unread)”, the inquirer ID in the document table (FIG. 23) is confirmed, and it is verified whether it is blank. In other words, all document NOs in which the document NO (unread document information) and the user information (inquirer ID) who viewed the document NO are not associated are searched from the document table (unread document search means).

  In step 2010, if there is no document corresponding to the search condition received from the client terminal 200 in the document table (FIG. 23), the server 100 transmits a no search condition corresponding document screen (FIG. 20) to the client terminal 200. .

In step 2011, the client terminal 200 receives the search condition relevant document no screen (FIG. 20) transmitted from the server 100, and displays the search condition relevant document no screen (FIG. 20). The search condition applicable document non-screen (FIG. 20) includes a message indicating that there is no document corresponding to the search condition and an OK button (2001).
In step 2012, the client terminal 200 presses the OK button (2001) on the search condition applicable document no screen (FIG. 20), and then inputs the search condition again.

  In step 2013, the server 100 associates all the document NOs retrieved by the unread document retrieval unit from the document table with the user information that matches the user information received in step 1007 in the user table (FIG. 22). Registered in the target (unread document target for each user) (2203 in FIG. 22) (unread document information registration means).

As described in step 2009, collation is performed for all documents in the document table (FIG. 23) based on the received search conditions. As a result of the collation, the document NO of the document that matches the search condition is registered in the unregistered browsing target (2203 in FIG. 22) in the user table (FIG. 22).
FIG. 5 will be described.

  In FIG. 5, after the unregistered search condition input screen (FIG. 15) is displayed on the client terminal, “unregistered” is selected from the data status selection unit of the client terminal, and an unregistered image search request (1503 in FIG. 15). Is transmitted, the unregistered image that is instructed to be displayed on the client terminal by the document management server is determined, and details of processing for instructing to display the determined unregistered image are described.

In step 3001, the server 100 determines a document to be displayed on the client terminal 200. The flow of browsing document determination will be described later in order to explain the details in FIG.
In step 3002, the server 100 creates a document image screen (FIG. 16) of the document to be displayed on the client terminal 200 determined in step 3001.
In step 3003, the server 100 transmits a document image screen (FIG. 16) to the client terminal 200.
In step 3004, the client terminal 200 receives the document image screen (FIG. 16) transmitted from the server 100.

The document image screen (FIG. 16) includes an image display unit (1601), a document number display unit (1602), a file name display unit (1603), a document information display unit (1604), a previous image button (1605), and a next image button (1606). ), A confirmation button (1607), a registration status button (1608), a re-search button (1609), and a menu button (1610).
FIG. 6 will be described.

  In FIG. 6, when the document image screen (FIG. 16) is displayed on the client terminal, a confirmation registration request (1607 in FIG. 16) is transmitted from the client terminal, and an unregistered image that the document management server instructs the client terminal to display is displayed. This is a process of registering that the user has confirmed.

In step 4001, the user 202 confirms the content of the document image screen (FIG. 16) displayed on the client terminal 200, and presses the confirmation button (1607) on the document image screen (FIG. 16) when there is no problem with the content. To do.
In step 4002, the client terminal 200 transmits an unregistered document registration request to the server 100.
In step 4003, the server 100 receives an unregistered document registration request.

  In step 4004, the server 100 updates the data status (2304) in the document table (FIG. 23) from “browsing” to “confirmed” for the document requested to be registered.

In step 4005, the server 100 determines a document to be displayed next on the client terminal 200. The browsing document determination flow will be described later in order to explain the details in FIG.
In step 4006, the server 100 creates a document image screen (FIG. 16) to be displayed next on the client terminal 200.
In step 4007, the server 100 transmits a document image screen (FIG. 16) to be displayed on the client terminal 200.

In step 4008, the client terminal 200 receives the document image screen (FIG. 16) transmitted from the server 100 and displays the document image screen (FIG. 16). Thereafter, the process returns to step 4001.
In step 4009, the user presses the registration status button (1608) on the document image screen (FIG. 16) displayed on the client terminal 200.
In step 4010, the user presses the previous image button (1605) on the document image screen (FIG. 16) displayed on the client terminal 200.
In step 4011, the user presses the next image button (1606) on the document image screen (FIG. 16) displayed on the client terminal 200.
In step 4012, the user presses the browse end button (1611) on the document image screen (FIG. 16) displayed on the client terminal 200.
FIG. 7 will be described.

  In FIG. 7, after the unregistered search condition input screen (FIG. 15) is displayed on the client terminal, “unregistered” is selected from the data status selection unit of the client terminal, and an unregistered image search request (1503 in FIG. 15). Is a detail of processing for determining an unregistered image to be displayed on the client terminal by the document management server when the message is transmitted.

FIG. 7 is a flowchart for explaining details of Step 3001 and Step 4005 for determining a document (unregistered image) to be browsed by the server 100 with respect to the client terminal 200.
In step 8001, the server 100 confirms the unregistered browsing target (2203) of the user 202 in the user table (FIG. 22).

  In step 8002, the server 100 determines that there is no target document as a result of checking the unregistered browsing target (2203) of the user 202 in the user table (FIG. 22). The process returns to the transmission process of the condition not applicable document no screen (FIG. 20).

  In step 8003, when the server 100 confirms the unregistered browsing target (2203) of the user 202 in the user table (FIG. 22), if the target document exists, the data in the document table (FIG. 23) of the target document. The status (2304) is confirmed.

To confirm the data status, the document numbers of the browsing target documents registered in the unregistered browsing target in the user table (FIG. 22) are checked in descending order. If the data status of the confirmed document NO is “unconfirmed” or “viewed”, the process proceeds to step 8004. If the data status is “browsing” or “confirmed” as a result of the confirmation, the document of the next document NO is confirmed.
In step 8004, the server 100 confirms the referrer ID (2305) of the corresponding document in the document table (FIG. 23).

  In step 8005, when the server 100 confirms the referrer ID (2305) of the target document, if the referrer ID (2305) of the corresponding document is a user ID other than the user, the currently confirmed document is the final document. If it is not the final document, the process returns to step 8003. If the document being confirmed is the final document, the flow proceeds to a browsed unregistered confirmation flow described in step 9001 and subsequent steps.

  In step 8006, if the referrer ID (2305) of the corresponding document in the document table (FIG. 23) is blank or the own user ID, the server 100 determines the corresponding document as a browsing target document.

In step 8007, after determining the browse document, the server 100 updates the data status in the document table (FIG. 23) to “being browsed”, and registers the user information “own user ID” received in step 2008 as the referrer ID. .
FIG. 8 will be described.

In FIG. 8, when the document image screen (FIG. 16) is displayed on the client terminal, a registration status display request (1608 in FIG. 16) is transmitted from the client terminal, and the document management server sends the registration status screen (FIG. 17) to the client terminal. ) Is a display instruction.
In step 4009, the client terminal 200 presses the registration status confirmation button (1608) on the currently displayed document image screen (FIG. 16).
In step 5001, when the registration status confirmation button (1608) is pressed on the client terminal 200, a registration status confirmation request is transmitted to the server 100.
In step 5002, the server 100 receives a registration status confirmation request from the client terminal 200.
In step 5003, the server 100 acquires information on all documents in the document table (FIG. 23).
In step 5004, the server 100 creates a registration status screen (FIG. 17) based on the acquired document information.
In step 5005, the server 100 transmits the created registration status screen (FIG. 17) to the client terminal 200.

In step 5006, the client terminal 200 receives the registration status screen (FIG. 17) transmitted from the server 100, and the registration status screen (FIG. 17) is displayed on the client terminal 200. The registration status screen (FIG. 17) includes a registration status display section (1701) and a close button (1702).
FIG. 9 will be described.

FIG. 9 shows a case where a document image screen (FIG. 16) is displayed on the client terminal after “unconfirmed (unread)” is selected from the data status selection unit of the client terminal and an unconfirmed image search request (not shown) is transmitted. In this process, a previous image display request (1605 in FIG. 16) is transmitted from the client terminal, and the document management server determines a previous image (read document) to be displayed on the client terminal.
Note that the process for determining a read document described in FIG. 9 is not limited to the document to be determined, and may be a process for determining image data and a file.
In step 4010, the client terminal 200 presses the previous button (1605) on the currently displayed document image screen (FIG. 16).
In step 6001, the client terminal 200 transmits a previous image display request to the server 100.

  In step 6002, the server 100 receives a previous image display request from the client terminal 200 to display the user information and the read document NO (unread document) again (previous document display request receiving means).

  In step 6003, when the server 100 receives the previous image display request, the server 100 acquires the document NO of the document being displayed on the client terminal 200, and the document NO registered in the unregistered browsing target in the user table (FIG. 22). Thus, the document number immediately preceding the document number of the currently viewed document is acquired. That is, the document NO (unread document information) associated with the user information that matches the user information received from the user table is selected as the first read document information (read document selection means).

  Next, the inquirer ID in the document table (FIG. 23) is confirmed. The inquirer ID (2305) of the document No. (2301) in the document table (FIG. 23) is confirmed. That is, it is determined whether the user information (inquirer ID) associated with the document NO selected from the document table matches the received user information (determination result) (read user determination unit).

  When it is determined that the read user determination unit does not match, the document NO is associated with the user information that matches the user information received from the user table and does not match the document NO that has already been selected (other than). The document NO is selected as the second read document information (read document selection means).

  The document No. document of the previous one (the next unread document information not selected) among the document Nos registered in the unregistered browsing target in the user table (FIG. 22) is confirmed. It is assumed that the process of selecting this document NO is repeated until the document to be browsed is determined.

  In step 6004, if the referrer ID (2305) before the displayed document NO (2301) confirmed in step 6003 is the self user ID, the server 100 determines the corresponding document as a viewed document (read document). That is, when it is determined that the read user determination unit matches, the selected document NO is determined as the document NO to be displayed on the client terminal that has received the user information (read document determination unit).

When the browse document is determined, the server 100 changes the data status of the document NO currently being browsed in the document table (the client terminal that has received the user information is currently being displayed) from “browsing (read)” to “viewed (read) ) ”, The data status of the document NO determined to be browsed is updated from“ Browsed (read) ”to“ Browsing (read) ”.
In step 6005, a document image screen (FIG. 16) of the document NO (including the read document) determined in step 6004 is created.

  In step 6006, the server 100 transmits the created document image screen (FIG. 16) to the client terminal 200 for display instruction to the client terminal 200.

In step 6007, the client terminal 200 receives the document image screen (FIG. 16) transmitted from the server 100, and the client terminal 200 displays the document image screen (FIG. 16) on the display unit.
FIG. 10 will be described.

FIG. 10 shows a case where the document image screen (FIG. 16) is displayed on the client terminal after “unconfirmed (unread)” is selected from the data status selection unit of the client terminal and an unconfirmed image search request (not shown) is transmitted. In this process, the next image display request (1606 in FIG. 16) is transmitted from the client terminal, and the document management server determines the next image (unread document) to be displayed on the client terminal.
Note that the process of determining an unread document described in FIG. 10 is not limited to the document to be determined, and may be a process of determining image data and a file.
In step 7001, the client terminal 200 transmits a next image display request to the server 100.

  In step 7002, the server 100 receives a next image display request from the client terminal 200 as a request for displaying user information and the next unread document (next document display request receiving means).

  In step 7003, when the server 100 receives the next image display request, the server 100 acquires the document NO of the document being displayed on the client terminal 200, and the document NO registered in the unregistered browsing target in the user table (FIG. 22). Thus, the document NO immediately after the document NO of the document currently being browsed is acquired. That is, the document NO (unread document information) associated with the user information that matches the user information received from the user table is selected as the first unread document information (unread document selection means).

  Next, the inquirer ID in the document table (FIG. 23) is confirmed. The inquirer ID (2305 in FIG. 23) of the document No. 2301 in the document table (FIG. 23) is confirmed. That is, a document NO that matches the document NO selected as the first unread document information from the document table is searched, and whether there is user information (referer ID) already associated with the searched document NO (judgment result) ) (Browser information determination means).

  If it is determined that there is a viewer information determination unit, the document NO is associated with user information that matches the user information received from the user table and does not match the document NO that has already been selected (other than) NO is selected as the second unread document information (unread document selection means).

  Confirmation of the document No. that is one more later (next unread document information not selected) among the document Nos registered in the unregistered browsing target in the user table (FIG. 22) is performed. It is assumed that the process of selecting this document NO is repeated until the document to be browsed is determined.

  When the last document among the document NOs registered in the unregistered browsing target in the user table (FIG. 22) is checked and there is no document to be checked next (when it cannot be selected), when the browsing is completed, which will be described later Proceed to the flow.

In step 7004, the server 100 determines the corresponding document as a browsed document (unread document) when the document NO (2301) next to the displayed document NO (2301) confirmed in step 6003 is blank. That is, when it is determined that there is no viewer information determination means, the selected document NO is determined as the document NO to be displayed on the client terminal that has received the user information (unread document determination means).
As a result, it is possible to preferentially determine a document that is not being browsed by another user, and to eliminate simultaneous access by other users in response to an unread document display request.

When the browse document is determined, the server 100 changes the data status of the document NO currently being browsed in the document table (the client terminal that has received the user information is currently being displayed) from “browsing (read)” to “viewed (read) ) ”, The data status of the document NO that has been determined to be browsed is updated from“ unconfirmed (unread) ”to“ browsing (read) ”. Further, the received “own user ID” is registered in the inquirer ID of the document table in association with the determined document NO (viewer information registering means).
In step 7005, a document image screen (FIG. 16) of the document NO (including unread document) determined in step 7004 is created.

  In step 7006, the server 100 transmits the created document image screen (FIG. 16) to the client terminal 200 for display instruction to the client terminal 200.

  In step 7007, the client terminal 200 receives the document image screen (FIG. 16) transmitted from the server 100, and the client terminal 200 displays the document image screen (FIG. 16) on the display unit.

FIGS. 11 and 12 show a document image screen (FIG. 16) in which the last document is displayed among the documents to be browsed in the user table (FIG. 22) on the client terminal 200, or the next image button (1606) or It is the figure which showed the flow at the time of depressing a confirmation button (1607).
FIG. 11 will be described.

FIG. 11 shows a case where there is an unregistered image to which a confirmation registration request is to be made when a confirmation registration request (1607 in FIG. 16) is transmitted from the client terminal after the document image screen (FIG. 16) is displayed on the client terminal. It is processing.
In step 9001, since the server 100 determines that the document being viewed is the final document, the server 100 updates the data status in the document table (FIG. 23).

  If it is determined that the document is the final document in step 8005 of the browse document determination flow (FIG. 12), “browsing” is changed to “confirmed”, and if it is determined that the document is the final document in step 7003, “reading”. Update to “Viewed”.

  In step 9002, the server 100 has the referrer ID (2305) as the own user among the documents to be browsed in the user table (FIG. 22), and the data status (2304) has been browsed. Check for documents.

  If not, go to Step 9003. Of the documents of document NO registered in the unregistered browsing target in the user table (FIG. 22), the data status of all documents whose inquirer ID is the own user in the document table (FIG. 23) is “confirmed”. In this case, the process proceeds to the same condition re-search flow. The same condition re-search flow will be described later with reference to FIG.

  In step 9003, the server 100 confirms in step 9001. As a result, the inquirer ID (2305) among the documents that are the browsing target document (2203) in the user table (FIG. 22) is the user, and the data status When there is a document that has been browsed (2304), a browsed unregistered document presence notification screen (FIG. 18) is transmitted to the client terminal.

In step 9004, the client terminal 200 receives the browsed unregistered document presence notification screen (FIG. 18) transmitted from the server 100, and the client terminal 200 displays the browsed unregistered document presence notification screen (FIG. 18). The browsed unregistered document presence notification screen (FIG. 18) includes a message that there is a browsed and unregistered document, a Yes button (1801), and a No button (1802).
In step 9005, the client terminal 200 depresses the Yes button (1801) and returns to the browse document determination flow.
In Step 9006, the client terminal 200 presses the No button (1802).
In step 9007, the client terminal 200 transmits a browsing information release request.
In step 9008, the server 100 receives the browsing information release request transmitted from the client terminal 200.

In step 9009, the server 100 has browsed the browsing target document (2203) in the user table (FIG. 22) and the data status (2304) in the document table (FIG. 23) and the referrer ID (2305). The data status (2304) and inquirer ID (2305) of the document of the corresponding user are made empty.
FIG. 12 will be described.

  FIG. 12 shows the next undisplayed instruction that the document management server instructs the client terminal to display when the confirmation registration request (1607 in FIG. 16) is transmitted from the client terminal after the document image screen (FIG. 16) is displayed on the client terminal. This is processing when there is no registered image.

  In step 10001, the server 100 is the user who has the referrer ID (2305) among the documents that are the browsing target documents (2203) in the user table (FIG. 22), and the data status (2304) is all confirmed. In this case, the same condition search screen (FIG. 19) is transmitted to the client terminal 200.

In step 10002, the client terminal 200 receives the same condition measure search screen transmitted from the server, and the client terminal 200 displays the same condition measure search screen (FIG. 19). The same condition measure search screen (FIG. 19) is composed of a message indicating that a re-search is performed under the same conditions, a YES button (1901), and a NO button (1902).
If the YES button (1901) is pressed, the process returns to step 2007.
If the NO button (1902) is pressed, the process returns to step 2010.
FIG. 13 will be described.
FIG. 13 is a login screen that the server 100 instructs to display in step 1003 of FIG.
1301 A login screen user ID input unit inputs a user ID used for login.
1302 Login screen The login button is used to log in to the system after entering the login ID in the login screen user ID input unit.
1303 The login screen end button is used to end the system.
FIG. 14 will be described.
FIG. 14 is a main menu screen that the server 100 instructs to display in step 1012 of FIG.
1401 Main menu screen unregistered search button is used to display a search condition input screen (FIG. 15).
1402 The main menu screen book registration search button is omitted in the present invention.
FIG. 15 will be described.
FIG. 15 is an unregistered search condition input screen that the server 100 instructs to display in step 2004 of FIG.
1501 Unregistered search condition input screen The financial institution code input unit inputs a financial institution code used as a search condition.
1502 The unregistered search condition input screen data status selection unit selects a data status to be used as a search condition from unregistered and unconfirmed.

1503 An unregistered search condition input screen search button is used to search for a document in the document table (FIG. 23) after a search condition is input in the search condition input screen financial institution code input section and search condition input screen data status selection section. To do.
1504 The unregistered search condition input screen return button is used to transition to the main menu screen (FIG. 14).
FIG. 16 will be described.

  FIG. 16 is a document image screen that the server 100 instructs to display in step 3003 in FIG. 5, step 4007 in FIG. 6, step 6006 in FIG. 9, and step 7006 in FIG.

1601 A document image screen image display unit displays an image of a document (an image of an account application form) in a document table determined to be browsed in the browse document decision flow.
1602 Document image screen The document number display section displays what document is being displayed among unregistered browsing targets in the user table (FIG. 22).
1603 The document image screen file name display section displays the file names in the document table (FIG. 23).
1604 Document image screen The document information display unit displays the financial institution code, the data status, and the inquirer ID in the document table (FIG. 23).

  1605 An image button before the document image screen displays a document immediately before the document No. of the currently displayed document among the documents registered as unregistered browsing targets in the user table (FIG. 22).

  1606 Document image screen The next image button displays a document immediately after the document No. of the currently displayed document among the documents registered as unregistered browsing targets in the user table (FIG. 22). The data status in the document table (FIG. 23) of the document being browsed at that time is updated to browsed.

1607 The document image screen confirmation button displays a document immediately after the document NO of the currently displayed document among the documents registered as unregistered browsing targets in the user table (FIG. 22). Note that the data status in the document table (FIG. 23) of the document being browsed at that time is updated to “confirmed”.
1608 The document image screen registration status confirmation button displays information on all documents registered in the document table.

  1609 The document image screen re-search button transits to a search condition input screen (FIG. 15). When the unregistered browsing target in the user table (FIG. 22) and the data status in the document table (FIG. 23) are not confirmed, the data status and the inquirer ID are reset.

1610 The button to the document image screen menu changes to the main menu screen (FIG. 14). When the unregistered browsing target in the user table (FIG. 22) and the data status in the document table (FIG. 23) are not confirmed, the data status and the inquirer ID are reset.
1611 is a browsing end button, and is pressed by the user in step 4012 of FIG. 6 when the user ends the browsing operation of the unread document and the read document.

1612 New unread display information, which is displayed together with the image of the account application form when it is determined that it is step 109 in FIG. If it is determined that it is not step 109 in FIG. 35, only the image of the account application form is displayed (new unread display information is not displayed).
FIG. 17 will be described.
FIG. 17 is a registration status confirmation screen that the server 100 instructs to display in step 5005 of FIG.
1701 Registration status confirmation screen The registration status display section displays all items in the document table (FIG. 23).
1702 The registration status confirmation screen close button closes the registration status confirmation screen (FIG. 17).
FIG. 18 will be described.
FIG. 18 is a browsed unregistered document existence notification screen that the server 100 instructs to display in step 9003 of FIG.
1801 Browsing unregistered document existence notification screen The Yes button displays the top document image of the unregistered browsing target in the user table (FIG. 22).

1802 Browsing unregistered document existence notification screen Transition to the search condition input screen (FIG. 15) by clicking the No button. When the unregistered browsing target in the user table (FIG. 22) and the data status in the document table (FIG. 23) are not confirmed, the data status and the inquirer ID are reset.
FIG. 19 will be described.
FIG. 19 is the same condition measure search screen that the server 100 instructs to display in step 10001 of FIG.
1901 The same condition measure search screen Yes button searches documents in the document table (FIG. 23) with the same search condition.
1902 Same condition measure search screen No button transits to the search condition input screen (FIG. 15).
FIG. 20 will be described.
FIG. 20 shows a search condition applicable document no screen that the server 100 instructs to display in step 2010 of FIG.
2001 Search condition applicable document no screen OK button transits to the search condition input screen (FIG. 15).
FIG. 21 will be described.
FIG. 21 is a login failure screen that the server 100 instructs to display in step 1009 of FIG.
2101 The login failure screen OK button transits to the login screen (FIG. 13).
FIG. 22 will be described.

  FIG. 22 is a diagram showing a user table (user unread management storage means) stored as a database (DB) in the document management server (document management apparatus) 100 according to the present invention. The user unread management storage unit stores the user information and the unread document information that is not browsed by the user in association with each user.

The user table stores a user number (2201), a user ID (2202), and an unregistered browsing target (2203). User NO (2201) stores a number assigned to each user who uses the present system stored in the user table. The user ID (2202) stores a user ID assigned to each user who uses the system when logging in to the system. The usage form of the user ID at the time of login will be described later. The unregistered browsing target (2203) is the document number (2301) of the document that is the browsing target that matches the search condition when the user using the system searches and browses the digitized document using the system. Remember. The usage mode of the unregistered browsing target (2203) when browsing the document will be described later.
2201 User table user NO memorize | stores the number allocated for every user.
2202 The user table user ID stores a user ID for each user.
2203 The user table unregistered browsing target stores a browsing target document for each user.
FIG. 23 will be described.

  FIG. 23 is a diagram showing a document table (document table) (unread document management storage means) stored as a database (DB) in the document management server (document management apparatus) 100 according to the present invention. The unread document management storage means stores unread document information and user information that browses the unread document in a uniquely associated manner.

  The document table stores a document number (2301), a file name (2302), a financial institution code (2303), a data status (2304), and an inquirer ID (2305).

  The document number (2301) stores a number assigned to each document stored in the document management server 100 of this system. The document number (2301) is used as an unregistered browsing target (2203) in the user table (FIG. 22).

  The file name (2302) stores the file name of the document stored in the document management server of this system. The file name (2302) is used for a file name display section (1603) of a document image screen (FIG. 16) described later.

  The financial institution code (2303) stores a search condition used when a user using the system searches the document stored in the document management server of the system using the system.

The data status (2304) stores a search condition used when a user using the system searches for a document stored in the document management server of the system using the system. The data status (2304) stores the confirmation status at the time when the user who uses the system browses the document using the system and confirms the consistency of the document. Details will be described later.
The following four types are stored in the data status.

  Unconfirmed is an unread data status not displayed by any user. In addition, the data status indicates that the user has not pressed the confirmation button (1607 in FIG. 16). It is an unread document. Since this data status is unread, there is no inquirer ID (user ID).

  While browsing, it is the status of the read data being displayed by the user. In addition, the data status indicates that the user has not pressed the confirmation button (1607 in FIG. 16). It is a read document. Since this data status is already read, there is an inquirer ID (user ID).

  “Readed” is a read data status displayed by the user. In addition, the data status indicates that the user has not pressed the confirmation button (1607 in FIG. 16). It is a read document. Since this data status is already read, there is an inquirer ID (user ID).

  “Confirmed” is the read data status displayed by the user. In addition, the data status indicates that the user has pressed the confirmation button (1607 in FIG. 16). It is a read document. Since this data status is already read, there is an inquirer ID (user ID).

The inquirer ID (2305) is registered with the user ID of the user who first viewed the unread document stored in the document table, and is stored in the document table.
2301 Document table Document NO stores a number assigned to each document.

  The number assigned to each document is assigned by the management server 100 as information for identifying the registered order when the unread document information is registered in the document table as unread document information (registration order information adding means). .

  When the unread document selection unit selects the unread document information, the unread document information may be selected according to information that can identify the registered order added by the registration order information adding unit.

When the read document selection unit selects the read document information, the unread document information may be selected according to information that can identify the registered order provided by the registration order information addition unit.
The document table file name 2302 stores the actual document file name.
The document table financial institution code 2302 stores a financial institution code used as a search condition.
2304 The document table data status stores a data status used as a search condition.
The document table referrer ID 2305 stores the user ID that viewed the document.

Next, with reference to FIGS. 24 to 33, an example of control of the present system when a confirmation operation of unconfirmed (unread) images is simultaneously performed by a plurality of users (user A and user B) will be specifically described.
FIG. 24 will be described.

  First, in FIG. 24, the financial institution code input unit (1501) and the data status selection unit (1502) from the search condition input screen from the client terminal (hereinafter referred to as user A) of the user ID (document table referrer ID) check001 in the left part. After inputting unconfirmed (unread) as the search condition, the search button (1503) is pressed. When a search button (1503) is pressed, the search condition input from the user A on the search condition input screen is transmitted to the server 100.

  Upon receiving the search condition (unconfirmed (unread)), the server 100 searches the document table for a document corresponding to the search condition (unconfirmed (unread)). First, a document with a matching financial institution code received as a search condition is extracted from the documents in the document table.

  Next, a document whose data status in the document table is “unconfirmed (unread)” is extracted from the extracted document. Further, a document in which the inquirer ID is not input in the document table is extracted. Documents that match all the conditions are registered in the unregistered browsing target document in the user table.

  In FIG. 24, the search condition of the financial institution code “blank (no condition)” and the data status “unconfirmed (unread)” is transmitted from the user A, and the result of the search in the document table is 1 for the unregistered browsing target of check001. , 2, 3, 4 and 5 are registered. The search is first performed using a financial institution code. Since there are no conditions this time, the documents Nos. 1, 2, 3, 4, and 5 are targeted. Next, a search is performed using the data status. Since the search condition is “unconfirmed (unread)” this time, the documents Nos. 1, 2, 3, 4, and 5 are targeted.

Next, a search is performed using the inquirer ID. Since this time, check 001 is the search condition, the documents Nos. 1, 2, 3, 4, and 5 are targeted. As a result of the search, documents NO1, 2, 3, 4, and 5 are registered as unregistered browsing targets in the user table. The flow up to this point is the flow described in step 2001 to step 2013 (FIG. 4).
FIG. 25 will be described.

  In FIG. 25, the document is determined and displayed on the document image screen of user A using the browsing document determination flow described in steps 8001 to 8007 (FIG. 7).

  When the document image screen is displayed, the server 100 updates the data status of the document table and registers the inquirer ID (check001). That is, in FIG. 25, the data status of the document No. 1 is updated from unconfirmed to browsing. The inquirer ID is check001.

  Next, while browsing the document No. 1 in the document table, the user A presses the search button from the client terminal (hereinafter referred to as user B) of the user who is the user ID (document table referrer ID) check002 on the right side. When the search button is pressed, the above-described steps 2001 to 2013 (FIG. 4) are executed.

In FIG. 25, the search condition of the financial institution code “blank (no condition)” and the data status “unconfirmed (unread)” is transmitted from the user B, and the search result in the document table is 2 for the unregistered viewing target of check002. , 3, 4 and 5 are registered. The search is first performed using a financial institution code. Since there are no conditions this time, the documents Nos. 1, 2, 3, 4, and 5 are targeted.
Next, a search is performed using the data status, and this time, “unconfirmed (unread)” is used as a search condition, so that documents Nos. 2, 3, 4, and 5 are targeted.

Next, a search is performed using the inquirer ID, and this time, check 002 is a search condition, and thus, documents NO2, 3, 4, and 5 are targeted. As a result of the search, the documents NO2, 3, 4, and 5 are registered as unregistered browsing targets in the user table.
FIG. 26 will be described.

  In FIG. 26, the document No. 2 document is determined and displayed on the user B document image screen using the browsing document determination flow described in steps 8001 to 8007 (FIG. 7).

At this time, the data status of the document table and the inquirer ID (check002) are registered. In FIG. 26, the data status of the document No. 2 is updated from unconfirmed to browsing. Inquirer ID (check002) is registered.
Next, the user A presses the confirmation button.
FIG. 27 will be described.

  In FIG. 27, according to the flow described in steps 4001 to 4007 (FIG. 6) and steps 8001 to 8007 (FIG. 7), the document No. 3 is determined and displayed for user A.

At this time, the data status of the document table is updated, and the inquirer ID (check001) is registered. In FIG. 27, the data status of the document No. 1 is updated from being viewed to being confirmed. Further, the data status of the document No. 3 is updated from unconfirmed to browsing. Inquirer ID (check001) is registered.
Here, user A presses the previous image button, and user B presses the next image button.
FIG. 28 will be described.

  In FIG. 28, a document No. 1 document (read document) is determined and displayed for user A in accordance with the explanation from step 6001 to step 6007 (FIG. 9), and user B's client is explained in accordance with the explanation in step 7001 to step 7007 (FIG. 10). The terminal 200 determines and displays the document No. 4 document (unread document).

At this time, the data status of the document table is updated. Inquirer ID (check002) is registered. In FIG. 28, the data status of the document No. 2 is updated from being viewed to being viewed. The data status of the document No. 3 is updated from browsing to browsed. The data status of the document No. 4 is updated from unconfirmed to browsing. Inquirer ID (check002) is registered.
Here, user A presses the next image button, and user B presses the confirmation status button.
FIG. 29 will be described.
In FIG. 29, the document No. 3 is determined and displayed on the client terminal 200 of the user A in accordance with the explanation from Step 7001 to Step 7007 (FIG. 10).

  Although the unread document determination process has been described with reference to FIG. 10, the document No. 3 is already read by the user A (check 001). In this case, when re-displaying the already-read document, if it is determined that there is a viewer information determination unit, it is determined whether the received user information and the user information associated with the document NO3 match. In the case where it is determined that the user A (check 001) is added even if the second image button is pressed by adding a second read user determination unit determined as a read document after the viewer information determination unit. ) Can be determined as the document NO3 that has already been read.

The data status of the document of document No. 3 is updated from browsing to browsing. A registration status confirmation screen (FIG. 17) is displayed on the client terminal 200 of the user B in accordance with the description from step 5001 to step 5006 (FIG. 8). The registration status confirmation screen acquires and displays information on all document numbers in the document table.
Here, user A presses the confirmation button, and user B presses the close button.
FIG. 30 will be described.

  In FIG. 30, according to the description of steps 4001 to 4007 (FIG. 6) and steps 8001 to 8007 (FIG. 8), the client terminal 200 of user A determines and displays the document No. 5 document.

At this time, the data status of the document table is updated, and the inquirer ID (check001) is registered. In FIG. 30, the data status of the document No. 3 is updated from browsing to confirmed. Document No. 5 updates the data status of five documents during browsing. Inquirer ID (check001) is registered.
Here, user A presses the confirmation button, and user B presses the confirmation button.
FIG. 31 will be described.

  In FIG. 31, the client terminal 200 of the user A displays the same condition re-search confirmation screen (FIG. 19) in accordance with the description of steps 9001 to 9002 (FIG. 11) and steps 10001 to 10002 (FIG. 12). In accordance with the description of 9004 (FIG. 11), the client terminal of user B displays a browsed unregistered document presence notification screen (FIG. 18).

  In FIG. 31, first, the data status of the document No. 4 is updated from browsing to confirmed. The data status of the document No. 5 is updated from being viewed to being confirmed. After the update, the server 100 confirms with the user A the data status of the unregistered browsing target document in the user table and the document whose inquirer ID in the document table is the user, and all are confirmed. Therefore, the same condition measure search screen (FIG. 19) is displayed to the user A.

Similarly, for user B, the data status of the unregistered browsing target document in the user table and the document whose inquirer ID in the document table is the user is confirmed, and there is a browsed document. A browsed unregistered document presence notification screen (FIG. 18) is displayed.
Here, both the user A and the user B press the Yes button.
FIG. 32 will be described.

  In FIG. 32, in accordance with the explanation from step 2007 to step 2012 (FIG. 4), the client terminal 200 of user A displays the search condition applicable document no screen (FIG. 20), and follows the explanation of step 8001 to step 8006 (FIG. 7). User B's client terminal 201 determines and displays the document No. 2 document whose data status has been browsed.

At this time, the user unregistered browsing target in the user table is updated. In FIG. 32, all the unregistered browsing targets of Check001 in the user table are reset, and all the document NOs registered in the unregistered browsing targets are blank. For the unregistered browsing target of Check002, the document of the document No. 2 whose data status in the document table has been browsed is updated. The data status of the document No. 2 in the document table is updated during browsing.
Here, user A presses the OK button, and user B presses the confirmation button.
FIG. 33 will be described.
In FIG. 33, the user A client terminal 200 displays the search condition input screen, and the user B client terminal 201 displays the same condition destination search screen (FIG. 19).
The server 100 updates the data status of the document No. 2 in the document table from being viewed to being confirmed.
FIG. 34 will be described.
FIG. 34 is a modification of the document table (document table) of FIG. 23 for executing the processes of FIGS.
The document data for each document is managed by associating the document (file name) with a management number (NO) uniquely.
In the document data for each document, a document (file name) and information (introducer ID) that can identify that the document has been browsed are uniquely associated and managed.
In the document data for each document, a document (file name) and a user ID (browsing history information) for browsing the document in the past are uniquely associated and managed.

In the document data for each document, a document (file name) and a data status are uniquely associated and stored. There are three data statuses: unread, browsing, and read.
The unread data status in FIG. 34 has the same meaning as the unconfirmed data status in FIG.
The already read data status in FIG. 34 has the same meaning as the viewed data status in FIG.
The document management apparatus stores a document table for managing all document data for each document as a database (document storage means).

  Reference numeral 3401 in FIG. 34 denotes a document table after the user check001 has pressed the next image button. As the next image button is pressed, (001) check001 is registered in the empty introducer ID field. Thus, until check001 presses the browse end button, the document in which check001 is registered can be occupied in the column of the introducer ID.

  Reference numeral 3402 in FIG. 34 denotes a document table after the user check001 has pressed the previous image button. As the previous image button is pressed, (1) the introducer ID does not change.

  Reference numeral 3403 in FIG. 34 denotes a document table after the user check002 presses the browse end button. As the browse end button is pressed, (1) check002 that occupied the introducer ID is deleted from the introducer ID column. (2) Check002 is registered in the blank viewing history column.

Reference numeral 3404 in FIG. 34 denotes a document table after the user check001 has pressed the next image button. As the next image button is pressed, (001) check001 is registered in the empty introducer ID field. (2) Since there is check002 in the browsing history column, in step S110, the client terminal that has received the next document display request is notified that the browsing history is an unread document (notification means).
FIG. 35 will be described.

FIG. 35 is a modification of the flowchart for performing the document determination process of the document management apparatus 100 when the next image button (1606 in FIG. 16) is pressed. The process starts from F in FIG. 6 and returns to G in FIG.
Here, a process for determining a document to be displayed on the client terminal where the next image button is pressed using a document table (document table) will be described.

  In step S101, as a first purpose, the client terminal identifies the client terminal in order to preferentially display an unread document that no one is currently browsing, such as itself or another user, in the next display. A next document determination request (next document display request) including the user ID (self) is transmitted to the document management apparatus.

As a second purpose, a next document determination request (next document display) including a user ID (self) for identifying a client terminal in order to preferentially display a read document that has already been browsed by the next display. Request) to the document management apparatus.
In step S102, the document management apparatus receives a next document determination request (next document display request) from the client terminal (next document display request receiving means).

  In step S103, the document management apparatus documents one document data that is not currently instructed to be displayed to the client terminal that has received the next document determination request (the client terminal that has received the next document determination request is not currently displaying). A candidate for document data to be displayed next is selected from a plurality of document data in the table (unread document selection means).

  In the document data selection processing in step S103, one different document data is repeatedly selected (reselected) from the plurality of document data in the document table until the document management apparatus determines the next document to be displayed. Is.

  In the document data selection process in step S103, if there is document data that is currently instructed to be displayed (viewed) in the client terminal that has received the next document determination request, it is excluded from the document data to be selected here. .

  In the document data selection process in step S103, as a method for extracting the first selected document data, the document management number (ordered number) is preferentially selected from the smaller one. Further, which document at the time of the first processing in step S103, such as preferentially selecting a number one higher than the management number of the document data currently instructed to be displayed (viewed) to the client terminal that has received the next document determination request, By setting an extraction rule for selecting data in advance, it is possible to control the selection order of document data when a document is determined.

  That is, in the case of the next image button (next document determination request), the document management number (ordered number) which is NO in the document table indicated by 3401 in FIG. 34 is 1 → 2 → 3 → 4 → 5 → 6. The selection order of the document data in step S103 is controlled in ascending order.

In step S104, the document management apparatus searches the document table, determines whether there is any remaining document data not selected in step S103, and confirms the final selection remaining.
If there is remaining document data that has not been determined in step S105 (the document determination process is in progress), the process proceeds to step S105.

  When there is no remaining document data not determined in step S105 (all document data selected in step S103 is determined in step S105), the process proceeds to G.

In this case, since there is no document image to be replaced in response to the next document determination request from the client terminal, the current display instruction (document image) is held as it is, and the document image is replaced in response to the next document determination request from the client terminal. Absent.
Thereby, it is possible to determine whether or not the selection process in step S103 is completed.

  In step S105, the document management apparatus searches the document table, and the user ID (information that can identify that the document has been browsed) is registered in the column of the introducer ID of one document data selected in step S103. It is determined whether or not it is present (browsing information determination means).

If it is determined that it is not registered (blank), the process proceeds to step S106. As a result, when the next button is pressed on the client terminal, no one is currently browsing the document data in the document table as the document data to be displayed on the client terminal next to the document data currently instructed to be displayed. It is possible to prioritize unread documents.
If it is determined that it is registered (there is any user ID), the process proceeds to step S107.

In step S106, the document management apparatus determines one document data selected in step S103 as document data to be displayed on the client terminal that has received the next document display request (unread document determination unit).
In this case, the document image can be replaced in response to the next document determination request from the client terminal.

  Further, the document management apparatus registers the user ID received in step S103 as identifiable information in the introducer ID column (blank) of the document data in the document table determined in step S106 (browsing information). Registration means).

  Here, by registering the user ID in association with the document data, when the next image button is pressed after returning to the read document already viewed by the same user with the previous image button, the determination is made in step S107. It is a standard for judging whether or not.

  In step S107, the document management apparatus searches the document table, and whether the user ID (identifiable information) of the selected single document data selected in step S103 matches the user ID received in step S102. (Second read user determination means).

If it is determined that they match (same user ID), the process proceeds to step S108. As a result, even if the next button is pressed after the previous button returns to a read document already read by the same user, the read document already read by the same user is preferentially determined as the next document. It can be displayed again, and a document already read by another user can be skipped and displayed.
If it is determined that they do not match (other user IDs), the process proceeds to step S103, and another document data is selected again.

In step S108, the document management apparatus determines one document data selected in step S103 as document data to be displayed on the client terminal that has received the next document display request (unread document determination unit).
In this case, the document image can be replaced in response to the next document determination request from the client terminal.

In step S109, it is determined whether or not the document data determined in step S106 has a user ID (browsing history 3403 in FIG. 34) in the browsing history column (browsing history determination means).
If it is determined that there is a user ID (there is a user ID), the process proceeds to step S110.
If it is determined that there is no (blank), the process proceeds to step S111.
In step S110, the document management apparatus notifies the client terminal that has received the next document display request that it is an unread document with a browsing history (notification means).
As a notification method, a method of instructing the client terminal to display display data that can be identified as a new unread document, as indicated by 1612 in FIG.

In other words, when the user presses the next image request to display a read document, it is only necessary to notify the user that the document has been interrupted before displaying the read document.
Therefore, not only the browsing history but also a method of notifying that it is unread document data newly registered (added) in the document table during browsing work may be used.

In step S111, the document management apparatus instructs the client terminal that has received the next document determination request in step S103 to display the document image of the document data determined in steps S106 and S108.
In step S112, the client terminal displays the received document image on the display unit as indicated by 1601 in FIG.
In this case, the document image is replaced in response to the next document determination request from the client terminal.
Then go to G.
FIG. 36 will be described.

FIG. 36 is a modification of the flowchart for performing the document determination process of the document management apparatus 100 when the previous image button (1605 in FIG. 16) is pressed. The process starts from E in FIG. 6 and returns to G in FIG.
Here, processing for determining a document to be displayed on the client terminal where the previous image button is pressed will be described using a document table.

In step S201, the client terminal displays a previous document determination request including a user ID (self) for identifying the client terminal in order to preferentially display the read document that the client terminal has already viewed in the previous display. The previous document display request) is transmitted to the document management apparatus.
In step S202, the document management apparatus receives a previous document determination request (previous document display request) from the client terminal (previous document display request reception unit).

  In step S203, the document management apparatus documents one document data that is not currently instructed to be displayed to the client terminal that has received the previous document determination request (the client terminal that has received the previous document determination request is not currently displaying). A plurality of document data in the table is selected as a candidate of document data to be returned and instructed to be displayed (read document selection means).

  Further, the document data selection process in step S203 repeatedly selects (reselects) one different document data from a plurality of document data in the document table until the document management apparatus determines the document to be returned and instructed to be displayed. )

  In the document data selection process in step S203, since there is document data that is currently instructed to be displayed (viewed) in the client terminal that has received the previous document determination request, it is excluded from the document data to be selected here.

  Further, in the document data selection process in step S203, as a method for extracting the document data to be selected first, the document management number (ordered number) is preferentially selected from the one having the largest document number. Further, which document at the time of the first processing in step S203, such as preferentially selecting a number one smaller than the management number of the document data currently instructed to be displayed (viewed) to the client terminal that has received the previous document determination request, By setting an extraction rule for selecting data in advance, it is possible to control the selection order of document data when a document is determined.

  That is, in the case of the previous image button (previous document determination request), the document management number (ordered number) that is NO in the document table 3401 in FIG. 34 is 6 → 5 → 4 → 3 → 2 → 1. The selection order of the document data in step S103 is controlled in descending order.

In step S204, the document management apparatus searches the document table, determines whether or not there is remaining document data not selected in step S203, and confirms the final selection remaining.
If there is remaining document data not determined in step S205 (the document determination process is in progress), the process proceeds to step S205.

  If there is no remaining document data not determined in step S205 (all document data selected in step S203 is determined in step S205), the process proceeds to G.

In this case, since there is no document image to be replaced in response to the previous document determination request from the client terminal, the current display instruction (document image) is held as it is, and the document image is replaced in response to the previous document determination request from the client terminal. Absent.
Thereby, it is possible to determine whether or not the selection process in step S203 is completed.

  In step S205, the document management apparatus searches the document table, and the user ID (information that can identify that the document has been browsed) is registered in the column of the introducer ID of one document data selected in step S203. Determine if you are.

If it is determined that it is not registered (blank), the process proceeds to step S203. Accordingly, since it is desired to return to the previous image and only the already read document is selected, the document data can be reselected when the unread document is selected in step S203.
If it is determined that it is registered (there is any user ID), the process proceeds to step S206.

  In step S206, the document management apparatus searches the document table, and whether the user ID (identifiable information) of the selected one document data selected in step S203 matches the user ID received in step S202. (First read user determination means).

If it is determined that they match (same user ID), the process proceeds to step S207. As a result, when the previous image button is pressed, a read document that has already been viewed by the same user can be preferentially determined and displayed again as a previous document, and has already been read by another user. The document can be skipped and displayed.
If it is determined that they do not match (other user IDs), the process proceeds to step S203, and another document data is selected again.

In step S207, the document management apparatus determines one document data selected in step S203 as document data to be displayed on the client terminal that has received the previous document display request (read document determination unit).
In this case, the document image can be replaced in response to the previous document determination request from the client terminal.

In step S208, the document management apparatus instructs the client terminal that has received the previous document determination request in step S203 to display the document image of the document data determined in step S207.
In step S209, the client terminal displays the received document image on the display unit as indicated by 1601 in FIG.
In this case, the document image is replaced in response to the previous document determination request from the client terminal.
Then go to G.
FIG. 37 will be described.

  FIG. 37 is a flowchart for performing the browsing end process of the document management apparatus 100 when the browsing end button (1611 in FIG. 16) is pressed. The process starts from M in FIG.

In step S301, the client terminal transmits a browse end request including a user ID (self) for identifying the client terminal to the document management apparatus in order to end browsing of the document performed by the user so far.
In step S302, the document management apparatus receives a browsing end request from the client terminal.
In step S303, the document management apparatus selects one document data as a candidate of document data to be browse-terminated from a plurality of document data in the document table.

  The document data selection process in step S303 is to repeatedly select (reselect) one different document data from the plurality of document data in the document table until there is no more document data to be browsed.

In step S304, the document management apparatus searches the document table, determines whether there is any remaining document data not selected in step S303, and confirms the final selection remaining.
If there is remaining document data that has not been determined in step S305 (browsing end processing is in progress), the process proceeds to step S305.

If there is no remaining document data not determined in step S305 (all document data selected in step S303 is determined in step S305), the process proceeds to step S309.
Thereby, it is possible to determine whether or not the selection process in step S303 is completed.

  In step S305, the document management apparatus searches the document table, and the user ID (information that can identify that the document has been browsed) is registered in the column of the introducer ID of one document data selected in step S303. Determine if you are.

If it is determined that it is not registered (blank), the process proceeds to step S303. Thereby, since it is desired to select only the read document here, the document data can be selected again when the unread document is selected in step S303.
If it is determined that it is registered (there is any user ID), the process proceeds to step S306.

  In step S306, the document management apparatus searches the document table, and determines whether the user ID (identifiable information) of one document data selected in step S303 matches the user ID received in step S302. To do.

If it is determined that they match (same user ID), the process proceeds to step S307. As a result, it is possible to determine document data having the same introducer ID and the user ID that requested the browsing end, and execute the document data editing process at the end of browsing, which is the determination criterion in step S109. In step S303, another document data is selected again.
In step S307, the user ID received in step S302 is registered in the column for browsing history of document data determined in step S306.
Thereby, even after the user finishes the browsing work, it is left in the history that there was browsing in the past.
In step S308, the user ID is deleted from the column of introducer ID of the document data determined in step S306.

Here, by deleting the introducer ID, the document data occupied by a specific user during the browsing operation can be newly unread when another browsing user presses the next image button. Can be displayed as a document.
In step S309, the document management apparatus transmits an end instruction to the client terminal and ends the operation.

The program in the present invention is a program that can be read and executed by the computer in the processing method of the flowcharts shown in FIGS. 3 to 12 and 35 to 37, and the storage medium of the present invention is the program in FIGS. 3 to 12 and 35. 37 is stored in the external memory 411 of the document management server 100 as a program that can be executed by a computer.

As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by executing the reading.

In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium storing the program constitutes the present invention.

As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk or the like can be used.

Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network by a communication program, the system or apparatus can enjoy the effects of the present invention.
In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

100 Document management server (document management device)
200 Client terminal 401 CPU
402 ROM
403 RAM (storage unit)
411 External memory (storage unit)

Claims (9)

A document management device communicably connected to a client terminal,
Document storage means for storing, for each document, document data that uniquely associates a document with information that can identify that the document has been viewed;
A next document display request receiving means for receiving a next document display request for displaying an unread document from the client terminal;
An unread document selecting means for selecting one document data from the document data stored in the document storage means when the next document display request is received;
Browsing information determination means for determining whether the selected one document data stored in the document storage means includes the identifiable information;
An unread document determination unit that determines the selected document data as document data to be displayed on the client terminal that has received the next document display request when it is determined that there is no browsing information determination unit;
A document management apparatus comprising:   The document management apparatus according to claim 1, wherein the identifiable information is user information for viewing a document. The next document display request receiving means further receives user information together with the next document display request from the client terminal,
Browsing information registration for registering the received user information as the identifiable information in the determined document data stored in the document storage means when the unread document determination means determines the document data to be displayed. The document management apparatus according to claim 2, further comprising means. A previous document display request receiving means for receiving a previous document display request including user information in order to display a browsed document from the client terminal;
A read document selection unit that selects one document data from the document data stored in the document storage unit when the previous document display request is received;
It is determined whether the identifiable information of one document data selected by the read document selection unit stored in the document storage unit matches the user information included in the previous document display request. First read user determination means to:
A document that instructs to display one document data selected by the read document selection unit to the client terminal that has received the previous document display request when it is determined that the determination results of the first read user determination unit match Means for determining a read document to be determined as data;
The document management apparatus according to claim 2, further comprising: When the browsing information determination unit determines that there is the identifiable information, the identifiable information of one document data selected by the unread document selection unit stored in the document storage unit, and the previous A second read user determination unit for determining whether or not the user information received by the document display request reception unit matches;
The unread document determination means displays one document data selected by the unread document selection means on the client terminal that has received the next document display request when it is determined that the second read user determination means matches. 5. The document management apparatus according to claim 2, wherein the document management apparatus determines the document data to be instructed. The document data of the document storage means further stores a document and past browsing history information in a uniquely associated manner,
A browsing history determination unit that determines that the browsing information determination unit does not have the identifiable information, and determines whether the browsing history information exists in the document data determined by the unread document determination unit;
A notification means for notifying the client terminal that has received the next document display request that the browsing history is an unread document when it is determined that there is the browsing history determination means;
The document management apparatus according to claim 2, further comprising: The document data in the document storage means further stores a document and a number that is assigned to the document in a uniquely associated manner,
The document management apparatus according to any one of claims 2 to 6, wherein when the unread document selection unit selects one document data, the document is selected according to the ordered number. A document management apparatus comprising a document storage unit that stores document data that uniquely associates a document with information that can be identified as having been browsed for each document that is communicably connected to a client terminal. A control method,
A next document display request receiving means for receiving a next document display request for displaying an unread document from the client terminal;
An unread document selection step of selecting one document data from the document data stored in the document storage unit when the unread document selection unit of the document management apparatus receives the next document display request;
A browsing information determination step in which the browsing information determination unit of the document management device determines whether the selected one document data stored in the document storage unit includes the identifiable information;
When the unread document determining unit of the document management apparatus determines that there is no browsing information determination step, the selected one document data is used as document data for instructing display to the client terminal that has received the next document display request. Unread document determination process to determine;
The control method characterized by including. A program that can be read and executed by a document management apparatus that is communicably connected to a client terminal,
The document management device;
Document storage means for storing, for each document, document data that uniquely associates a document with information that can identify that the document has been viewed;
A next document display request receiving means for receiving a next document display request for displaying an unread document from the client terminal;
An unread document selecting means for selecting one document data from the document data stored in the document storage means when the next document display request is received;
Browsing information determination means for determining whether the selected one document data stored in the document storage means includes the identifiable information;
An unread document determination unit that determines the selected document data as document data to be displayed on the client terminal that has received the next document display request when it is determined that there is no browsing information determination unit;
A program characterized by making it function.

Images