JP2006338115A - Data management device and data management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a document management system for efficiently setting the same index value as that of a certain document in a target document by an intuitive and easily understandable operation by using a user interface. <P>SOLUTION: When performing an operation to overlap a reference document whose index should be set on a target document in which an index value is set by a GUI operation using a mouse, an index value is captured from a reference document, and an operation to set the value in each item corresponding to the target document can be selected. Thus, it is possible to provide a data management device characterized to have a means for easily setting a plurality of index values only by a GUI operation without opening a setting screen. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a document index registration method set for a document in order to efficiently classify documents in a database or the like.

  For example, in order to classify and organize documents registered in a document management system, an item for setting a classification identifier called an index is registered as an attribute item for a document, and a common index representing the document characteristics is registered. .

  In a document management system classified by an appropriate index, sorting can be done efficiently by sorting by index name, and data trends can be easily grasped by the number of documents classified in each category. This makes it possible to efficiently search for necessary documents. How efficiently an index can be set for each document is important for realizing efficient document management.

As a conventional example, for example, Patent Document 1 can be cited.
JP 2001-243216 A

  To classify documents is to classify the documents that belong to the same type into some groups according to a certain rule, but how to distinguish the appropriate group for the contents of the documents. An identifier (hereinafter referred to as an index) is also assigned.

  To set document properties for one document, select the document, open the screen for setting the properties of the document, set the value arbitrarily, and close it. If registered, an appropriate index for each of them can be efficiently set as an index. Select multiple documents, open a window to set index values for them, and enter the entered values at once. There is a technique for setting an index efficiently by using the setting technique.

  However, if a large number of index items are set in the document management system and values for all index items already set in a document A are to be set in a target document B, the property setting screen of the document B is displayed. There is a problem in that it is necessary to set the same value for each index item corresponding to document B while opening and referring to each index item of document A.

  Therefore, an object of the present invention is to provide a document management system that can efficiently set the same index value as a certain document to the target document.

  According to the present invention, when an operation for superimposing a reference document on which an index is to be set is performed on a target document on which an index value is set by a GUI operation using a mouse or the like, the index value is obtained from the reference document, and the target document is obtained. Data characterized in that it is possible to select an operation to set a value for each corresponding item of a document, and to provide a means for easily setting a plurality of index values only by a GUI operation without opening a setting screen. A management device is provided.

  As described above, according to the present invention, for example, as a technique for classifying documents, there has conventionally been a system that sets an index value as an identifier for classification and sorts by the index value. In order to set an index, it is necessary to set an appropriate index value for each document. However, when a large number of documents are registered, it is necessary to open the user interface for each document and set one document at a time. In the case where there are many indexes that can be set for a document, since the setting efficiency is further poor, it takes time and may cause erroneous setting.

  On the other hand, the setting values of the documents can be combined and combined with an intuitive user interface as if the actual documents are superimposed, so that the index setting efficiency can be improved.

  DESCRIPTION OF EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a block diagram showing a schematic configuration of a document management system (hereinafter referred to as DMS) according to an embodiment of the present invention.

  As shown in FIG. 1, the DMS is constructed in the network 11.

  This system basically includes a DMS server 12 and a DMS client 13 in the network 11. The DMS server 12 is a computer that manages the entire system. In addition to network processing realized by a known technique, the DMS server 12 mainly constructs a document database, transmits / receives document data between devices, and performs security processing. It performs exclusive control processing between users, management of databases that store document data, and the like. Details of the DMS server 12 will be described later with reference to FIG.

  The DMS client 13 is a personal computer on which a user actually inputs, references, and outputs document data. Only one DMS client 13 is shown for convenience in FIG. 1, but in the present embodiment, a plurality of DMS clients 13 are used. It is assumed that the client 13 is connected to the network 11. Details of the DMS client 13 will be described later with reference to FIG.

  Like the scanner 15, the printer 14 is shared by a plurality of DMS clients 13 using a known technique, and each DMS client 13 can control the DMS clients 13 via the network 11. In the present embodiment, the printer 14 mainly plays a role of printing out document data stored in the DMS server 12.

  The scanner 15 is a device that reads data such as characters, graphics, and images printed or written on paper, converts the data into image data, and outputs the image data. The scanner 15 is connected to the network 11. Each DMS client 13 can share the scanner 15 using a known technique, and can control its operation via the network 11.

  The modem 16 performs transmission / reception processing of electronic mail and FAX transmission / reception with other network systems. The modem 16 is also shared by a plurality of DMS clients 13, and each DMS client 13 can control the DMS clients 13 via the network 11.

  The CD-ROM drive 17 is shared by the DMS server 12 and the plurality of DMS clients 13, and the DMS server 12 and the like can be controlled via the network 11. In this embodiment, the CD-ROM drive 17 is mainly used for installing the DMS control program of the DMS server 12 and the DMS client 13.

  In this embodiment, the printer 14, the scanner 15, the modem 16, and the CD-ROM drive 17 are connected to the network 11. However, the present invention is not limited to this. For example, these are directly connected to the DMS client 13. A form of connection can also be adopted.

  FIG. 2 is a block diagram illustrating the configuration of the DMS server 12 in more detail.

  The CPU (central processing unit) 22 performs processing as shown in the flowcharts described later in accordance with each control program stored mainly in the external storage device 28.

  A ROM (read-only memory) 23 corresponds to a basic determination program of a flowchart to be described later, a character font used for display / printing, and an electrical signal output by pressing a key from the keyboard 25 as an input device. It stores character code tables and preset values.

  A RAM (Random Access Memory) 24 has a work area required during each process.

  Reference numeral 241 denotes a basic I / O program area, which is a work area required when the basic determination program stored in the ROM 23 operates. The CPU 22 first activates the basic I / O program and then activates the OS on which the DMS operates.

  Reference numeral 242 denotes a work area for operating the OS.

  Reference numeral 243 denotes an area where the DMS server program operates, and is an area where the DMS server program 282 stored in the HDD 28 is loaded.

  An area 244 is loaded with fixed data such as resources of the DMS data 283 stored in the external storage device 28 required for the operation of the DMS program.

  Reference numeral 245 denotes a work area for editing database data or the like temporarily stored in the HDD 28 for operating the DMS program.

  A work area 246 is used in other processes.

  Reference numeral 25 denotes a keyboard as an input device.

  Reference numeral 26 denotes a pointing device as an input device. This embodiment uses a mouse.

  Reference numeral 27 denotes a display device, and the administrator of the DMS determines the progress of the operation and the result according to the display.

  Reference numeral 28 denotes an external storage device. In this embodiment, the external storage device 28 is a general fixed disk.

  The external storage device 28 is a basic program 281 for managing a network and a DMS server program 282 that is a program for managing a DMS, and includes a program for managing and controlling index items. Next, DMS data 283 such as fixed data such as resources required for the operation of the DMS program, and a scan program 284 that is a control program for managing the scanner 15 are recorded, and this DMS server A database list for managing the database list 285, a database format for storing and managing document data, a region DMSDB 286 for managing users, groups, privileged data, index data, documents, folders, etc., and An area DMSVOLUME 287 for storing a corresponding document entity is included. The DMS annotation 288 stores actual data for display and print development of annotation registered in this database.

  The flexible disk drive (FDD) 29 is used not only for storing document data in the flexible disk (FD) 2A, but also for installing the DMS control program recorded on the flexible disk 2A.

  The control program is installed in areas such as the DMS server program 282 and the DMS data 283 of the HDD 28. The contents recorded on the flexible disk 2A will be described later with reference to FIG.

  Note that a CD-ROM drive and a CD-ROM storing a DMS control program may be used instead of the FDD 29 and the FD 2A.

FIG. 3 is a block diagram illustrating the configuration of the DMS client 13 in more detail.
The CPU (central processing unit) 32 performs processing as shown in a flowchart described later, mainly in accordance with the DMS client control program 371 stored in the external storage device 37.

  A ROM (read only memory) 33 corresponds to a basic determination program of a flowchart to be described later, a character font used for display / printing, and an electrical signal output by pressing a key from the keyboard 34 as an input device. A character code table for outputting a character code, a preset value, and the like are stored.

  Reference numeral 34 denotes a keyboard as an input device.

  A RAM (Random Access Memory) 35 has a work area required during each process.

  Reference numeral 351 denotes a basic I / O program area, which is a work area required when the basic determination program stored in the ROM 33 operates. The CPU 32 first activates the basic I / O program, and then activates the OS on which the DMS operates.

  Reference numeral 352 denotes a work area for operating the OS.

  Reference numeral 353 denotes an area where the DMS client operates, and an area where the DMS client control program 371 stored in the HDD 37 is loaded.

  Reference numeral 354 denotes an area (DMS client data) in which fixed data or the like such as resources of the DMS data 373 stored in the HDD 37 required for the operation of the DMS client program is loaded.

  Reference numeral 355 denotes a work area used in other areas.

  Reference numeral 36 denotes a pointing device as an input device, and a mouse is used in this embodiment.

  Reference numeral 37 denotes an external storage device, which is necessary for the operation of the DMS client control program 371 that is a program for performing data communication with the DMS server 12, the scan program 372 that is a program for controlling the scanner 15, and the DMS program. And DMS data 373 such as fixed data such as resources.

  An area 374 for managing a list of databases registered for reference by the DMS client 13 is provided. In this list, not only the DMS server 12 but also a list of databases managed by DMS servers on different networks is registered.

  Reference numeral 38 denotes a display device, and a user working on the DMS client 13 determines the progress of the operation and the result in the state of the DMS user interface displayed on the display device 38.

  A flexible disk drive (FDD) 39 is used to store document data on the flexible disk 3A, and is used to install this DMS control program recorded on the FD 3A.

  The control program is installed in the DMS client program 371, the scan program 372, the DMS data 373, etc. in the HDD 37. The contents recorded on the FD 3A will be described later with reference to FIG.

  The FDD 39 and the FD 3A may be a CD-ROM drive and a CD-ROM, respectively.

  FIG. 4 is a diagram showing the details of the area 286 (DMS DB) for managing the database of FIG. 2 in more detail. This includes database management information such as users and groups managed by the database, and registered document information. In FIG. 4, information groups 40 and 41 each indicate data of one cabinet. Therefore, the following data exists as many as the number of cabinets registered in the server.

  Reference numeral 42 denotes a cabinet identifier. In this embodiment, a cabinet name “claim management” is stored.

  A user list 43 stores a list of users registered in the cabinet. Use this user name to connect to the cabinet.

  A group list 44 stores a list of groups registered in the cabinet. Used when you want to perform the same management for multiple users. Users registered in the 43 user lists are arbitrarily registered in each group.

  Reference numeral 45 denotes a printer list, in which a list of printers that can be used in this cabinet is registered. In the system of the present invention, the DMS client 13 can print only from printers registered in this area.

  46 is an index list. The index is used for purposes such as document classification and search. It is registered in units of cabinets, and index titles, a list of already registered indexes, and the like are managed. Details will be described with reference to FIG.

  47 is a folder list. A folder created in the cabinet is registered.

  Reference numeral 48 denotes a document list. All the attribute information of documents registered in this cabinet is stored. Details will be described with reference to FIGS.

  Reference numeral 49 denotes an annotation list. Annotation attributes registered in this cabinet are registered.

  4A is a volume list. The entity of the document registered in this cabinet is stored in the DMS Volume 287 in FIG. 2, but a pointer to it is stored.

FIG. 5 shows the contents of the index list 46 of FIG. 4 in more detail.
The information groups 50 and 51 are information units of the index list, and indexes already registered in the document are stored in the order of registration, and this unit is stored for the number of index items that can be registered in each document in the cabinet. When the user selects a document on the client 13 and sets an index value for the document, this information unit is displayed as an option for prompting input assistance as shown in the user interface 99 of FIG.

  52 is an index identifier of the information unit 50 and represents the identifier of the index item. In this embodiment, “occurrence department” is assigned. This value is used to identify the index item in internal processing.

  53 is an index value already set in the document, which means that an index value of “after service” is already registered in the document in the index item of “department department”.

  Similarly, 54, 55, 56, and 57 are index values already registered in the document.

  58 and 59 are also index value storage areas, which means that the index has not been registered yet and the registered list is not filled.

  FIG. 6 is a diagram showing in detail the contents of the document information stored in the document list 48 of FIG.

  Reference numerals 60 and 61 denote document information units, which are stored as many as the number of registered documents.

  62 is attribute information indicating the identifier of the document. In the present embodiment, information “claim 1” is allocated.

  Reference numeral 63 denotes document attribute information, which stores information related to document attributes such as a document name and a creator.

  Reference numeral 64 denotes a creation date and time. Stores the date and time when this document was registered in the document management system. In this embodiment, 2002/09/20 is stored.

  65 is an update date. The date and time when an unspecified user made a change to the document and updated it is stored. In this embodiment, 2002/12/25 is stored.

  66 is the access date and time. Stores the date and time when an unspecified user accessed the document by an operation such as reference. In this embodiment, 2002/12/26 is stored.

  67 is an ACL (access control list) for this document. A list of security levels when each user accesses this document is stored.

  68 is one of index items that can be set in this document, and the user can set an index value by a user interface as shown by 97 in FIG. In this area, the set index value is stored. In the present embodiment, the value “shipment” is set.

  Similarly, 69 and 6A are index items that can be set in this document, and 69 indicates that an index value “replacement” is already stored in “transport” 6A.

  The information group 61 will be described with reference to FIG.

  FIG. 7 is a diagram showing details of the information group 61 in FIG.

  71 corresponds to the information group 61 shown in FIG.

  Reference numeral 72 denotes attribute information indicating an identifier of the document. In the present embodiment, information “claim 2” is allocated.

  Reference numeral 73 denotes document attribute information, which stores information relating to document attributes such as a document name and a creator.

  74 is a creation date. Stores the date and time when this document was registered in the document management system. In this embodiment, 2003/09/18 is stored.

  75 is an update date. The date and time when an unspecified user made a change to the document and updated it is stored. In this embodiment, 2004/10/25 is stored.

  Reference numeral 76 denotes an access date and time. Stores the date and time when an unspecified user accessed the document by an operation such as reference. In this embodiment, 2004/10/25 is stored.

  77 is an ACL (Access Control List) for this document. A list of security levels when each user accesses this document is stored.

  Reference numeral 78 denotes one of index items that can be set in this document, and the user can set an index value by a user interface as shown by 97 in FIG. In this area, the set index value is stored. This embodiment indicates that no index value is set.

  Similarly, 79 and 7A are index items that can be set in this document. 69 indicates that “not confirmed” 6A indicates that an index value “exchange” has already been stored.

  FIG. 8 is a diagram showing a user interface of the client 13 shown in FIG.

  The window is composed of windows, and 81 is a tree view area. The list of the DMS database list 285 shown in FIG. 2 of the DMS server 12 shown in FIG. In the figure, a database named “My Cabinet” and a database named “New Cabinet” are referred to.

  In this embodiment, the database of the DMS server 12 is displayed, but a database created by the DMS client 13 may be used.

  Reference numeral 82 denotes a content area which displays a list of documents stored in the database. This embodiment indicates that a list of documents registered in the folder “new folder” in the database “my cabinet” selected in the tree view 81 is displayed.

  Reference numerals 84 and 85 denote registered documents, which are displayed in a thumbnail format representing a general overview of the document, but may be displayed in a list format.

  Reference numeral 84 denotes an example in which the document name “claim 1” is registered and managed by the information group 60 shown in FIG.

  Reference numeral 85 denotes an example in which the document name “Claim 2” is registered and managed by the information group 71 shown in FIG.

  A pointer 86 is operated by the mouse 36 of the client 13. This pointer can be used to point to the document, or the document can be moved using the button operation of the mouse 36 together.

  In the figure, an operation of selecting the document 84 and attempting to overlap the document 85 is shown.

  FIG. 9 shows an example of a user interface equipped to display the document property “claim 1” shown in FIG.

  Reference numeral 91 denotes a document name. This indicates that the document name is “Claim 1”.

  Reference numeral 92 denotes the storage location of this document. It is stored in the “new folder” of the database “My Cabinet”.

  Reference numeral 93 denotes a thumbnail, which displays the same as the thumbnail 84 shown in FIG.

  Reference numerals 94, 95, and 96 are items used in the description of the embodiment of the present invention and represent index items.

  Reference numeral 94 denotes “occurrence department” of the identifier 52 of the information group 50 in the index list shown in FIG.

  Reference numeral 95 denotes an identifier “cause location” of the information group 51 in the index list shown in FIG.

  Reference numeral 96 similarly represents an identifier of the index list.

  Reference numeral 97 denotes a user interface for setting an index value of the index item 94, which displays the value “shipment” of the index 68 shown in FIG.

  Reference numeral 98 denotes a user interface for setting the index value of the index item 95, which displays the value “transport” of the index 69 shown in FIG.

  Reference numeral 99 denotes a user interface for setting an index value of the index item 96, which displays the value “exchange” of the index 69 shown in FIG. Further, as shown in the figure, a selection method and an input method of arbitrary input are possible.

  FIG. 10 shows an example of a user interface displayed when a document is overlaid on another document using the user interface as shown in FIG. This user interface can be used to select an operation after overlapping. As a result, it is a feature of the present invention that specified operations can be collectively executed on a document.

  Reference numeral 101 denotes a document being operated. In this embodiment, since the document 84 shown in FIG. 8 is superimposed on the document 85, documents “claim 1” and “claim 2” are displayed in a list. The document displayed above is a target document, and the document displayed below is a reference document. Therefore, in the present embodiment, the processing is to set the document of “claim 2” with reference to the index value of the document of “claim 1”.

  Reference numeral 102 denotes a user interface for selecting an operation related to document combination. In addition to the functions used in the present invention, an operation for combining document entities, an operation for registering as a separate document after combining, an operation for combining only print information, an operation for registering only macro processing for a document, etc. are performed with this user interface. You can choose. In the present invention, the operation “Combine Index Values” for combining the index items is selected from these.

  FIG. 11 is a flowchart for explaining operations necessary for explaining the present invention. Details will be described later in Examples.

  FIG. 12 explains the contents of the flexible disk storing the control program of this document management system. This document management system is supplied in such a format and installed in the HDD 28 or the HDD 37.

  This may be a CD-ROM.

  An area 121 manages the format format of the medium, the directory management format, the name given to the medium, and the like.

  Reference numeral 122 denotes an area for managing directory information.

  An area 123 stores a server program for the document management system, and is stored in the DMS server program 282 of the HDD 28 by installation.

  An area 124 stores fixed data of the document management system, and is stored in the DMS data 283 of the HDD 28 by installation.

  An area 125 stores a document management system client program, which is stored in the DMS client program 371 of the HDD 37 upon installation.

  An area 126 stores fixed data of the document management system and is stored in the DMS data 373 of the HDD 37 by installation.

  Next, in order to explain the present invention, an example in which the user sets the index value of the reference document 84 to the index value of the target document 85 using the user interface in the user interface shown in FIG. The main processing and operation of the present invention in which an operation can be completed simply by overlapping documents using an interface will be described with reference to the flowchart of FIG.

  First, in the flowchart of FIG. 11, in step 110, initialization processing is performed. The DMS server 12, DMS client 13, printer 14, scanner 15, modem 16, CD-ROM drive 17, and network system 11 are activated. Each of the startup processes is performed, and the connection process to the network system is performed via the network 11, but since these can be performed by a known technique, the details are omitted. After this processing, it is assumed that the document can be operated using the user interface in the state shown in FIG.

  The operation of this patent is performed by operating the mouse cursor 86 which is a user interface shown in FIG. 8 using the mouse 36 shown in FIG.

  In step 111, it is confirmed whether or not the reference document 84 overlaps the target document. This determination process is performed by a program stored in the DMS client program 371 shown in FIG. Since the actual determination process can be performed using a known technique, details are omitted.

  If it is determined that they do not overlap, the process is returned and the determination process is performed again. If it is determined that they overlap, the process moves to step 112.

  In step 112, the property of each document is referred to and processing for obtaining the value of each index set in the document is performed. The index item and each set value of the reference document 84 can be obtained from the document list information group 60 shown in FIG. 6 stored in the DMSDB 286 shown in FIG. Information of indexes 68, 69, and 6A can be acquired from the stored information, and a pointer is set here.

  Similarly, the process of acquiring the index value of the target document 85 is performed, and similarly, it can be acquired from the information group 71 shown in FIG. Information of indexes 78, 79, and 7A shown in FIG. 7 is acquired, and a pointer is set here.

  In step 113, a user interface as shown in FIG. 10 is activated for the user to confirm the operation from the above information. In the case of this patent, since the reference document 84 is overlaid on the target document 85, the document is displayed as indicated by 101.

  Next, in step 114, processing for selecting an operation to be performed on the superimposed documents is performed. A process to be performed on the document displayed in 101 on the user interface 102 shown in FIG. 10 is selected. In this user interface, operations such as combining document entities, registering as a separate document after combining, operation combining only print information, and registering only macro processing for a document can be selected. In this embodiment, since an index value is set, “join index value” is selected from options. This option is temporarily stored as a flag in the “other WORK” 355 in the RAM 35 area of the DMS client 13.

  In step 115, the process selected by the user interface 102 is determined with reference to the above flag. In the case of other processing, the process proceeds to step 116. In the case of “index combination” for explaining the present invention, the process proceeds to step 118.

  In step 116, what is determined to be other processing is shifted, but it is determined whether or not an operation is not selected or invalid. If the process cannot be determined because no operation has been selected, the process returns to step 114. In the case of other processing, the processing shifts to 117. Actually, there is a decision branch process for each determined process, but in this embodiment, the process in step 117 will be described as other processes, and a detailed description for each operation will be omitted.

  In step 117, other processing is performed. After performing the process, the process proceeds to step 122 and the process ends.

  Since it is determined in step 118 that index combination processing is to be performed, processing for designating a pointer for each index is performed. First, the pointer of the reference document 84 shown in FIG. 8 is set to the index 68 shown in FIG. On the other hand, the pointer of the target document 85 is set to the index 78 shown in FIG. Thereafter, the process up to step 121 is performed as a process of combining one index. If there is an index to be combined next, the process returns to step 118 again, and the pointer is moved to the next index.

  In step 119, it is determined whether something is set in the target document. If not set, the process proceeds to 120. In this embodiment, since the value of the index 78 of the target document 85 is not set, it is determined that the index is not set, and the process proceeds to step 120 in order to perform a normal overwriting process.

  In step 120, processing for setting the index value of the reference document as the index value of the target document is performed. In this embodiment, since the index value “shipment” is set in the index 68 of the reference document 84, the value is set as “shipment” in the corresponding index 78 of the target document 85. Thus, one index value is set, and the process proceeds to step 121.

  In step 121, it is determined whether or not there is an index value to be combined. If the index exists by moving the pointers of the target document and the reference document, the process returns to 118 for the process of combining the next index item. If it is determined that all indexes have been combined, the process proceeds to step 122.

  In step 122, end processing is performed. Perform memory release processing.

  Next, a series of processes when a certain value is set as the index value of the target document in step 119 will be described. In this embodiment, an example of index values set in the index 69 shown in FIG. 6 of the reference document 84 and the index 79 shown in FIG.

  In step 124, it is determined whether or not the set value is the same as the index value of the reference document. In the case of the present embodiment, “transport” is set in the index 69 of the reference document 84, whereas “not confirmed” is set in the index 79 shown in FIG. It is determined as a different value. In this case, the process proceeds to step 125. If it is determined that the values are the same, no processing is performed, and the processing proceeds to step 121 in order to perform processing for the next index. In the present embodiment, the index 6A of the reference document 84 is set to “exchange”, whereas the index 7A shown in FIG. 7 of the target document 85 is also set to “exchange”. It is determined that the values are the same, and the process proceeds to step 121.

  In step 125, a warning message indicating that the index value has already been set is displayed. Since the user performs overwriting or a value is set, the user can select whether or not to perform index combining processing for this index. If the user selects to overwrite, the process proceeds to step 120. In the present embodiment, the value of the index 69 shown in FIG. 6 of the reference document 84 is “transportation”, whereas the value of the index 79 shown in FIG. The value “missing confirmation” is deleted and the value “transport” is set.

  In this step, if nothing is selected, the index value of the target document is not changed.

  In step 126, the process selected by the user is determined by the confirmation message displayed in step 125, and the process proceeds according to the determination. If it is determined that nothing is to be performed, the process proceeds to step 121, and if it is determined to perform overwriting, the process proceeds to step 120.

  With the above process, the process of combining the index value set in the reference document 84 with the corresponding index of the target document 85 using the user interface shown in FIG.

  In the conventional document management system, there is a system in which an index representing document characteristics is set for document classification, and the same index is set for documents having common characteristics. Because it is necessary to open and set the user interface as shown, it is not possible to provide an efficient operation to set an index on multiple documents, and it takes time to set and causes incorrect settings. It was a problem.

  When setting index values that represent document characteristics, select an operation when overlaying thumbnails representing each document with an easy-to-understand operation such as overlaying actual documents manually using the user interface shown in FIG. Thus, the present invention is characterized in that the index values set in the document can be easily combined.

  In this embodiment, an example of index values has been described. However, in this patent, format information, print information, job information in which macro processing for a document is recorded, etc., which are attributes that can be set for a document in the document management system. It is also possible to realize a process of combining and combining these by the same operation.

It is a block diagram explaining the schematic structure of the DMS system which shows one Example of this invention. 2 is a diagram illustrating in detail a configuration of a DMS server 12 illustrated in FIG. It is a figure showing the structure of the DMS client 13 shown in FIG. 1 in detail. FIG. 3 is a diagram showing in detail the configuration of a DMS database list 286 shown in FIG. 2. It is a figure showing the structure of the index list | wrist 46 shown in FIG. 4 in detail. It is a figure showing the structure of the document list 48 shown in FIG. 4 in detail. It is a figure showing the structure of the information group 61 shown in FIG. 6 in detail. It is an example of a user interface for explaining an operation in which a user selects a document with the DMS client 13 and sets an index value in another document in the document management system configured by this patent. It is an example of a user interface for explaining an operation in which a user selects an arbitrary document with the DMS client 13 and sets an index value in the document management system configured by this patent. FIG. 8 is an example of a user interface for selecting an operation to be performed on a document when the document is overlaid on the user interface described in this patent. It is a flowchart explaining the procedure which a user selects a document in the document management system comprised by this patent, and sets an index value to an object document. The contents of the FDs 2A and 3A for supplying a control program for the document management system will be described.

Claims (1)

  When an index is set as an identifier for document classification in a document management system, an operation for superimposing a document that refers to an index value on a target document for which the index value is synthesized is performed using a user interface technique realized by a known technique. Means for realizing, means for selecting an operation to be performed on the target document using a user interface technique realized by a known technique, and means for acquiring an index value of each document from the database according to the selected operation Depending on the index setting status of each document and each document, if the merge destination value is not set, the reference source index value setting means, and if any value is set for the merge destination, the reference document and the target document If the index value is already set for the target document Means for displaying and selecting a user interface that prompts the user to select whether to perform overwriting processing or no processing, and means for performing a combining process on all indexes when a plurality of index items are set And a data management device.

Images