File management apparatus, file management method, computer readable medium, and computer program product

Abstract

A file management apparatus, a file management method, and a computer-readable medium are provided. The file management apparatus includes a processor that performs control to display a selection screen in which a plurality of registration-destination candidates of an electronic file are selected by a user and an assignment screen in which the plurality of registration-destination candidates selected in the selection screen are displayed and the electronic file is assigned to each registration-destination candidate by the user, and performs control to display detailed information for a registration-destination candidate that is not displayed in the selection screen in the assignment screen.

Description

Technical Field

[0001] This disclosure relates to document management apparatus, document management method, and computer-readable medium. Background Technology

[0002] Users can store (register) electronic files in their desired folders or databases on servers.

[0003] Japanese Patent Application Publication No. 2006-330819 discloses a document management device that, upon receiving a user's designation of electronic documents as copy sources, designation of multiple folders as copy destinations, and execution instructions, batch copies electronic documents from the designated copy sources to the designated multiple folders.

[0004] Japanese Patent Application Publication No. 2005-275807 discloses a document management system that includes a server for managing a document database and a client connected to the server via a network. In this document management system, the server receives multiple documents and instructions for batch registration from the client, and batch registers the received multiple documents into the document database. Summary of the Invention

[0005] When a user registers the same or different electronic documents to multiple different registration destinations, the electronic documents are sometimes registered to the wrong registration destination. The purpose of this disclosure is to prevent the electronic documents from being registered to the wrong registration destination when a user registers electronic documents to multiple different registration destinations.

[0006] According to a first aspect of this disclosure, a file management device is provided, wherein the file management device includes a processor that performs the following control: displaying a selection screen and an allocation screen, wherein a user selects multiple registration destination candidates for electronic files in the selection screen, and the multiple registration destination candidates selected in the selection screen are displayed in the allocation screen, and electronic files are allocated to each registration destination candidate by the user, and the processor performs the following control: displaying detailed information for the registration destination candidates that is not displayed in the selection screen in the allocation screen.

[0007] According to the second aspect of this disclosure, the processor performs the following control: in the allocation screen, when the user selects an electronic file that has been assigned to a candidate registered destination, at least one of the attribute information of the selected electronic file and a preview screen is displayed simultaneously with the allocation screen.

[0008] According to the third aspect of this disclosure, the processor, in the allocation screen, allows a user to move an electronic file assigned to a registration destination candidate to another registration destination candidate, copy an electronic file assigned to a registration destination candidate to another registration destination candidate, and replace an electronic file assigned to a registration destination candidate with at least one of the electronic files assigned to other registration destination candidates.

[0009] According to the fourth aspect of this disclosure, the processor, in the allocation screen, does not allow the user to move a registered electronic document that has already been registered to a registration destination candidate while displaying the registered electronic document that has already been registered to a registration destination.

[0010] According to the fifth aspect of this disclosure, the processor, in the allocation screen, allows a user to copy a registered electronic file that has been registered to a registration destination to a candidate registration destination.

[0011] According to the sixth aspect of this disclosure, the processor performs the following control: displays a selection section in the selection screen, which allows the user to select multiple registration destination candidates in batches according to a predetermined document classification unit.

[0012] According to the seventh aspect of this disclosure, the registration destination candidate is the registration destination of the electronic document to be produced in each process of a case that includes multiple processes, and the registration destination is specified according to the type of the electronic document. The processor performs the following control: displays a selection unit in the selection screen, which is used to allow the user to select multiple registration destination candidates corresponding to each process of the case in batches by process unit.

[0013] According to the eighth aspect of this disclosure, the registration destination candidate is the registration destination of the electronic document to be produced in each process of a case that includes multiple processes, and the registration destination is specified according to the type of the electronic document. The processor performs the following control: displays a selection unit in the selection screen, which is used to allow the user to select in batches the registration destination candidates of the same type of electronic document corresponding to multiple cases that are common to the process.

[0014] According to the ninth aspect of this disclosure, a computer-readable medium is provided, which stores a program that causes a computer to perform processing, wherein the following control is performed: displaying a selection screen and an allocation screen, wherein a user selects multiple registration destination candidates for an electronic document in the selection screen, and the multiple registration destination candidates selected in the selection screen are displayed in the allocation screen, and the electronic document is allocated by the user to each registration destination candidate, and wherein the following control is performed: displaying detailed information for the registration destination candidates that is not displayed in the selection screen in the allocation screen.

[0015] According to the 10th aspect of this disclosure, a file management method is provided, wherein the following control is performed: displaying a selection screen and an allocation screen, wherein a user selects multiple registration destination candidates for electronic files in the selection screen, and the multiple registration destination candidates selected in the selection screen are displayed in the allocation screen, and the electronic files are allocated to each registration destination candidate by the user, and the following control is performed: displaying detailed information for the registration destination candidates that is not displayed in the selection screen in the allocation screen.

[0016] The effects of the invention

[0017] According to Scheme 1, Scheme 9, or Scheme 10, users are prevented from registering electronic documents to the wrong registration destination.

[0018] According to the second scheme, the registration of erroneous electronic documents was suppressed.

[0019] According to the third or fifth scheme, the efficiency of the allocation operation of electronic documents to the candidate registration destination is improved.

[0020] According to the fourth scheme, the accidental loss of registered electronic documents from the registration destination is prevented.

[0021] According to the sixth scheme, users do not need to individually select multiple registration destination candidates belonging to each document category.

[0022] According to the seventh scheme, users do not need to individually select multiple registration destination candidates belonging to each process of the case.

[0023] According to the eighth scheme, users do not need to select multiple registration destination candidates belonging to the same type of electronic document individually. Attached Figure Description

[0024] Figure 1 This is a summary structure diagram of the file management system.

[0025] Figure 2This is a functional block diagram of a file management device.

[0026] Figure 3 This is an example of a view showing an overview.

[0027] Figure 4 This is a diagram used to illustrate batch selection for the same process.

[0028] Figure 5 This is a flowchart showing the display process of the allocation screen for batch selection of the same process.

[0029] Figure 6 This is an example of a registration screen showing batch selections for the same process.

[0030] Figure 7 This is a diagram used to illustrate batch selection of the same document.

[0031] Figure 8 This is a flowchart illustrating the display process of the allocation screen for batch selection of the same document.

[0032] Figure 9 This is an example of a registration screen showing batch selection of the same document.

[0033] Figure 10 This diagram illustrates the copying of registered document files in the allocation screen. Detailed Implementation

[0034] The following is a confirmation of the attached document. Figure 1 The various embodiments of this disclosure will be described in detail below. The structures described below are illustrative examples and can be appropriately modified to fit the specifications of systems, devices, etc. Furthermore, in cases where multiple embodiments or variations are included, it is assumed from the outset that their feature parts are appropriately combined. In all the drawings, the same reference numerals are used for the same elements, and repeated descriptions are omitted.

[0035] <Structure of a Document Management System>

[0036] Figure 1 This is a schematic diagram of the file management system 10. The file management system 10 includes a server 12 as a file management device and multiple clients 14 that are connected to the server 12 in a communicative manner via a network 18 such as the Internet. Hereinafter, the server 12 will be referred to as the file management device 12. In addition, the network 18 is not limited to the Internet, and can adopt various methods such as intranets and dedicated lines.

[0037] The document management device 12 is a computer that manages document files corresponding to cases, accepts document file registrations based on requests from the client 14, and provides registered document files to the client 14. In this embodiment, the document management device 12 manages document files as electronic files, but the electronic files managed by the document management device 12 are not limited to document files. The form of electronic files is not limited; for example, it can be documents, photos, animated images, etc. The document management device 12 includes a processor 20 and a storage device 22. The processor 20 includes a CPU and performs information processing according to a program installed on the document management device 12. The processor 20 can be defined as a computer in a narrow sense. The storage device 22 is ROM, RAM, flash memory, hard disk, etc., and stores the program executed by the processor 20 and a document database (see [reference]). Figure 2 The file management device 12 functions as a web server.

[0038] In addition, the program executed by the processor 20 of the file management device 12 is provided via a network such as the Internet, or it can be provided by storing it on a computer-readable recording medium such as an optical disc or a USB memory.

[0039] Client 14 is a personal computer (PC), tablet terminal, or smartphone, etc., operated by the user. A web browser is installed on client 14 to display screen information sent from file management device 12. The user starts the web browser, navigates to the web page provided by file management device 12, and logs in on that web page, thereby displaying the overview screen (see reference) provided by file management device 12. Figure 3 ) and registration screen (refer to) Figure 6 , 9 The screens on client 14 display operations. Alternatively, a dedicated application can be used on client 14 instead of a web browser.

[0040] <Functional Structure of Document Management Device>

[0041] Figure 2 This is a functional block diagram of the document management device 12. The processor 20 operates according to a program (not shown) stored in the storage device 22, thereby functioning as the operation receiving unit 24, the overview screen providing unit 26, the registration screen providing unit 28, and the registration unit 30. The operation receiving unit 24 receives operations from the client 14, the overview screen providing unit 26 provides an overview screen to the client 14, the registration screen providing unit 28 provides a registration screen to the client 14, and the registration unit 30 registers the document files received from the client 14 in the document database 32.

[0042] The storage device 22 of the document management device 12 stores a document database 32 (hereinafter referred to as document DB 32) that manages document files corresponding to cases. The document DB 32 includes case information 40, case process information 42, case document information 44, corresponding information of registered document files 46, and registered document file groups 48.

[0043] Here, a case is a task (including business) that involves multiple processes, for example... Figure 3 The overview screen 60 includes "Document Management System Development," "Workflow System Development," and "Ordering System Development," among others. The process of a case (hereinafter also referred to as steps) is the procedure performed during the execution of a case, for example... Figure 3 The overview screen 60 includes sections such as "Plan," "Development," and "Evaluation." Case documents are the types of documents (hereinafter referred to as document types) that are pre-planned to be produced at each stage of the case execution process. For example, they are... Figure 3 The overview screen includes "Development Plan", "Basic Contract", "Basic Design" and other documents.

[0044] The case information in document DB 32 40 exists for each case, for example, Figure 3 The information in the overview screen 60, such as "A0001" (project ID), "Document Management System Development" (project name), and "Fujitaro" (person in charge), is matched with the case-related information.

[0045] Document DB 32 contains the case process information 42, which exists for each process of each case, for example, Figure 6 On the registration screen 100, the "Steps" section shows the "Evaluation" process, and the information related to the process, such as "Shinjiro Tanaka" (technical manager), "Tetsuo Mikami" (administrative manager), "2019 / 06 / 20" (scheduled start date of evaluation), and "2019 / 07 / 20" (scheduled completion date of evaluation), are matched together.

[0046] Document information 44 for cases in document DB 32 exists for each type of document to be produced in each process of each case, for example, Figure 6 The registration screen shows the "Document Information" section, which corresponds to the document-related information in the "Test Plan" such as "Shinjiro Tanaka" (Production Manager) and "2019 / 06 / 10" (Scheduled Production Date).

[0047] The case information 40, case process information 42, and case document information 44 in document DB 32 are typically information registered by the user via client 14 before the document files are registered to document DB 32, for example, during the schedule study phase of each case.

[0048] The registered document file group 48 of document DB 32 is a collection of document files stored in document DB 32 that have been registered with document DB 32 according to the instructions of client 14. The correspondence information 46 of the registered document files in document DB 32 is information indicating which document in which case each document located in the registered document file group 48 corresponds to.

[0049] <Overview of the screen>

[0050] Next, a summary of the overview screen and the registration screen will be provided. Figure 3 This is a diagram showing an example of a view screen 60. View screen 60 is a screen that displays the registration status of document files in document DB 32. In addition, view screen 60 is also a selection screen for registering document files to document DB 32 or reading registered document files from document DB 32.

[0051] <Definitions for the registered destination, etc.>

[0052] Here, "registration destination" refers to at least one of the document file's storage destination or location destination. In this embodiment, it is the document file's location destination determined by the case's identification information (e.g., case name) and document type. "Registering a document file to a registration destination" means storing the document file in at least one of the storage destinations that serve as registration destinations or associating the document file with a location destination that serves as a registration destination. In this embodiment, it means associating the document file with the case's identification information and document type in the document database. Furthermore, registration destination candidates are candidates for registration destinations when registering a document file within a registration destination. The overview screen 60 is an example of a selection screen where the user selects multiple registration destination candidates for a document file using the batch selection unit 76 of the process unit or the batch selection unit 78 of the document unit, as described below.

[0053] <Summary of the registration screen>

[0054] There are two methods available on the registration screen. Figure 6 , 9 Examples of registration screens for various methods are shown below. Figure 6 The registration screen 100 is shown in the overview screen 60, such as Figure 4 The screen shown is displayed when multiple registration destination candidates are selected in batches by process unit 76 of the case and a batch registration (batch upload) request is issued by pressing the batch selection unit 76 of the process unit. Figure 9 The registration screen 100A is shown in the overview screen 60, such as Figure 7The screen shown is displayed when multiple registration destination candidates are selected in batches by document type and a batch registration (batch upload) request is issued by pressing the batch selection unit 78 of the document unit.

[0055] Registration screen 100 (reference) Figure 6 The system includes an allocation screen 102 with an allocation table 104, a file information display unit 114, and a preview display unit 116. In the allocation table 104, users select from multiple registered destination candidates (…). Figure 6 The allocation screen 112 assigns document files to each registration destination candidate. After assigning document files from the user to each registration destination candidate, pressing the upload button 122 registers these document files to each registration destination candidate. Alternatively, document files can be temporarily registered to each registration destination candidate during the allocation stage, and then, based on certain conditions (such as acceptance of button presses, the passage of a certain period of time, etc.), they can be truly registered (i.e., become registered). In this embodiment, it has a significant feature in that: the allocation screen 102 displays detailed information about the registration destination candidates that is not displayed in the overview screen 60 (e.g., ...). Figure 6 The "Document Information" section lists the person in charge of each document's creation and the scheduled creation date. Detailed information about the registration destination candidates indicates their attributes and is not displayed on the selection screen. In other words, it's detailed information about the registration destination candidates that cannot be obtained from the selection screen. This prevents users from registering documents to the wrong registration destination candidate.

[0056] <Detailed overview of the screen>

[0057] Next, a detailed explanation of screen 60 will be provided. For example... Figure 3 As shown, the overview screen 60 includes a list 62. The list 62 includes case items 64, process items 66, document items 68, a case information bar 70, and an element bar 72. In the case information bar 70, information related to a case is arranged horizontally, and cases are arranged vertically. In the process items 66, the names of each process in a case are arranged horizontally. In the document items 68, the names of the documents created in each process of a case are displayed, corresponding to the process.

[0058] Table 62 is a table that arranges cases vertically as vertical items and documents created within cases horizontally as horizontal items. The elements in column 72 of the table indicate whether any documents corresponding to the cases and documents are registered. In column 72, if a document is registered, a marker indicating the document (called a document marker) is displayed; if no document is registered, a dashed outline of the document marker is displayed.

[0059] The definition information 34 of the overview screen storing the form of the overview table 62, case items 64, process items 66, and document items 68 in the storage device 22 (see reference) Figure 2 The processor 20 of the file management device 12 functions as a view provider 26, using the view definition information 34, the case information 40 of the document DB 32, and the corresponding information 46 of the registered document files to generate a view table 62, which is then provided to the display of the client 14.

[0060] The overview screen providing unit 26 displays the information from the case information 40 of document DB 32 that corresponds to the case items 64 in the overview table 62 defined in the definition information 34 of the overview screen in the case information column 70. Furthermore, the overview screen providing unit 26 uses the corresponding information 46 of the registered document files in document DB 32 to display the element column 72 of the overview table 62. Specifically, the overview screen providing unit 26 sets documents (registration destinations) of cases for which there is no corresponding document file in the corresponding information 46 of the registered document files in document DB 32 as unregistered, and sets documents (registration destinations) of cases for which there is a corresponding document file in the corresponding information 46 of the registered document files in document DB 32 as registered, generates the element column 72 of the overview table 62, and displays them accordingly.

[0061] List 62 includes a batch selection unit 76 for selecting multiple documents in batches by process unit of a case, and a batch selection unit 78 for selecting multiple documents in batches by document unit of the same type. The batch selection unit 76 for process units is a button with a mark that overlaps two greater than / less than signs, and is set up for each process of each case. The batch selection unit 78 for document units is a button with a mark that overlaps two greater than / less than signs and rotates them 90 degrees, and is set up for each document unit. Hereinafter, the process of pressing the batch selection unit 76 for process units will be explained first, followed by the process of pressing the batch selection unit 78 for document units.

[0062] <Batch Selection of Process Units>

[0063] The processor 20 of the document management device 12 functions as an operation receiving unit 24, receiving operations from the client 14. The user clicks on the batch selection unit 76 of the process unit in the list 62 using a mouse cursor, etc., thereby... Figure 4 As shown in the portion surrounded by rounded quadrilaterals, multiple documents corresponding to the batch selection unit 76 of the pressed process unit are selected in batches. The overview screen providing unit 26 responds to the user's pressing of the batch selection unit 76 of the process unit, as... Figure 4 The pop-up window 80 appears as shown.

[0064] The pop-up window 80 contains a batch download (batch read) button 82 and a batch upload (batch register) button 84. When the user presses the batch download button 82 with the mouse cursor, one or more registered document files (registered document files existing in document DB 32) from the batch selection unit 76 of the process unit in the list 62 are read to the client 14.

[0065] On the other hand, when a user presses the batch upload button 84 in the pop-up window 80 using the mouse cursor, the upload is displayed on the monitor of the client 14. Figure 6 The registration screen shown below. (The following will also...) Figure 6 The registration screen is called the registration screen corresponding to the batch selection of process units.

[0066] Additionally, pop-up window 80 contains process information table 86. Process information table 86 is a table representing information related to the process of the case (hereinafter referred to as the selected process) selected by the batch selection unit 76 of the process units in list 62. Figure 4 In the process information table 86, information related to the evaluation process of case A0002 (project ID) is displayed, including "Technical Manager", "Action Manager", "Evaluation Start Date", and "Evaluation Completion Date". This information is read and displayed by the overview screen provider 26 from the process information 42 of the case in document DB 32.

[0067] Additionally, the "Status" item in the process information table 86 indicates whether the selected process is in progress. For example, if the current date and time fall within the range of the scheduled start date to the scheduled completion date of the evaluation in the selected process's information, it is displayed as "In Progress"; otherwise, it is displayed as "Not In Progress". Furthermore, if the selected process is proceeding as scheduled, the "Status" item in the process information table 86 is displayed as "GREEN"; otherwise, it is displayed as "RED". For example, if the current date and time exceeds the scheduled completion date of the evaluation in the selected process's information, and there are document files not registered in document DB 32 among the multiple documents belonging to the selected process, it is displayed as "RED"; otherwise, it is displayed as "GREEN".

[0068] <Registration screen corresponding to batch selection of process units>

[0069] Next, the registration screen corresponding to the batch selection of the process unit will be explained in detail. For example... Figure 6As shown, the registration screen 100 includes an allocation screen 102 with an allocation table 104, a document information display unit 114, and a preview display unit 116. The allocation table 104 includes a case information field 106, a step (process) information field 108, a document information field 110, and an allocation field 112. The format and items of the allocation table 104 are defined in the registration screen definition information 36 stored in the storage device 22 (see reference). Figure 2 Defined in ).

[0070] Here, the operation of the processor 20 of the file management device 12 used to display the allocation table 104 will be described. Figure 5 This is a flowchart illustrating the process performed by the processor 20 of the file management device 12 in order to display the allocation table 104.

[0071] exist Figure 5 In S100, processor 20 functions as operation receiving unit 24, as shown in list 62 (see reference). Figure 4 In the process, the selection of case i and document j (j+n) serves as the candidate registration destination. This is in... Figure 4 The process occurs when the batch selection section 76 for the process unit is pressed and the batch upload button 84 is pressed in the pop-up window 80. Here, case i refers to the process of uploading the list 62 (refer to...). Figure 3 The cases shown in the case information column 70 are numbered sequentially from top to bottom as the i-th case. Document j refers to the j-th document shown in the document item 68 of the overview table, which is numbered sequentially from left to right. Document j ~ (j+n) refers to n documents (registration destination candidates).

[0072] Next, in S102, the processor 20 functions as the registration screen provider 28, retrieving detailed information about case i from the case information 40 in the document DB 32. The retrieved detailed information is displayed in the allocation table 104 (see reference). Figure 6 In case information section 106. Additionally... Figure 5 The process is that after the registration screen providing unit 28 obtains information in each step of S102 to S108, it uses the obtained information to generate and display the allocation table 104 in S110.

[0073] Next, in S104, the registration screen providing unit 28 retrieves detailed information about the process to which documents j to (j+n) in case i belong from the process information 42 of case DB 32. The retrieved detailed information is displayed in the step information column 108 of allocation table 104.

[0074] Next, in S106, the registration screen providing unit 28 retrieves the detailed information of documents j to (j+n) in case i from the document information 44 of document DB 32. The retrieved detailed information is displayed in the document information column 110 of allocation table 104. Additionally, as... Figure 6 As shown, in the document information bar 110, detailed information of each document is displayed vertically.

[0075] Next, in S108, the registration screen providing unit 28 retrieves the filenames of the document files registered in document DB 32 from the corresponding information 46 of the registered document files in document DB 32 for document j to (j+n) in case i. The retrieved filenames are displayed in the allocation column 112 of the allocation table 104. Furthermore, in the allocation column 112, the filenames of the registered document files are displayed corresponding to each document in the document information column 110. Additionally, in... Figure 6 In allocation table 104, an example of displaying the filenames of registered document files in allocation column 112 is not shown. Instead, an example of displaying the filenames of allocated document files (described later) in allocation column 112 is shown. Allocated document files are those that are not in a registered state. The example of displaying the filenames of registered document files in allocation column 112 is shown in... Figure 9 As shown in Allocation Table 104A, "Basic Contract_k1.doc" is a registered document file. As shown in the figure, the quadrilaterals surrounding the filenames are arranged differently to distinguish between the registered document file (Basic Contract_k1.doc) and the allocated document file (Contract_k3.doc). Specifically, the filename surrounded by a quadrilateral with right angles is the filename of the registered document file, and the filename surrounded by a quadrilateral with rounded corners is the filename of the allocated document file.

[0076] Next, in Figure 5 In S110, the registration screen providing unit 28 uses the definition information 36 of the registration screen (refer to...). Figure 2 Based on the information obtained in S102 to S108, an allocation table 104 is generated and provided to the display of the client 14. The above is... Figure 5 Explanation of the process.

[0077] exist Figure 6 In allocation table 104, users allocate document files stored on client 14 to the allocation column 112 (document registration destination candidate) for example by dragging and dropping. The document files allocated to allocation column 112 are already allocated document files, and the filename of the allocated document file is displayed in allocation column 112. Figure 6 In the document, "Test Plan.doc" is the assigned document file.

[0078] Here, on the allocation screen 102, detailed information about the document (registration destination candidate) that is not shown on the overview screen 60 is displayed. Figure 6 In the case information section 106, the "Project Budget" and "Product Launch Scheduled Date" are detailed information; in the steps information section 108, the "Technical Lead," "Action Lead," "Evaluation Start Scheduled Date," and "Evaluation Completion Scheduled Date" are detailed information; and in the document information section 110, the "Production Lead" and "Production Scheduled Date" for each document are detailed information. Additionally, in... Figure 3 The overview screen 60 displays detailed case information such as "responsible person" and "scheduled completion date". However, if the element bar 72 is widened in the overview screen 60, such detailed information is not displayed in the overview screen 60, but only in the assignment screen 102.

[0079] Users can confirm the details of each registered destination candidate displayed in the allocation table 104 while assigning document files to the allocation column 112 of each registered destination candidate in the allocation table 104, thus preventing the document files from being assigned to the wrong registered destination candidate.

[0080] When a user allocates document files to the allocation column 112 corresponding to the documents (each registered destination candidate) in the document information column 110 of the allocation table 104, these document files are stored as temporary document files in the temporary storage area 38 of the storage device 22 of the file management device 12 (see reference). Figure 2 ). Figure 2 The temporary document file group 52 in the storage device 22 represents a collection of temporary document files 56. When a temporary document file 56 is stored in the temporary storage area 38, a correspondence information 50 is generated indicating which document in which case the temporary document file 56 corresponds to, and this correspondence information 50 is stored in the temporary storage area 38.

[0081] Then, when the user presses the button located at the mouse cursor, etc. Figure 6 When the upload button 122 is pressed on the registration screen 100, each document file assigned to the allocation column 112 is registered in the document DB 32. This is achieved by the processor 20 of the file management device 12 functioning as the registration unit 30, moving the temporary document files stored in the temporary storage area 38 to the document DB 32 as part of the registered document file group 48, and moving the corresponding information 50 of the temporary document files stored in the temporary storage area 38 to the document DB 32 as part of the corresponding information 46 of the registered document files.

[0082] As described above, in addition to the allocation screen 102, the registration screen 100 also includes a file information display unit 114 and a preview display unit 116. The file information display unit 114 displays the attribute information of the selected document file (hereinafter referred to as the selected document file) when a user clicks on an allocated or registered document file in the allocation column 112 of the allocation table 104 using a mouse cursor or similar device. Here, the attribute information of the electronic file refers to information representing the attributes of the electronic file, such as the update date and time, updater, size, creation date and time, and creator. In the case of a document file, page count, word count, etc., can also be attribute information; in the case of a moving image file, length, etc., can also be attribute information.

[0083] The preview display unit 116 is the part that displays a preview screen of the selected document file when the user clicks on an assigned document file or a registered document file configured in the allocation column 112 of the allocation table 104 using the mouse cursor or the like.

[0084] When the selected document file is an already assigned document file, the registration screen providing unit 28 reads the attribute information and file body (or thumbnail) of the temporary document file located in the temporary storage area 38 of the storage device 22, which is the selected document file. Then, the registration screen providing unit 28 displays the read attribute information on the file information display unit 114, and displays a preview screen on the preview display unit 116 based on the read file body (or thumbnail). As a result, the user can confirm the attribute information and preview screen of the assigned document file by clicking on it with the mouse cursor in the registration screen 100, thus preventing the incorrect document file from being assigned to the registration destination candidate during registration.

[0085] Furthermore, when the selected document file is a registered document file, the registration screen providing unit 28 reads the attribute information and file body (or thumbnail) of the selected document file located in document DB 32. Then, the registration screen providing unit 28 displays the read attribute information on the file information display unit 114, and displays a preview screen on the preview display unit 116 based on the read file body (or thumbnail). In this way, the user can confirm the detailed content of the registered document file.

[0086] In addition, such as Figure 6As shown, a page switching button 118 can also be provided in the file information display unit 114. Each time the page switching button 118 is pressed, different attribute information of the document file is displayed sequentially in the file information display unit 114. Furthermore, as shown in the figure, a page switching button 120 can also be provided in the preview display unit 116. Each time the page switching button 120 is pressed, different pages of the document file are displayed sequentially. In this embodiment, both a file information display unit 114 and a preview display unit 116 are provided, but it is also possible to provide only one of them.

[0087] <Batch selection of document units>

[0088] Next, the batch selection section 78 for document units was pressed (see reference). Figure 7 The following explains the processing steps. The user selects document units in batches using the mouse cursor (e.g., by pressing the batch selection button 78). Thus, as... Figure 7 As shown in the portion surrounded by rounded quadrilaterals, multiple documents corresponding to the batch selection unit 78, which is pressed, are selected in batches. The overview screen providing unit 26 responds to the user's pressing of the batch selection unit 78 for document units, as shown in the image. Figure 7 As shown, a pop-up window (90) appears.

[0089] The pop-up window 90 contains a batch download (batch read) button 92 and a batch upload (batch register) button 94. When the user presses the batch download button 92 with the mouse cursor, one or more registered document files (registered document files located in document DB 32) from the multiple documents selected by the batch selection unit 78 of the document unit are read to the client 14.

[0090] On the other hand, when a user presses the batch upload button 94 in the pop-up window 90 using the mouse cursor, the upload is displayed on the monitor of the client 14. Figure 9 The registration screen is 100A. Additionally, in... Figure 9 For ease of illustration, the diagram shows the relationship between [the two]. Figure 7 The batch selection unit 78 selects 5 documents, and the top 3 documents are related to the allocation table 104A. The following will also... Figure 9 The registration screen 100A is called the registration screen 100A corresponding to the batch selection of document units.

[0091] <Registration screen corresponding to batch selection of document units>

[0092] Next, a detailed explanation of the registration screen 100A corresponding to the batch selection of document units will be provided. Figure 9 ).exist Figure 9In registration screen 100A, allocation table 104A is an allocation table related to multiple documents spanning a case, which differs from the registration screen corresponding to batch selection of work units. Figure 6 However, they are otherwise the same. Below, in Figure 9 The instructions for registration screen 100A address the issue of... Figure 6 The commonalities of the registration screens 100 are appropriately omitted in the explanation.

[0093] Figure 8 This is shown in order to display Figure 9 The flowchart shows the process of processing the allocation table 104A contained in the registration screen 100A by the processor 20 of the file management device 12.

[0094] exist Figure 8 In the S200, the processor 20 functions as the operation receiving unit 24, as shown in Table 62 (see reference). Figure 7 In the process, cases 1 to m and document j are selected as candidate registration destinations. This is in... Figure 7 The process occurs when the batch selection section 78 of the document unit is pressed and the batch upload button 94 is pressed in the pop-up window 90. Here, Case 1 refers to the overview table 62 ( Figure 7 The case at the top of the case information column 70 (refer to) Case m refers to the mth case from the top of the case information column 70, and document j refers to the jth document when the documents shown in document item 68 of the overview table are numbered from left to right. Cases 1 to m and document j refer to m documents (registration destination candidates).

[0095] Next, in S202, the processor 20 functions as the registration screen provider 28, retrieving detailed information for each of cases 1 to m from the case information 40 in document DB 32. The retrieved detailed information is displayed in allocation table 104A (see reference). Figure 9 In the case information section 106, ( ). Additionally, as... Figure 9 As shown, in case information column 106, detailed information for each case is displayed vertically. Additionally, Figure 8 process and Figure 5 The process is the same: after the registration screen providing unit 28 obtains information in each step of S202 to S208, it uses the obtained information to generate and display the allocation table 104A in S210.

[0096] Next, in S204, the registration screen providing unit 28 obtains detailed information about the processes to which documents j in cases 1 to m belong from the process information 42 of the case in document DB 32. The obtained detailed information is displayed in the step information column 108 of the allocation table 104A. In addition, detailed process information is displayed in the step information column 108 corresponding to each case in the case information column 106.

[0097] Next, in S206, the registration screen providing unit 28 retrieves the detailed information of each document j in cases 1 to m from the document information 44 of the case in document DB 32. The retrieved detailed information is displayed in the document information column 110 of the allocation table 104A. In addition, in the document information column 110, the detailed information of each document is displayed corresponding to each case in the case information column 106.

[0098] Next, in S208, the registration screen providing unit 28 retrieves the filenames of the document files registered in document DB 32 from the corresponding information 46 of the registered document files in document DB 32 for cases 1 to m. The retrieved filenames are displayed in the allocation column 112 of the allocation table 104A. Furthermore, in the allocation column 112, the filenames of the registered document files are displayed corresponding to each document in the document information column 110. Figure 9 In the document, “Basic Contract_k1.doc” is a registered document file.

[0099] Next, in Figure 8 In S210, the registration screen providing unit 28 uses the definition information 36 of the registration screen (refer to...). Figure 2 Based on the information obtained in S202-S208, an allocation table 104A is generated and provided to the display of client 14. The above is... Figure 8 Explanation of the process.

[0100] exist Figure 9 In the allocation table 104A, the user allocates the document file stored on the client 14 to the allocation column 112 of the document (registration destination candidate) for which they wish to register the document file, for example, by dragging and dropping. This is consistent with... Figure 6 The allocation table 104 is the same. Figure 9 In the document, “contract_k3.doc” is the allocated document file.

[0101] exist Figure 9 The allocation screen 102A also has Figure 6 Similarly, allocation screen 102 displays detailed information about the documents (registration destination candidates) that is not shown on overview screen 60. Figure 9 In the process, the "Plan Leader" and "Plan Date" in step information column 108, and the "Production Leader" and "Production Scheduled Date" in each document in document information column 110, provide detailed information. Figure 9 In the allocation screen 102A, the user can simultaneously review the detailed information displayed in the allocation table 104A and allocate document files to the allocation columns 112 of each registered destination candidate in the allocation table 104. This prevents the document files from being assigned to the wrong registered destination candidate. When the user presses the mouse cursor or other key located at... Figure 9 When the upload button 122 is pressed on the registration screen 100A, each document file assigned to the allocation column 112 is registered to document DB 32.

[0102] Additionally, as the user allocates a document file to the allocation field 112, the temporary document file 56 and its corresponding information 50 are stored in the temporary storage area 38 (see reference). Figure 2 This point, along with pressing the upload button 122 on the registration screen 100A, moves the temporary document file 56 stored in the temporary storage area 38 and its corresponding information 50 to the document DB 32. This point, along with the user pressing the assigned document file 130 or the registered document file 132 with the mouse cursor on the registration screen 100A, displays the document file's attribute information on the file information display unit 114 and displays a preview of the document file on the preview display unit 116. This point is related to... Figure 6 The registration screen is 100% identical.

[0103] Next, the movement, copying, and replacement of document files in allocation column 112 of the allocation table will be explained. Furthermore, the methods described here can be applied to… Figure 6 , 9 The allocation tables for both parties are 104 and 104A.

[0104] exist Figure 10 The diagram illustrates a scenario where a registered document file 132 configured in allocation column 112 of allocation table 104A is copied to another allocation column 112 of allocation table 104A. As shown in the diagram, a confirmation window 140 is displayed by dragging and dropping the registered document file 132, and the registered document file 132 is copied to the allocation column 112 of the released destination by pressing the copy button 142 within the confirmation window 140. In this case, the filename is displayed as the allocated document file in the allocation column 112 of the released destination. Thus, in allocation screen 102A, the user can copy a registered document file already registered to one allocation destination to a registration destination (candidate registration destination) where no document file is registered. Therefore, compared to temporarily reading the registered document file 132 to the client 14 and allocating it to the allocation column 112 of allocation table 104A, the efficiency of the allocation operation for allocating a document file to allocation column 112 is improved.

[0105] On the other hand, it is preferable to prevent registered document files 132 in allocation column 112 of allocation table 104A from being moved to the allocation column 112 of an unregistered document file's registration destination (registration destination candidate) via drag and drop. This prevents registered document files 132 from being accidentally lost from their registration destination. Furthermore, in this embodiment, it is not permissible to replace an allocated document file 130 in allocation column 112 of a certain registration destination with a registered document file 132 configured in allocation column 112 of another registration destination.

[0106] Furthermore, it is also possible to move, copy, or replace allocated document files 130 (referred to as original document files) configured in allocation column 112 of allocation table 104A to allocation columns 112 of other registered destination candidates via drag and drop, or other means. In this way, by allocating document files stored in client 14 to allocation column 112, the efficiency of the allocation operation of allocating document files to allocation column 112 can be improved compared to sending document files from client 14 to file management device 12.

[0107] In addition, as can be seen from the above, in allocation table 104A, besides the situation where multiple different document files are allocated to multiple registration destination candidates, there may also be a situation where the same document file is allocated to multiple registration destination candidates.

[0108] <Other Implementation Methods>

[0109] Next, other embodiments will be described. In the embodiments described above, a list of contents (refer to Table 62) will be used. Figure 3 The system includes a batch selection unit 76 for process units and a batch selection unit 78 for document units. However, the list table 62 may also include a batch selection unit for selecting multiple documents in batches based on a predetermined document category. Document categories include, for example, contract documents, design documents, and specification documents. "Selecting multiple documents in batches by document category" means, for example, selecting documents with names such as "design document" in batches. In this way, users can select documents of the same category (e.g., documents with names such as "design document") in batches and register these document files uniformly in the registration screen.

[0110] Furthermore, in the embodiments described above, document files are stored in a database. However, it is also possible to register (store) document files in folders designated as registration destinations. For example, the processor 20 of the file management device 12 provides a selection screen that displays a large number of folders and accepts multiple folders from the large number of folders as registration destination candidates from the user, and provides an allocation screen that displays the multiple folders (registration destination candidates) selected on the selection screen and allocates document files from the user to each of the multiple folders (registration destination candidates). At this time, the processor 20 displays detailed information about the folders designated as registration destination candidates in the allocation screen that is not displayed on the selection screen. The detailed information about the folders includes, for example, folder attribute information (creation date and time, update date and time, size, etc.), the number of files stored in the folder, the type of files, etc. In this way, the possibility of registering (storing) document files in the wrong folder is prevented.

[0111] Furthermore, in the embodiments described above, the file management device 12 displays an overview screen and a registration screen on the client 14's display. However, the file management device 12 may also display an overview screen and a registration screen on its own display, allowing the user to perform operations on these screens via the input device (mouse, keyboard, etc.) of the file management device 12.

[0112] In the above embodiments, processor refers to processor in a broad sense, including general-purpose processors (such as CPU: Central Processing Unit, etc.) and special-purpose processors (such as GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic devices, etc.).

[0113] Furthermore, the actions of the processors in the above embodiments can be completed not only by a single processor, but also by multiple processors located in physically separate positions working together. Moreover, the order of the processor's actions is not limited to the order described in the above embodiments and can be appropriately changed.

Claims

1. A document management device, wherein, The file management device includes a processor. The processor performs the following control: displays a selection screen and an allocation screen as distinct screens. In the selection screen, the user selects multiple candidate registration destinations for the electronic file. Following the selection screen, the allocation screen displays the multiple candidate registration destinations selected in the selection screen, and the electronic file is allocated to each candidate registration destination by the user. The processor then performs the following control: in the allocation screen, it displays detailed information about the candidate registration destination that is not displayed in the selection screen.

2. The document management device according to claim 1, wherein, The processor performs the following control: In the allocation screen, when the user selects an electronic file that has been assigned to a candidate registered destination, at least one of the attribute information and preview screen of the selected electronic file is displayed simultaneously with the allocation screen.

3. The document management device according to claim 1 or 2, wherein, In the allocation screen, the processor allows a user to move an electronic file assigned to a registration destination candidate to another registration destination candidate, copy an electronic file assigned to a registration destination candidate to another registration destination candidate, and replace an electronic file assigned to a registration destination candidate with at least one of the electronic files assigned to other registration destination candidates.

4. The document management device according to claim 1 or 2, wherein, In the allocation screen, the processor does not allow the user to move a registered electronic document that is already registered to a registration destination candidate while displaying the registered electronic document that is already registered to a registration destination.

5. The document management device according to claim 1 or 2, wherein, In the allocation screen, the processor allows the user to copy a registered electronic file that has been registered to a registration destination to a candidate registration destination.

6. The document management device according to claim 1 or 2, wherein, The processor performs the following control: The selection screen displays a selection section for users to select multiple registration destination candidates in batches according to a predetermined document classification unit.

7. The document management device according to claim 1 or 2, wherein, The candidate registration destinations are the registration destinations for electronic documents to be produced in each step of a case involving multiple steps, and are specified according to the type of electronic document. The processor performs the following control: The selection screen displays a selection section for users to select multiple registration destination candidates corresponding to each step of the case in batches, by step unit.

8. The document management device according to claim 1 or 2, wherein, The candidate registration destinations are the registration destinations for electronic documents to be produced in each step of a case involving multiple steps, and are specified according to the type of electronic document. The processor performs the following control: The selection screen displays a selection section for users to select multiple electronic documents of the same type corresponding to the same process in batches for registration destination candidates.

9. A computer-readable medium storing a program that causes a computer to perform processing, in which... The control is performed as follows: a selection screen and an allocation screen are displayed as distinct screens. In the selection screen, the user selects multiple candidate registration destinations for the electronic file. Following the selection screen, the allocation screen displays the multiple candidate registration destinations selected in the selection screen, and the electronic file is allocated to each candidate registration destination by the user. And the following control is performed: in the allocation screen, detailed information about the registered destination candidates that is not displayed in the selection screen is displayed.

10. A file management method, wherein, In the file management method described above, The control is performed as follows: a selection screen and an allocation screen are displayed as distinct screens. In the selection screen, the user selects multiple candidate registration destinations for the electronic file. Following the selection screen, the allocation screen displays the multiple candidate registration destinations selected in the selection screen, and the electronic file is allocated to each candidate registration destination by the user. And the following control is performed: in the allocation screen, detailed information about the registered destination candidates that is not displayed in the selection screen is displayed.

11. A computer program product comprising a program that causes a computer to perform a process, in which, The control is performed as follows: a selection screen and an allocation screen are displayed as distinct screens. In the selection screen, the user selects multiple candidate registration destinations for the electronic file. Following the selection screen, the allocation screen displays the multiple candidate registration destinations selected in the selection screen, and the electronic file is allocated to each candidate registration destination by the user. And the following control is performed: in the allocation screen, detailed information about the registered destination candidates that is not displayed in the selection screen is displayed.

Images