JP2012238130A - Document management device, document management method, and computer program - Google Patents

Abstract

An object of the present invention is to provide a document management apparatus capable of reliably and efficiently overwriting an overwrite target attribute with respect to a document whose attribute has been changed through a simple operation.
An application displays a document file included in a library in a file list view pane, and displays attribute information of the selected document file in the property pane. When the attribute information on the property pane 404 is dragged and dropped into the keep tray 421, the application generates an attribute object indicating the attribute information and displays it on the keep tray 421. When the attribute object in the keep tray 421 is selected by the application, the attribute indicated by the selected attribute object indicates the attribute information of the document file selected on the file list view pane 402 when the attribute object is selected. Overwrite with information.
[Selection] Figure 5

Description

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

  A document management system has been proposed that enables metadata search processing by defining metadata such as properties, indexes, and attributes in advance and setting values for the metadata in each document. . In the following description, metadata is described as an attribute. A value for metadata is described as an attribute value.

  Attributes set for a document include a document name, creation date, file size, creator, and comment. For example, the document management system sets attribute values such as “A company estimate. Doc”, “2009/12/10”, “2456”, “Momotaro Miyamoto”, “Important!”, Etc. To do.

  There are two types of attribute values, one that is automatically assigned by the document management system and one that is assigned by the document management system in response to a user operation. For example, the attribute value for each of the document name, creation date / time, file size, and creator is an attribute value automatically given by the document management system when the document is stored in the document management system. On the other hand, the comment is an attribute value given to the document by the document management system in accordance with a user operation.

  The document management system provides, for example, a property screen that has both a function of referring to attributes set in a document and a function of allowing a user to change document attribute settings. The user can access the attributes displayed on the property screen.

  The attributes displayed on the property screen of the document management system are the attributes of the document selected on the file list display screen of the document management system. The file list display screen is a screen that displays a list of documents in the document management system, and provides operations such as selection, opening, and deletion of displayed documents. The property screen displays a list of attributes of the document selected on the file list display screen.

  When the user wants to copy the attribute value of one document to the same attribute value of another document, the user selects the copy source document on the file list display screen. The document management system displays a list of attributes of the selected document on the property screen. The user remembers a pair of an attribute and an attribute value to be copied among the attributes and attribute values displayed in a list on the property screen.

  The user reselects the copy destination document on the file list display screen. The document management system displays a list of attributes of the copy destination document on the property screen. The user overwrites the attribute value of the attribute previously remembered with respect to the attribute value included in the attribute list of the displayed copy destination document.

  Patent Document 1 displays a list of all data attributes in a hierarchical manner, selects a copy source attribute and a copy destination attribute from the list displayed attributes in accordance with a user operation, and selects the copy destination attribute. An information processing apparatus for copying a copy source attribute to an attribute has been proposed.

JP 2009-054084 A

  The user remembers the attribute / attribute value pair that he / she wants to copy, and for the attribute value of the attribute included in the attribute list of the copy destination document displayed on the property screen, the attribute value of the remembered attribute is entered. The method of overwriting depends on the user's memory. Therefore, in this method, when the user reselects the copy destination document, there is a problem that the attribute or attribute value to be copied is forgotten.

  Moreover, the information processing apparatus proposed by Patent Document 1 has the following problems. That is, in this information processing apparatus, the user needs to specify the attribute copy source and copy destination successively on the list display screen. Therefore, if the user does not copy the attribute now but plans to do it later, the user first remembers the position of the attribute of the copy source, and then stores it again after the copy destination is determined. It is necessary to find the position of the copy source by relying on. As a result, there is a possibility that the user forgets the position of the copy source that has been remembered. Also, in the information processing apparatus proposed by Patent Document 1, when the user wants to copy the same copy source attribute to a plurality of copy destination attributes, different copy destinations cannot be specified at once. As a result, the user needs to repeat the copy operation as many times as the number of copy destination attributes.

  The present invention has been made to solve at least one of the above-described problems. SUMMARY OF THE INVENTION An object of the present invention is to provide a document management apparatus capable of reliably and efficiently overwriting an overwrite setting target attribute for a document whose attribute has been changed through a simple operation.

  A document management apparatus according to an embodiment of the present invention displays an electronic document included in an electronic document storage unit in a first area on a display screen, and is selected from electronic documents displayed in the first area. Display means for displaying attribute information of the electronic document in the second area on the display screen, and generating an attribute object indicating the attribute information displayed in the second area in accordance with a cursor operation on the display screen When the attribute object generating means for displaying in the third area on the display screen and the attribute object displayed in the third area are selected, the attribute object is selected on the first area when the attribute object is selected. And attribute setting means for overwriting and setting the attribute information of the electronic document selected by the attribute information indicated by the selected attribute object.

  According to the document management apparatus of the present invention, the attribute information of the electronic document selected on the first area on the display screen is collectively displayed with the attribute information held by the attribute object displayed in the second area. Can be overwritten. Further, according to the document management apparatus of the present invention, the user can add an attribute object that holds the attribute item and attribute value of the attribute to be set to the electronic document in the second area by a simple cursor operation called drag and drop. Can be generated. This eliminates the need for the user to store attribute items and attribute values that the user wants to set in the electronic document. Further, according to the document management apparatus of the present invention, the attribute object held in the second area can be called at an arbitrary timing and set in the electronic document to which the attribute information is copied. This eliminates the need for the user to specify the attribute information copy source and copy destination electronic documents in succession.

It is a figure which shows the system configuration example of this embodiment. It is a figure which shows the structural example of client PC. It is a figure which shows an example of application UI. It is a figure explaining the example of the production | generation process of the attribute object to a keep tray. It is a figure which shows the example of application UI. It is a flowchart explaining the example of an attribute setting process. It is a figure explaining the process which overwrite-sets attribute information. FIG. 10 is a diagram for explaining a modified example of the first embodiment. It is a flowchart explaining the example of an attribute setting process. It is a figure which shows the example of application UI. It is a figure explaining the modification of Example 2. FIG. It is a figure explaining the example of the display process of the attribute object to a sub area | region. It is a figure which shows the example of application UI. It is a flowchart explaining the example of an attribute setting process.

Example 1
FIG. 1 is a diagram illustrating a system configuration example of the present embodiment. The system shown in FIG. 1 includes a document management server 101 and a client PC 102. A document management server 101 and a client PC (Personal Computer) 102 are communicably connected via a network 105. The network 105 is, for example, the Internet or an intranet. Although one client PC 102 is connected to the network 105 in FIG. 1, the system of this embodiment may include a plurality of client PCs 102.

  The document management server 101 provides general document management services such as document storage and retrieval. The document management server 101 has a database for document management. The client PC 102 is a document management apparatus according to this embodiment. The document management server 101 and the client PC 102 may function as a single document management apparatus.

  The client PC 102 includes a document management client that uses a document management service provided by the document management server 101, and the document management client operates on the client PC 102. The document management client is an application that operates on various operating systems such as Microsoft Windows (registered trademark) and Linux (registered trademark). The document management client may be an application that operates on a Web browser included in the client PC 102.

  Note that when the network 105 is the Internet, the document management server 101 may function as a cloud service. The system configuration when the document management server 101 functions as a cloud service is the same as a general cloud service configuration.

  FIG. 2 is a diagram illustrating a configuration example of the client PC illustrated in FIG. FIG. 2A shows the hardware configuration of the client PC. The hardware configuration of the document management server 101 is the same as the hardware configuration of the client PC 102 shown in FIG.

  For example, an input device such as a pointing device such as a keyboard 204 and a mouse 205 and an output device such as a display device 213 are connected to the client PC 102. A network controller (NC) 210 is connected to the network 105 via a predetermined network interface 211 and executes communication control processing with other network devices. The CPU 201 controls the entire client PC 102. The CPU 201 includes at least one processor.

  The memory 202 stores a computer program (control program) used by the CPU 201 for controlling the client PC 102. This control program is a computer program that causes the client PC 102 to execute the document management method according to the present embodiment, and causes the CPU 201 to execute the application 301 shown in FIG. In addition, when the CPU 201 executes this control program, the processes shown in the flowcharts of FIGS. 4, 6, 9, 12, and 14 described later are executed. The memory 202 is, for example, a RAM (Random Access Memory) or a ROM (Read Only Memory). The video interface 212 outputs an image to the display device 213.

  The I / O interface 203 receives input information input in accordance with the operation of the keyboard 204 and the mouse 205. The storage device 208 includes a hard disk drive (HDD) 209. The HDD 209 stores data to be processed by the client PC 102 (for example, a document file or image data). The HDD 209 may store a computer program used by the CPU 201 for controlling the client PC 102. The storage device 208 may include a silicon drive.

  The CD-ROM drive 206 is used as a nonvolatile data source. The interconnection bus 207 mediates communication between the processing units included in the client PC 102. Specifically, the interconnection bus 207 communicates between the processing units in accordance with an operating system such as Microsoft Windows (registered trademark) or Linux (registered trademark) operating on the client PC 102 based on an instruction from the CPU 201. Mediate.

  FIG. 2B shows a functional configuration diagram of the client PC. The document management method of this embodiment is executed by the application 301 shown in FIG. An application 301 is an application included in a document management client that operates on the client PC 102.

  The application 301 includes an application UI unit 302 and a library management unit 303. The application UI unit 302 functions as a display unit that constructs and displays an operation screen (application UI) described later with reference to FIG. In addition, the application UI unit 302 executes a process for receiving various input operations from the user and displaying a processing result by the input operation. For example, the application UI unit 302 receives a document operation request in accordance with the operation of the keyboard 204 and the mouse 205 by the user on the screen of the display device 213, and executes functional processing according to the document operation request. The document operation request is, for example, a document file search request.

  A library management unit 303 manages a library used by the application 301 for processing such as document management. The library management unit 303 executes various document operations such as storing documents in the library, browsing, updating, changing attributes, and searching documents in the library.

  The library is data storage means for storing data for document management. For example, the library stores document data (document file) and document attributes. The library used by the application 301 has two types according to the data storage location. The first is a form of a local library in which the application 301 creates a data storage area in the local HDD 209 and the application 301 itself manages data in this data storage area. When the library takes the form of a local library, the system of the present embodiment can be configured such that the document management server 101 is omitted and only the client PC 102 is provided.

  The second is a shared library form in which the application 301 delegates document management to a document management service provided by the document management server 101. In the form of this shared library, the library management unit 303 passes the document operation request received from the application UI unit 302 to the document management server 101. Then, the library management unit 303 receives a processing result corresponding to the document operation request from the document management server 101 and passes it to the application UI unit 302.

  In the case where the library takes the form of a shared library, the library management unit 303 may be configured to be able to transmit and receive data between the application 301 and the document management server 101. Therefore, the form of the shared library is a preferable form when the document management client is configured to operate on the Web browser. The interface 305 is an interface that connects the library management unit 303 and a local library built in the storage device 208. The interface 305 may be an interface that connects the library management unit 303 and the document management service of the document management server.

  FIG. 3 is a diagram illustrating an example of the application UI. Reference numeral 400 denotes a main window of the application UI. The navigation pane 401 is a display area for displaying a library registered by the application and folders arranged under the library. The library and folder are electronic document storage units for storing electronic documents. The electronic document is, for example, a document file. In the example shown in FIG. 3, libraries 411 to 413 and folders 414 and 415 are displayed. In addition, the folder 414 in which the electronic document related to the approval document is stored is selected as the current location. The application 301 selects a library or a folder according to a user operation. The user can move the current location by selecting a library or a folder arranged under the library on the navigation pane 401.

  The file list view pane 402 is an area (first area) for displaying a document folder stored in a location selected on the navigation pane 401. That is, the application 301 displays the electronic document included in the electronic document storage unit in the first area on the display screen.

  In this example, seven document files are listed on the file list view pane 402. A selection frame 403 indicates that the document file surrounded by the selection frame 403 is selected. In FIG. 3, a document file having a file name “approval document A.doc” is selected. When the user single-clicks a document file displayed on the file list view pane 402 with the mouse 205, the application 301 surrounds the document file with a selection frame 403 to select it. In this example, the mouse pointer 430 is located in the vicinity of the selected document file. The application 301 may select a plurality of document files by sequentially single-clicking a document file to be selected with the mouse 205 while the user presses the shift key of the keyboard 204.

  A property pane 404 is an area (second area) for displaying attribute information of one document file selected on the file list view pane 402. That is, the application 301 displays the attribute information of the selected electronic document among the electronic documents displayed in the first area (file list view pane 402) in the second area on the display screen. In the example illustrated in FIG. 3, the property pane 404 displays attribute information of a document file having a document file name “decision document A.doc”. The attribute information includes attribute items and attribute values. The attribute items are, for example, a name, creation date and time, size, and the like. The attribute value is a value corresponding to the attribute item. In FIG. doc. The attribute value corresponding to the creation date is 2010/06/16 14:35:45. The attribute value corresponding to the size is 522 and 752 bytes.

  Items that can be set in the property pane 404 are defined in advance for each library. Items that can be set are variable depending on the function of the library. For example, in the case of a local library, the same items as attributes that can be set in the file system of the operating system can be set. In the case of a shared library, it is possible to set the same item as the attribute arbitrarily customized by the setting on the document management server 101 side.

  The library management unit 303 has a function of managing attribute items as library capabilities, acquiring attribute item and attribute value information according to the library, and passing the information to the application UI unit 302. When a plurality of document files are selected in the file list view pane 402, no attribute is displayed in the property pane 404, and the number of selected document files is, for example, “<2 documents selected>”. Is displayed.

  The attribute items and attribute values displayed in the property pane 404 can be dragged and dropped onto the keep tray 421 by operating the mouse 205. Drag and drop from the property pane 404 to the keep tray 421 is performed as follows. The user clicks the character string indicating the attribute item or the attribute value with the mouse 205, remains in the clicked state (drag), moves the clicked character string to the keep tray 421, and clicks in the keep tray 421. Release (drop).

  A button 416 is a button for editing the attribute value displayed on the property pane 404. The user can change the attribute value on the property pane 404 by pressing the button 416 to enter the editing state. The attributes that can be changed in the property pane 404 are some attributes, and there are also attributes that cannot be changed. The attributes whose values are mainly managed and updated by the system are attributes that cannot be edited. Even when the button 416 is pressed to change the property pane to the editing state, the item values of these attributes cannot be edited. Will remain. For example, the URL attribute indicating the document position, the creation date attribute indicating the document creation date, and the update date attribute indicating the document update date can be listed as non-changeable attributes. Information indicating whether or not the attribute can be changed in the property pane 404 is stored in advance in the storage unit as changeability information.

  The panel 407 switches display / non-display of panes and windows. A button 408 included in the panel 407 switches display / non-display of the navigation pane 401. A button 409 switches display / non-display of the property pane 404. The button 420 switches display / non-display of the keep tray 421.

  The keep tray 421 is an area (third area) that holds attribute objects as temporary objects. The attribute object is an object indicating attribute information of the document file. The keep tray 421 is a floating window whose position can be arbitrarily moved, and the position can be changed so as not to disturb the display of other user interface components on the main window 400. The recycle bin 422 is used to discard a temporary object created on the keep tray.

  Hereinafter, Embodiment 1 of the present invention will be described with reference to FIGS. FIG. 4 is a flowchart for explaining an example of generation processing of attribute objects in the keep tray. The processing of this flowchart is executed when the CPU 201 develops and executes a control program stored in the memory 202 on the memory 202. First, the application UI unit 302 detects that the attribute information displayed on the property pane 404 has been dragged and dropped onto the keep tray 421 (step S1). Specifically, the application UI unit 302 detects that the attribute information has been dragged with the mouse 205 and has been dropped onto the display area of the keep tray 421.

  Next, the application 301 determines whether or not the dragged and dropped attribute information indicates an attribute that can be changed in the property pane, based on the changeability information stored in the storage unit (step S2). If the dragged and dropped attribute information does not indicate a changeable attribute in the property pane, the process ends. When the dragged and dropped attribute information indicates an attribute that can be changed in the property pane, the application 301 generates a new attribute object on the keep tray 421 (step S3).

  Next, the application 301 arranges the attribute object generated in step S3 at the position where the attribute is dropped on the keep tray 421 (step S4). Subsequently, the application 301 copies the attribute item and the attribute value included in the dropped attribute information to the newly created attribute object on the keep tray 421 (step S5). Thereby, an attribute object corresponding to the dropped attribute information is generated. That is, the application 301 is dropped when the cursor is dragged at the display position of the attribute information on the property pane, and the cursor is moved on the display screen and dropped on the keep tray 421 (on the third area). An attribute object indicating attribute information is generated.

  Next, the application 301 sets a label for display on the newly created attribute object on the keep tray 421 (step S6), and the process ends. The display label includes the copied attribute item and attribute value. After setting the display label, the application 301 displays an attribute object corresponding to the dropped attribute information on the keep tray 421. That is, the application 301 is attribute object generation means for generating an attribute object corresponding to the attribute information displayed on the property pane 404 and displaying it on the keep tray 421 in accordance with a cursor operation on the display screen. In the present embodiment, the cursor operation is a drag / drop of the cursor.

  FIG. 5 is a diagram illustrating the application UI in a state where the attribute object is displayed on the keep tray. Assume that the attribute information 601 of the attribute item “approver” and the attribute value “Takeda” is dropped from the property pane 404 to the keep tray 421. The application 301 generates an attribute object 602 corresponding to the attribute information “attribute approver” and attribute value “Takeda” and displays it in the keep tray 421. In the attribute object 602, “property” indicating that the attribute is a copy, “approver” indicating the attribute item to be held, and “Takeda” indicating the attribute value to be held are set as display labels. ing.

  FIG. 6 is a flowchart for explaining an example of attribute setting processing using the attribute object displayed in the keep tray. The processing of this flowchart is executed when the CPU 201 develops and executes a control program stored in the memory 202 on the memory 202. First, the application UI unit 302 detects that an attribute object displayed in the keep tray 421 has been selected (step S11). For example, when the attribute object is single-clicked with the mouse 205, the application UI unit 302 detects that the attribute object has been selected.

  Next, the application 301 determines whether one or more document files are selected on the file list view pane 402 (step S12). If there is no document file selected in the file list view pane 402, the process ends.

  When one or more document files are selected on the file list view pane 402, the application 301 executes the following processing. The application 301 overwrites and sets the attribute information indicated by the attribute object detected in step S11 to the attribute information of the document file selected in the file list view pane 402 (step S13). .

  That is, the application 301 functions as an attribute setting unit that executes the following processing when the attribute object displayed on the keep tray 421 is selected. When the attribute object is selected, the application 301 overwrites and sets the attribute information of the electronic document selected on the file list view pane 402, that is, the first area, with the attribute information indicated by the selected attribute object.

  FIG. 7 is a diagram for explaining processing for overwriting the attribute information indicated by the attribute object to the attribute information of the document file. In the example of FIG. 7, three document files are selected on the file list view pane 402. Specifically, a document file 811 having a document file name “decision document B.doc”, a document file 812 having a document file name “decision document C.doc”, and a document file name “decision document D.doc” A document file 813 having is selected. In this state, it is assumed that the attribute object 602 indicating the attribute information including the attribute item “authorizer” and the attribute value “Takeda” in the keep tray 421 is selected by a single click with the mouse pointer 430. The application 301 overwrites and sets the attribute value of the attribute item “approver” included in the attribute information included in the document files 811 to 813 to the attribute value “Takeda” held by the attribute object 602.

  According to the first embodiment, the attribute information of a plurality of document files selected on the file list view pane 402 can be collectively overwritten with the attribute information held by the attribute object. Therefore, the user does not need to repeat the same operation as many times as the number of document files for which attribute values are desired to be set.

  Further, according to the first embodiment, an attribute item and attribute value of an attribute to be set in a document file can be generated as an attribute object in the keep tray 421 by a simple cursor operation such as drag and drop. Therefore, it is possible to reduce a risk that the user cannot forget to rewrite the attribute information because the user forgets the attribute item and the attribute value to be set in the document file. Further, according to the first embodiment, the attribute object held in the keep tray 421 can be called at an arbitrary timing and set in the document file to which the attribute information is copied. Therefore, it is not necessary for the user to specify the attribute information copy source and copy destination document files in succession.

  FIG. 8 is a diagram illustrating a modification of the first embodiment. In this example, the application 301 changes the attribute value held by the attribute object on the keep tray in accordance with a user operation. A context menu 1201 is a menu for editing the attribute object.

  When the user changes the attribute value held by the attribute object, the user right-clicks the mouse 205 on the attribute object. As a result, the application 301 displays the context menu 1201 in the vicinity of the attribute object. When the user selects “change value” 1202 via the mouse 205, the application 301 sets the attribute value included in the attribute information corresponding to the attribute object 602 to an editable state. When the user inputs an arbitrary value as the attribute value via the keyboard 204, the application 301 changes the attribute value to the input value.

  The application 301 can also group a plurality of attribute objects in the keep tray 421 in accordance with a user operation using the context menu 1201 displayed in the vicinity of the attribute object 602. When the user selects “Group” 1203 via the mouse 205, the application 301 enters the grouping mode, and another attribute object (attribute object 603 in the example shown in FIG. 8) is left-clicked on the mouse 205. Allow selection.

  When the user selects the attribute object 603 via the mouse 205 and then right-clicks the mouse 205 at an arbitrary position on the keep tray 421, the application 301 displays a context menu near the position. Then, the application 301 calls “end grouping” 1204 included in the context menu to end the grouping. As a result, the application 301 groups the attribute object 602 and the attribute object 603 as one attribute object corresponding to two pieces of attribute information.

  When the user single-clicks the grouped attribute object with the mouse 205, the application 301 places the grouped attribute object in a selected state. The application 301 performs a process similar to the process shown in the flowchart of FIG. 6, and sets all attributes held by the grouped attribute object to the attributes of the electronic document selected on the file list view pane 402. Can be overwritten. Therefore, the application 301 prevents attribute objects having the same attribute item from being grouped into the same group in order to avoid double setting of attribute values. In other words, the application 301 functions as a grouping unit that groups a plurality of attribute objects indicating attribute information having different attribute items among the attribute objects displayed on the keep tray 421 as the first attribute object.

  Further, the application 301 can copy the attribute object on the keep tray 421 in accordance with a user operation using the context menu 1201. When the user right-clicks “duplicate” 1205 included in the context menu 1201 displayed in the vicinity of the attribute object 602 with the mouse 205, the application 301 generates a duplicate of the attribute object 602 on the keep tray 421.

(Example 2)
Hereinafter, Example 2 of the present invention will be described with reference to FIGS. 9 and 10. FIG. 9 is a flowchart for explaining an example of attribute setting processing using the attribute object generated in the keep tray 421. The processing of this flowchart is executed when the CPU 201 develops and executes a control program stored in the memory 202 on the memory 202. The application UI unit 302 detects that the first attribute object displayed in the keep tray 421 has been dragged and dropped onto the second attribute object displayed in the keep tray 421 (step S21). The process in step S21 will be described below with reference to FIG.

  FIG. 10 is a diagram illustrating an example of the application UI in a state where a plurality of attribute objects are generated on the keep tray. On the keep tray 421, attribute information 1001 that holds attribute information including the attribute item “approver” and attribute value “Suzuki”, and attribute information that includes the attribute item “approver” and attribute value “Takeda” are displayed. There is an attribute object 602 to be held. The application 301 detects that the cursor is dragged at the display position of the attribute object 602 that is the first attribute object on the keep tray 421 and dropped at the display position of the attribute object 1001 that is the second attribute object.

  Next, the application 301 determines whether one or more document files are selected on the file list view pane 402 (step S22). If there is no document file selected in the file list view pane 402, the process ends. If one or more document files are selected on the file list view pane 402, the process proceeds to step S23. In the application UI shown in FIG. 10, three document files 1011 to 1013 are selected on the file list view pane 402. Accordingly, the process proceeds to step S23.

  In step S <b> 23, the application 301 searches for document files having attribute items and attribute values held by the second attribute object at the drop destination from the document files selected on the file list view pane 402 (step S <b> 23). Step S23). That is, the application 301 searches for a document file corresponding to the attribute information indicated by the second attribute object that is the attribute object of the drop destination among the document files selected on the file list view pane 402 at the time of dropping. For example, the application 301 searches for document files having the attribute item “authorizer” and the attribute value “Suzuki” held by the attribute object 1001 among the document files 1011 to 1013 in FIG. For example, it is assumed that the document files 1011 and 1012 shown in FIG.

  Next, the application 301 determines whether one or more document files have been obtained by the search in step S23 (step S24). If one or more document files cannot be obtained by the search, the process ends. When one or more document files are obtained by the search in step S23, the application 301 executes the following process. The application 301 overwrites and sets the attribute information of the document file obtained by the search in step S23 with the attribute information indicated by the first attribute object detected to have been dragged and dropped in step S21 (step S25).

  In step S25, the application 301 overwrites the attribute value “Takeda” with the attribute value “Suzuki” corresponding to the attribute item “approver” included in the attribute information of the document files 1011 and 1012 obtained by the search.

  According to the second embodiment, by dragging and dropping an attribute object holding an attribute that the user wants to change (change source attribute) onto an attribute object holding the change destination attribute, the document file having the change destination attribute Only for, the original attribute can be overwritten.

  Therefore, there is no need for the user to perform an attribute search specifying the attribute of the document whose attribute is to be changed before the attribute is changed. As a result, only a specific attribute value of a specific attribute item can be easily changed collectively. Further, according to the second embodiment, since an attribute object having an attribute to be replaced can be specified, a mistake that a new attribute is erroneously set in a document file having an attribute that should not be replaced is prevented. be able to.

  FIG. 11 is a diagram illustrating a modification of the second embodiment. In the keep tray 421 in the application UI shown in FIG. 11, the attribute object 1102 and the attribute object 1103 are grouped. A group frame 1104 indicates that the attribute objects surrounded by the group frame 1104 are grouped as one group. In this example, the attribute object 1102 and the attribute object 1103 are grouped. The attribute object 1102 holds an attribute item “approver” and an attribute value “Takeda”. The attribute object 1103 holds an attribute item “status” and an attribute value “approval”. The group handle 1105 is index information used when the user drags and drops the grouped attribute objects. In the keep tray 421, there is an attribute object 1101 that holds an attribute item “creator” and an attribute value “Umzawa” as another attribute object.

  When the user drags the group handle 1105 with the mouse 205 and drops it on the attribute object 1101, the application 301 executes the process according to the flowchart shown in FIG. As a result, among the document files 1111 to 1113 that are selected on the file list view pane 402, only the document files having the attribute item “creator” and the attribute value “Umezawa” are collectively shown below. The attributes are changed as follows. That is, the attribute item “approver” held by the document file is overwritten to “Takeda”. In addition, the attribute item “status” held by the document file is overwritten to “approved”.

  According to the modification of the second embodiment, the attribute information indicated by the plurality of dragged and dropped attribute objects can be collectively overwritten only for the document file having the attribute information indicated by the drop destination attribute object.

(Example 3)
The third embodiment of the present invention will be described below with reference to FIGS. FIG. 12 is a flowchart for explaining an example of processing for displaying an attribute object in the sub area of the keep tray. The processing of this flowchart is executed when the CPU 201 develops and executes a control program stored in the memory 202 on the memory 202. The sub area is a predetermined area (fourth area) in the keep tray. First, the application UI unit 302 detects that an attribute object displayed in the keep tray 421 has been selected (step S31).

  FIG. 13 is a diagram illustrating an example of an application UI displayed in the third embodiment. On the keep tray 421, there is an attribute object 602 that holds the attribute item “approver” and the attribute value “Takeda”. When the user single-clicks the attribute object 602 via the mouse 205, the application UI unit 302 puts the attribute object 602 in a selected state. Accordingly, the application UI unit 302 detects that the attribute object 602 has been selected.

  Returning to FIG. 12, the application 301 determines whether one or more document files are selected on the file list view pane 402 (step S32). In the example of FIG. 13, seven document files 1421 to 1427 are selected.

  If there is no document file selected in the file list view pane 402, the process ends. When one or more document files are selected on the file list view pane 402, the application 301 executes the following processing.

  The application 301 searches the attribute value included in the attribute information of the document file selected on the file list view pane 402 for the attribute value corresponding to the attribute item held by the attribute object selected on the keep tray. Obtain (step S33). That is, the application 301 executes the following process when the attribute object displayed on the keep tray is selected. The application 301 acquires an attribute value corresponding to an attribute item included in the selected attribute object among attribute values included in the attribute information of the document file selected on the file list view pane 402 when the attribute object is selected. In the example illustrated in FIG. 13, the application 301 searches and acquires an attribute value corresponding to the attribute item “approver” held by the attribute object 602 among the attribute values included in the document files 1421 to 1427. In document files, attribute information may include attribute items for which attribute values are not set. In this case, the application 301 acquires “no setting” as a search result. In this example, for example, “no setting”, “Suzuki”, and “Umezawa” are acquired.

  Next, the application 301 creates an attribute value object corresponding to the attribute value acquired in step S33 on the memory 202 (step S34). An attribute value object is an object that holds an attribute value. When the acquired search result is “no setting”, the application 301 creates an attribute value object indicating no setting. In addition, when the acquired attribute values are duplicated, the application 301 creates one representative attribute value object including the duplicate attribute values. When the attribute value having the same value as the attribute value held by the attribute object detected to have been selected in step S31 is acquired, the application 301 creates an attribute value object corresponding to this attribute value. do not do.

  Next, the application 301 opens and displays the keep tray sub-area on the keep tray (step S35). In the example shown in FIG. 13, reference numeral 1401 denotes a sub area of the keep tray 421. The application 301 also displays a separator 1402 and an open / close switching button 1403 shown in FIG. The separator 1402 separates the area 1404 for displaying the attribute object in the keep tray and the sub area 1401. A switching button 1403 is a button for opening and closing the display of the sub area on the keep tray. After the sub area is opened, the application 301 temporarily closes the sub area by the user pressing the open / close switching button 1403 via the mouse 205.

  Returning to FIG. 12, the application 301 displays the attribute name label in the sub area of the keep tray (step S35). The attribute name label indicates an attribute item. The application 301 displays the attribute item corresponding to the attribute value held by the attribute value object displayed in the sub-region in the vicinity of the attribute name label (step S36). In the example illustrated in FIG. 13, the attribute item “approver” is displayed beside the attribute name label 1410.

  Next, the application 301 displays the attribute value object created on the memory 202 in the keep tray sub-area (step S37). For example, the application 301 adds an attribute value object 1411 corresponding to the attribute value “not set”, an attribute value object 1412 corresponding to the attribute value “Suzuki”, and an attribute value object 1413 corresponding to the attribute value “Umezawa” to the sub area 1401. indicate. That is, the application 301 functions as an attribute value display unit that displays the attribute value acquired in step S33 in the sub area.

  The keep tray sub-area 1401 opened by the processing according to the flowchart described with reference to FIG. 12 does not depend on whether or not the open / close switching button 1403 is operated until the selection state of the attribute object 602 is canceled. Exists on. The selected state of the attribute object is canceled when the user single-clicks the attribute object again with the mouse 205 or operates an object outside the keep tray 421. When the selected state of the attribute object is canceled, the application 301 deletes the display of the keep tray sub-area 1401 from the keep tray 421 and ends the process.

  FIG. 14 is a flowchart illustrating an example of attribute setting processing according to the third embodiment. The processing of this flowchart is executed when the CPU 201 develops and executes a control program stored in the memory 202 on the memory 202. First, the application UI unit 302 detects that the attribute object selected in the keep tray is dragged and dropped onto one of the attribute value objects in the sub area (step S41). For example, the application UI unit 302 detects that the attribute object 602 illustrated in FIG. 13 has been dragged and dropped onto the attribute value object 1412 in the sub area 1401.

  Next, the application 301 searches for a document file having an attribute value held by the attribute value object of the drop destination for the attribute item held by the dragged and dropped attribute object (step S42). That is, the application 301 extracts this document file from the document file selected on the file list view pane. For example, the application 301 searches for a document file having the attribute value “Suzuki” held by the drop-destination attribute value object 1412 for the attribute item “approver” held by the attribute object 602 shown in FIG. The application 301 extracts this document file from the document files 1421 to 1427. That is, the application 301 executes the following processing when the cursor is dragged at the display position of the attribute object selected in the keep tray 421 and dropped at the display position of the attribute value in the sub area. The application 301 searches for a document file corresponding to attribute information including the attribute value displayed at the position where the cursor is dropped, among the document files selected on the file list view pane 402.

  Returning to FIG. 14, the application 301 overwrites the attribute information of the extracted document file with the attribute item and attribute value held by the dragged and dropped attribute object (step S43). That is, the application 301 functions as a means for overwriting the attribute information of the retrieved document file with the attribute information indicated by the attribute object selected on the keep tray 421.

  According to the third embodiment, when the user drags and drops the selected attribute object onto the attribute value object displayed in the sub area, the application 301 executes the following process. The application 301 overwrites and sets the dragged and dropped attribute items and attribute values for the document file having the attribute value of the attribute value object of the drop destination among the document files selected on the file list view pane 402.

  Therefore, there is no need for the user to perform an attribute search specifying the attribute of the document whose attribute is to be changed before the attribute is changed. As a result, only a specific attribute value of a specific attribute item can be easily changed collectively. Further, according to the third embodiment, since an attribute to be replaced can be specified, it is possible to prevent a mistake that a new attribute is erroneously set in a document file having an attribute that should not be replaced. Further, according to the third embodiment, therefore, unlike the second embodiment, it is not necessary to prepare two attribute objects having the same attribute item in the keep tray. In the third embodiment described above, drag and drop is performed on the attribute object 602. However, the drag and drop may be performed on the attribute value object displayed in the sub area. Alternatively, the attribute value object displayed in the sub area may be dragged and dropped on the attribute object 602. As a result, the attribute information can be easily replaced by the user.

(Other examples)
In the above embodiment, when the attribute object 602 is single-clicked, the attribute object attribute setting process is not executed unless a file is selected. As another embodiment, the application 301 may execute this attribute setting process when a file is selected by the mouse 205 after the attribute object 602 is single-clicked.

The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed. In this case, the program and the storage medium storing the program constitute the present invention.

101 Document management server 102 Client PC

Claims (7)

An electronic document included in the electronic document storage unit is displayed in a first area on the display screen, and attribute information of the selected electronic document among the electronic documents displayed in the first area is displayed on the display screen. Display means for displaying in the second area;
Attribute object generating means for generating an attribute object indicating the attribute information displayed in the second area in accordance with a cursor operation on the display screen and displaying the attribute object in the third area on the display screen;
When the attribute object displayed in the third area is selected, the attribute indicating the attribute information of the electronic document selected on the first area when the attribute object is selected is indicated by the selected attribute object A document management apparatus comprising: attribute setting means for overwriting setting with information. The cursor operation is a drag / drop of a cursor,
The attribute object generation means is configured such that the cursor is dragged at the display position of the attribute information in the second area, and the dragged cursor is moved on the display screen and dropped on the third area. 2. The document management apparatus according to claim 1, wherein an attribute object indicating the attribute information is generated and displayed in the third area. The attribute setting means is configured such that the cursor is dragged at the display position of the first attribute object in the third area, and the dragged cursor is dropped at the display position of the second attribute object in the third area. The electronic document corresponding to the attribute information indicated by the second attribute object among the electronic documents selected on the first area at the time of the drop, and the attribute information of the retrieved electronic document The document management apparatus according to claim 2, wherein the document information is overwritten with attribute information indicated by the first attribute object. The attribute information includes an attribute item and an attribute value,
The attribute object displayed on the said 3rd area is provided with the grouping means which groups the some attribute object which shows the attribute information from which an attribute item differs mutually as said 1st attribute object. 3. The document management apparatus according to 3. The attribute information includes an attribute item and an attribute value,
The attribute setting means includes
When the attribute object displayed in the third area is selected, the attribute value included in the attribute information of the electronic document selected on the first area when the attribute object is selected is selected. Attribute value display means for acquiring an attribute value corresponding to an attribute item included in the attribute object and displaying the acquired attribute value in a fourth area;
When the cursor is dragged at the display position of the attribute information indicated by the attribute object selected in the third area, and the dragged cursor is dropped at the display position of the attribute value in the fourth area The electronic document corresponding to the attribute information including the attribute value displayed at the position where the cursor is dropped is searched from among the electronic documents selected on the first area. The document management apparatus according to claim 2, further comprising means for overwriting attribute information with attribute information indicated by the selected attribute object. Displaying an electronic document included in the electronic document storage unit in a first area on the display screen;
Displaying the attribute information of the selected electronic document among the electronic documents displayed in the first area in a second area on the display screen;
Generating an attribute object indicating attribute information displayed in the second area according to a cursor operation on the display screen and displaying the attribute object in the third area on the display screen;
When the attribute object displayed in the third area is selected, the attribute indicating the attribute information of the electronic document selected on the first area when the attribute object is selected is indicated by the selected attribute object A document management method comprising: overwriting with information.   A computer program for causing a computer to execute the document management method according to claim 6.

Images