JP3493354B2 - Document search method - Google Patents

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a document management system for managing documents using an electronic computer, and more particularly to managing documents managed by an electronic computer regardless of the management system of the file system of the computer. -Relates to a document management method suitable for classification.

[0002]

2. Description of the Related Art At present, companies and the like use documents such as word processing software and spreadsheet software on personal computers and workstations to create and manage documents.

Conventionally, on these computers, documents are managed in the form of data files on the file system using a file system which is a subsystem of the OS (operating system). For example, in the Microsoft Windows operating system (trade name: Microsoft Corporation, USA), it is possible to manage documents using a control file called a directory on a hierarchical file system that manages data files in a hierarchical manner. Documents are hierarchically managed using this directory. At this time, when the document is composed of a plurality of data files such as a text data file and a format data file, the technique for associating the document with the data file is:
Storing multiple data files in the directory by correlating the file name format (the document name is the data file base name and the extension is assigned to each data file type) and the directory name to the document name The technique of letting is used.

As a technique for associating a document with an application program, for example, the above-mentioned Microsoft Windows has a file manager which is a program for managing a file system and uses an extension part of the name of a data file. , It has a function of associating with an application program, and when you instruct the data file to start the application program, it becomes possible to search for the corresponding application program from the extension of the data file and start the data file as data. ing.

As another technique, Macintosh (trade name: Apple Computer, USA) uses a technique of storing application program information in each data file.

Further, as a technique for classifying and browsing documents, there is a technique for classifying documents by directories using a hierarchical file system. For example, by giving the directory a name corresponding to the classification and hierarchically configuring the directory and data files in a tree structure, the user can freely construct the classification system and determine the type of document that exists. By following it, you can browse. At this time, as a technique for classifying one document from directories of different hierarchies, the above-mentioned Macintosh uses a function called an alias of a file to change a special control file that refers to another data file. There is a technique for creating multiple classifications by putting them in a directory of different levels.

[0007]

In the prior art, the OS
Since the document is managed by using the file system described above, there are cases where the document cannot be managed sufficiently due to the restrictions of the OS.

First, when a document is composed of a plurality of data files, it is necessary for the user to manage the correspondence between the document and the data file group by himself / herself using the file name. In some cases, for example, when a user wants to copy, he / she may forget to copy a part of the data file. In addition, data file names are used to associate with application programs, and information is stored in each data file, so when you want to change the corresponding application program,
I had to change the data file name and recreate the data file.

Secondly, since the documents are classified by using the hierarchical directory of the file system, there are cases where the name of the document is restricted by the file system and the performance is deteriorated when the classification hierarchy becomes deep. Also, if you want to have special information in the classification, for example, if you want to create the classification by the creator of the document, it is necessary to make the creator name correspond to the directory, and other information such as the address of the creator is newly added. I had to create and store a data file separate from the directory control file.

Third, since the hierarchy of document classification is created by the system of the directory hierarchy of the file system, it is possible to browse the documents by tracing each classification.
No consideration was given to browsing by combining multiple categories.

The present invention has been made in view of the above circumstances, and a first object of the present invention is to provide a document management method for facilitating correspondence between a document and a data file and an application program. That is.

[0012] A second object is to provide a document management method in which the classification of documents is not restricted by the restrictions of the file system.

A third object is to provide a document management method that facilitates browsing of documents by combining a plurality of classifications.

[0014]

The first purpose is to provide an information node corresponding to the type of a document in order to manage the document so that the document belongs to the information node corresponding to the type. The information node also stores information about the structure of the data file of the document to which it belongs and information about the corresponding application program. With regard to documents, by providing document information that is data that stores the data file names that make up the documents and the location of the documents, these document information are linked from information nodes that represent the type of document. To be achieved.

The second purpose is to hierarchically configure the information nodes regardless of the directory hierarchy, and to store a set of lower information nodes and a set of document information in each information node. This is achieved by allowing the user to store arbitrary information in the information node.

The third object is achieved by providing a plurality of information node hierarchies and performing a logical product or logical sum operation on a set of document information belonging to the information node when browsing a document.

[0017]

In a document, the information node to which the document belongs stores information about the configuration of the document and the application program. Therefore, by referring to the information node to which the document belongs, batch processing of a plurality of data files and processing of the application program can be performed. Collaboration is possible. Further, even if the structure of the data file or the application program is changed, the corresponding information of one information node may be changed, and it is not necessary to change each document.

Since the information node stores information about a set of subordinate information nodes and a set of documents, the classification can be configured regardless of the limitation of the hierarchical directory. Further, since the user can set arbitrary information in the information node, related information can be stored separately from the classification name.

Since it is possible to manage a document in a plurality of classifications by using a hierarchy of a plurality of information nodes, a document belonging to an information node of a certain classification is recursively included in a document included in a lower information node. Create a set of documents in, and the created set of documents with the set of documents created by other classification,
By creating a new document set by performing a logical sum or logical product operation, it is possible to browse a document in which a plurality of classifications are freely combined.

[0020]

EXAMPLE FIG. 1 shows the basic configuration of this example.

An input / output device with a user is composed of a pointing device 101 such as a mouse, a display device 102, and a keyboard 103, and accesses a main storage device 105 through a CPU 104. The main storage device 105 has a document management program 106. The document management program 106 has a data display unit 107 for displaying data, a data control unit 108 for controlling data according to a request from a user,
A document information management unit 109 that manages documents, an information node management unit 110 that controls information nodes, and a data operation management table 111 that edits documents are included. Further, the database 112 includes a document information storage unit 113 for storing documents,
It has an information node storage unit 114 that stores information nodes.

FIG. 2 shows the relationship between the information node of the information node storage unit 114 and the document of the document information storage unit 113 in this embodiment. The information node has three types of views: company 201, product 202, and document class 203. IDs for identifying information nodes and documents
Is attached.

The view of the company 201 has a lower node, A company 2
11, B company 212, C company 213. The lower node of the company B 212 has a B1 section 221 and a B2 section 222. The subordinate node of the B1 section 221 has a first G 231, a second G 232 and a document 5 (245). This document 5 (245) is B1
It is directly related to the section 221. Document 1 (241), document 2 (242), document 4 (24
4) is related. Further, the document 2 (242) and the document 3 (243) are associated with the second G232.

The view of the product 202 is the OS2 on the lower node.
14 and AP215. AP215 is product X223,
The node of the product Y224 and the document 4 (244) are associated with each other. Document X (242) and Document 5 for product X223
(245), the document Y (243) is associated with the product Y.

The view of the document class 203 is the specification 251.
And holds minutes 252. Specification 251 is document 1 (24
1), document 2 (242), and document 3 (243) are associated with each other. Minutes 252 is Document 4 (244), Document 5
(245) is associated.

By using the information node in this way, one document (for example, document 3 (243)) can be classified into a plurality of categories (company B, company B) regardless of the structure of the OS file system.
It can be managed by Section 1 2G, AP product Y).

FIG. 3 shows the structure of an information node used when classifying documents. The information node can be created when the user wants to arbitrarily classify the document other than the document class, and can be linked to the document. Further, it is possible to browse the document based on the created information node. The information node 300 is created by the user and shows an example of the B1 section 221 in FIG. The information node 300 includes data such as ID, node creator, and node creation date. The node link 301 stores the number of nodes linked to the lower order and its ID. The document link 302 stores the number of documents associated with the node and its ID. User attribute information 30
3 is arbitrary information given by the user, and for example, information such as an address can be stored in the node (company organization).

FIG. 4 shows the structure of document information for managing documents. This document information shows an example of the document 1 (241). The affiliation information node ID 405 stores the node of the document class to which it belongs. Document 1 (241) is associated with the specification 251 and therefore the ID of the specification 251.
1001 is stored. The document information 400 is I
D, document name, document owner, update date, document size, document storage location, number of constituent files, etc. are stored. When the information location type 403 is directly accessible 404, the file name 410 used by a plurality of computers is stored, the belonging information node ID 405 is traced, the AP of the document class to which this document belongs is acquired, and the AP is activated. It is possible. When direct access is not possible, there is an effect that, for example, information indicating the position of a document shelf in which a document is stored is stored, and it is possible to manage a document that has not been digitized in the computer. The user information link 411 is
This is the same as the user information link 303 in FIG.

FIG. 6 shows the structure of a document class information node. In this example, the document class is the specification 251. Each document belongs to a document class information node indicating the type of document. The document class information node 600 has an attribute including an attribute name 601 and an attribute value 630. The attribute 601 of the information node includes an ID 602, a node name 603,
It has a node creator 604, a node creation date 605, a node link 606, a document link 607, a user attribute number 608, a user attribute link 609, an AP name 610, a file configuration number 611, and a file link 612. The node link 606 has information 640 of lower information nodes linked to the information nodes. In the specification 251, the number of link destination nodes is 0 because there are no lower nodes. The document link 607 has information 641 of the document to which the information node is linked.

The AP name 610 stores the AP name used when updating the document. Here, it is shown that an AP named "Word Processor A" is used. The user attribute link 609 is the same as 303 in FIG. 3 and is arbitrarily set by the user. In the file link 612, the file type 643 of the document to which the document belonging as an attribute is composed
Have. As described above, since the information node 600 has the AP name, it has the information of the AP that created the document. Therefore, when it is desired to edit the document belonging to the information node, the application can be activated, and there is an effect that it is not necessary to be aware of the application of the document registered at the time of updating. Further, the AP name may be changed by changing this information. Further, since the structure of the file related to the AP can be retained, the files can be collectively copied when copying the document.

Hereinafter, embodiments of the condition retrieval type (FIGS. 7 to 19) and the narrowing retrieval type (FIGS. 20 to 28) browsing will be described with reference to screen diagrams and PADs. First, the conditional search type browsing will be described.

FIG. 7 shows a condition search type initial screen. Figure 2
The condition retrieval type browsing program 2900 of No. 1 is executed, and it is in the state of waiting for the user's input (step 2901). Select view 700 (step 2902) and select "Company" from the pull-down menu. Then Fig. 8
As shown in, the view 700 shows "Company",
The hierarchy 1001 of the relevant information node is displayed (step 2910). At this time, the current top node ID 502 of FIG.
The ID = 1 of the company 201 is stored in. Next is node hierarchy 1
When the first G1002 is selected from 001 (step 2093), the current node operation ID 501 is incremented, and the current top node ID (ID = 1) and the selected node ID (ID = in the operation table 504 of the current node operation ID).
20) is stored (step 2912). Also, when another information node is subsequently selected, the current node operation ID 501 is similarly incremented, and the current top node ID and the selected node ID are stored in the operation table 504 of the current node operation ID (step 2912). Next, "Open Document List" is selected from the pull-down menu (not shown) of the file (F) in FIG. 8 (step 2).
905). Then, the conditional search display program is executed (step 2914), and as a result of the processing of the conditional search display program shown below, the document 1 (1203) and the document 2 (120) are displayed in the document list 1202 as shown in FIG.
4) and document 4 (1205) are displayed.

The condition retrieval type display program 2914 shown in FIG. 22 executes the document acquisition processing for the number of storages 3001 stored in the node operation table 504 to acquire the document linked to the node ID (step 300
2) If there is a lower node in the node ID (step 3003), the documents linked to all the lower nodes are acquired (step 3004). The obtained documents are logically merged to create a document list 505 and stored in the node operation table 504 (step 300).
5). When the user selects a plurality of information nodes, a plurality of node IDs are stored in the node operation table 504, so the document acquisition process is executed for all the nodes stored in the node operation table 504. To do. After this processing is completed, a logical operation specified by the user is performed for each top node ID to create one document list, which is executed when the user has selected a plurality of views.

In other words, the set management table 50 is repeated by repeating the number of stored node operation tables (step 3006).
6 top node ID (step 3008),
If the same top node exists, the document list 505 of the node operation table 504 and the set management table 50
The document list 507 of No. 6 is subjected to a user-specified logical sum operation or logical product operation stored in the document logical operation mode 503, the documents are merged, and the document list 507 is updated (step 3010). The same top node I
If there is no D, the top node ID of the node operation table 504 and the document list 505 are stored in the set management table 506.
(Step 3009). As described above, when the logical operation for each top node ID is completed, it is repeated for the number of storages in the set management table (step 3011), and the document list of each top node ID is ANDed (step 3
012) and display it in the document list 1201 (step 30)
13).

In the above example, the node operation table 504
The number stored in is 1 and the document to which the node ID = 20 is linked is acquired (step 3002). That is, the document 1 (241), the document 2 (242), and the document 4 (244) are acquired. Next, it is judged whether or not this node ID has a lower node (step 3003). Since there is no lower node,
The acquired document is stored in the document set merge of the node operation table 504 (step 3005). Next, since nothing is stored in the set management table 506, the top node ID of the node operation table 504 and the top node ID of the set management table 506 are not equal (step 3008), and the set management table 506 has a node operation table. The top node ID = 1 of 504 and the document list of the node ID = 20 in the document set merge are stored. Therefore, the number stored in the set management table 506 is one. Next, the logical product merge of the document lists of the respective top node IDs is executed, but since there is only one document, the documents included in this document list are displayed in the document list (steps 3013 and 310).
1).

Next, as shown in FIG. 10, the node hierarchy 100
Select 1G1002 and 2G1003 from 1,
When the logical product 1004 is selected as the logical operation mode, the above-described conditional search type browsing program 2900 and the conditional search type display program 2914 are executed, and a resulting document list is created. Here, in order to select the information node in the same view, the document list of the first G1002 and the document list of the second G1003 are logically ANDed, and as a result, as shown in FIG.
402) is displayed. When the logical sum is designated as the logical operation mode, the document list list 1 as shown in FIG.
In 501, a document 1 (1502), a document 2 (1503), a document 3 (1504), and a document 4 (1505) are displayed.

In this example, the node operation table 504 stores information on two nodes. The stored information is that the top node ID = 1 and the node ID = 2.
The node ID = 21 for 0 and the top node ID = 1. The document acquisition for each node is the same as the above example, and the former document list includes document 1 (241) and document 2
(242) and document 4 (244) are included, and the latter document list includes document 2 (242) and document 3 (243). The created document list is stored in the document set merge. Next, the node management table 504 is repeated by the number stored, and in the first iteration processing, the set management table 506 is executed.
Since there is nothing in, the top node ID equal to the first top node ID = 1 in the node operation table 504.
(Step 3008), the same as the previous example,
The set management table 506 stores a document list for the top node ID = 1 and the node ID = 20 (step 3009). In the second iteration processing, the top node ID = 1 in the node operation table 504 and the top node ID = 1 in the set management table 506 are equal (step 3008), and the document list and the node ID = 21 in the node operation table 504 are collected. The document list of the management table 506 is operated by a user-specified logical product, and the resulting document list is the document list of the top node ID = 1 of the set management table 506.

The document list here is Document 2 (242).
Is included, and the number of storages in the set management table 506 is 1. Next, the number of documents stored in the set management table 506 is repeated (step 3011), but since there is only one, the document (document 2 (242)) included in the document list of the top node ID = 1 in the set management table 506 is deleted. It is displayed in the document list (step 3013). If the user designation is a logical sum, Document 1 (241), Document 2 (242),
Document 3 (243) and document 4 (244) are displayed (step 3013).

FIG. 13 shows the second G1 from the view companies.
It is a figure when changing a view after selecting 003, and is a state where the view 700 is changed to a product using the pull-down menu and the node hierarchy 1005 is displayed.
Here, when the product X1006 is selected from the node hierarchy and the document list is opened, as a result, the document 2 (1902) is displayed in the document list list 1901 by the above-mentioned program as shown in FIG.

That is, here, the second G1003 document list for the view company is created, then the product X1006 document list for the view product is created, and both document lists are subjected to the logical product operation in the set management table 506. And the results are displayed. The values in FIG. 5 show the values when this example is executed. In this example, first, the second G232 of the view company 201 is selected, but the same operation as in the above example is performed and the node operation table 50 is selected.
The top node ID = 1 and the node ID = 21 are stored in No. 4 (step 2912). Next view product 20
Since the second product X223 is selected, the top node ID = 2 and the node ID = 12 are stored in the second node operation table 504 (step 2912). Next, a document is acquired for each of these two node IDs (step 3002), a document list is created, and linked to each document set merge (step 3005).

In other words, the document list here includes the document 2 (242) and the document 3 (243) in the former, and the document 2 (242) and the document 5 (245) in the latter. Next, the set management table 506 is created from the node operation table 504, but the top node I of the node operation table 504 is
Since D is not equal to the top node ID of the set management table 506, the set management table 506 includes a document list of top node ID = 1 and node ID = 21 and a document list of top node ID = 2 and node ID = 12. Stored (steps 3006, 3007, 300
8, 3010). Next, the number of storages in the set management table 506 is repeated (step 3011), and each top node ID
AND the document list linked to (step 30
12), documents included in the resulting document list (document 2 (2
42)) is displayed in the document list (step 3013).
That is, in the example here, there is an effect that the documents can be narrowed down by a simple browsing operation of displaying a document list by designating a plurality of nodes.

Next, the narrowing search type will be described with reference to FIGS. 15 to 20 and FIGS.

FIG. 15 is an initial screen of the narrowing-down search, in which the view list 2000 is displayed in advance, the narrowing-down search-type browsing program 3200 is executed, and the user is waiting for input (step 3201 in FIG. 24). . When the company 2101 is selected from the view list in FIG. 16 (step 3202), information nodes are displayed in the node list list 2201. The information node is displayed by deleting the displayed information node if the information node is already displayed (step 3210) (step 3211) and displaying the information node for the view (if the document list has already been created). (Add sign)
(Step 3212). At this time, the current top node I
The view node ID ID = 1 is stored in D502 (step 3213). Next, when the first G 2202 of the information node is selected from the node list 2201 (step 320
3) The current node operation ID 501 is incremented, and the current top node ID (ID = 1) and the selected node ID (ID = 20) are added to the operation table 504 of the current node operation ID.
Is stored (step 2912), and 1G is displayed in the history column 2203 (step 3215).

If another information node is subsequently selected, the current node operation ID 501 is similarly incremented, and the current top node ID and the selected node ID are stored in the operation table 504 of the current node operation ID. (Step 2912), the selected information node is displayed in the history column 2203 (step 3215). Next, "Open 2602" is selected from "File 2601" in the menu of FIG. If "Open 2602" is selected (step 320)
5), the narrow-down search type display program 3217 is executed, and as a result of the processing of the narrow-down type display program shown below, the document list 2401 includes document 1 (2402), document 2 (2402), document 4 ( 240
4) is displayed.

The narrowed search type display program 3217 shown in FIG. 25 executes the document acquisition processing of the storage number 3301 stored in the node operation table 504. Due to the narrowed-down search, the logical product operation of the document list is executed each time it is repeated.

That is, the first time (step 3302), the document acquisition program is executed (step 3305) to acquire the document linked to the node ID (step 340).
1) If there is a lower node in the node ID (step 3402), the documents linked to all the lower nodes are acquired (step 3403). The obtained documents are logically merged to create a document list 505 and stored in the node operation table 504 (step 340).
4). When the user selects a plurality of information nodes, the second and subsequent iterations are executed, and when the second and subsequent iterations are performed (step 3303), the document acquisition program 3305 is executed.
And the document list 505 created in the previous iterative process are logically merged to obtain the document list 5.
05 is created and stored in the node operation table 504 (step 3306).

In the final iteration (step 330
4) The operation is executed with reference to the designation of the logical operation mode for the last selected information node. The document logical operation mode 503 includes DEEP and SHALOW.
EP3308 is for acquiring the document linked to the node of the selected information and the document linked to all the lower nodes of the information node, and here, it is the same as executing the document program 3305. SHALLOW3
307 acquires 3309 only the document linked to the selected information node. This DEEP or SHALL
The final document list 505 is obtained by logically merging the document list obtained by OW and the document list 505 obtained by the previous iteration.
Is created and stored in the node operation table 504 (step 3310). When the final document list 505 is created, the documents included in the document list are displayed on the document list screen 2400.
(Step 3013).

In the above example, the node operation table 504
The top node ID = 1 and the node ID = 20 are stored in, and one piece of information is stored in the node operation table 504. Although there is only one in the table, the final loop is executed (step 3304) and the document acquisition program 3305 (D if there is no designation of the document logical operation mode)
Since EEP is given by default, the processing for DEEP) is executed (step 3308), and node ID = 2.
Get the document linked to 0 (step 340
1) Since there is no subordinate node (step 3402), the acquired documents (document 1 (241), document 2 (242), document 4 (244)) are made into a document list and stored in the document set merge (step 3404). . Next, document 1 (241), document 2 (242), document 4 included in this document list
Display (244) on the document list screen (step 301).
3).

Next, after selecting the first G from the companies in the view (“1G” is displayed in the history column of FIG. 18), when the product 2503 is selected from the view list 2000, the product 2503 The information node is the node list 220
It is displayed in 1. The AP 2505 is selected from this information node, and the AP is displayed in the history column 2203. Next, when the logical operation mode is switched to SHALLOW 2603 and “Open 2602” in the “File 2601” menu is selected, the above-described narrow-down search type browsing program 32 is displayed.
00 and the narrowing-down search display program 3217 display the document 4 (2702) in the document list 2701 as a result as shown in FIG. When the logical operation mode is DEEP, document 2 (2802) and document 4 (2803) are displayed in the document list list 2801 as shown in FIG. In this example, the node operation table 50
4, the top node ID = 1, the node ID = 20, the top node ID = 2, and the node ID = 9 are stored, and two pieces of information are stored in the node operation table (504).

Next, the first loop is executed (step 3302), the document acquisition program 3305 is executed,
Document 1 (241) and Document 2 (24 with node ID = 20
2), the document list including the document 4 (244) is stored in the document set merge. Subsequently, the last loop is executed (step 3304), and the document logical operation mode 503 is user specified SHALOW (step 330).
7), document 4 (2 directly linked to node ID = 9
44) and obtain a document list (step 3
309), a logical product merge is performed with the document list created in the previous loop to create a document list, and this document list is stored in the document set merge with node ID = 9 (step 33).
10). Documents included in this document list (Document 4 (24
4)) is displayed on the document list screen (step 301).
3).

When the user designation is DEEP (step 3308), the document acquisition program 3305 causes the document 4 (244) linked to the node ID = 9.
(Step 3401) and the documents (document 2 (242), document 5 (245)) linked to all the lower nodes of the node ID are acquired (steps 3402 and 340).
3) Then, the obtained documents are logically merged to create a document list (step 3404). Therefore, in this document list, document 2 (242), document 4 (244), document 5 (2
45) are included. This document list and the document list of the previous loop are logically merged, and the document list (document 2 (24
2), the document 4 (244 is included) is created and stored in the document set merge with the node ID = 9 (step 331).
0). Documents included in this document list (Document 2 (24
2), the document 4 (244) is displayed on the document list screen (step 3013).

In other words, here, there is a SHALLOW designation for acquiring only the document linked to the information node, and it is not necessary to obtain the document set related to the lower information node, so that there is an effect that a document set with improved performance can be created. Further, there is an effect that a detailed search can be performed by obtaining a document linked to an information node and a document linked to a lower node. In addition, when the nodes are narrowed down, the nodes that have already been narrowed down and have no relation to each other are displayed with a code added, which is effective in preventing unnecessary operations by the user.

The display of the above-mentioned document list is a process common to the condition search type and the narrowed search type, and is represented by the "document list / document list screen display program 3013" shown in FIG. With respect to the final document list, this program displays the documents included in the document list on the document list (step 3101). In addition, from the menu of the document list or the document list screen, "AP start 1903, 2
804 ”is selected (step 3102), the belonging document node ID 4 is determined based on the file 410 for the selected document.
By tracing 05, the AP with the AP name 210 can be taken out and activated (step 3105). When "Search 1904, 2805" is selected from the menu (step 3103), attribute search or full-text search can be performed on the documents displayed in the document list (step 3106). When "close" is selected from "file" in the menu (step 3104), this screen is closed (step 3107).

Both the condition search type and the narrowed search type can be registered on the browser screen, and the document can be registered by selecting "document registration (S)" in "file 2601" (step 2906, 3206), Document I
When D is entered (steps 2915 and 3218), the document IDs entered for all the nodes in the operation table
To link. That is, it is possible to register a document in a necessary place all at once by one operation, and it is not necessary to search for and store a storage location one by one, which has an effect of reducing a user operation.

Further, when browsing and acquiring a document, each document has an access right, and there is a function that can be displayed only to a user who is permitted the access right. That is, each information node has a node creator for the node name as shown in FIGS. 2 and 6, and has document links 241 and 301 for the document to which the access right is permitted. You can't see documents that aren't in the document links here. That is, there is an effect that the disclosure and update of the document can be limited to only the necessary users. Further, even when a condition search is desired, a document set to be searched can be created by the processing of the present embodiment, so that there is an effect that the search performance can be improved by narrowing down the conditions in advance.

[0056]

According to the present invention, a user can manage a document from a free classification viewpoint (view) that exceeds the functions of directories and folders provided by the OS. Since information nodes can be created according to the type of document, it is easy to associate multiple files and applications with the document. By creating multiple views and selecting the information nodes that make up the view, the user can quickly find the document he or she needs. Even in the system, it is possible to extract the document according to the user's needs by managing the association between the information node and the document without managing the directory and the folder. Further, the user can easily narrow down the documents by selecting the information node based on the node hierarchy of the information nodes displayed on the screen. In addition to selecting information nodes and narrowing down documents, extraction of only documents that are directly linked to information nodes, or extraction of all documents of subordinate information nodes in addition to documents that are directly linked, etc. You can select operations that improve the document extraction performance or operations that reduce the number of operations. When an information node that spans views is selected, logical operations are performed in the system, so that user operation can be simplified and documents can be automatically narrowed down.

[Brief description of drawings]

FIG. 1 is a diagram of a basic configuration in an embodiment of the present invention.

FIG. 2 is a diagram showing a relationship among views, information nodes, and documents used in an embodiment of the present invention.

FIG. 3 is a diagram showing a table configuration for managing attribute data of information nodes.

FIG. 4 is a diagram showing a table configuration for managing document information data.

FIG. 5 is a diagram showing a work table used in the system when narrowing down documents.

FIG. 6 is a diagram showing a table configuration for managing attribute data of a document class information node.

FIG. 7 is a diagram showing a conditional search type initial screen.

FIG. 8 is a diagram in which a conditional search type information node is selected.

FIG. 9 is a diagram showing a list of documents for an information node selected by a conditional search type.

FIG. 10 is a diagram in which a plurality of condition search type information nodes are selected.

FIG. 11 is a diagram showing a document list when a logical product is designated for a plurality of information nodes of conditional search type.

FIG. 12 is a diagram showing a document list when a logical sum is designated for a plurality of information nodes of conditional search type.

FIG. 13 is a diagram of selecting an information node for a changed view of the conditional search type.

FIG. 14 is a diagram showing a document list when an information node is selected for a plurality of conditional search views.

FIG. 15 is a diagram in which a view list is displayed on a narrow-down search initial screen.

FIG. 16 is a diagram in which a narrow-down search type information node is selected.

FIG. 17 is a diagram showing a document list for a selected information node of a narrowed search type.

FIG. 18 is a diagram showing an operation of opening a document list by designating SHALOW as a logical operation mode by selecting an information node for a plurality of views of a narrowed search type.

FIG. 19 is a diagram showing a document list when a plurality of narrow search type views are designated.

FIG. 20 is a diagram showing a document list when DEEP is designated as a logical operation mode for an information node of a narrowed search type and a plurality of views is designated;

FIG. 21 is a diagram showing a condition retrieval type browsing program.

FIG. 22 is a diagram showing a condition retrieval type display program.

FIG. 23 is a diagram showing a program for displaying a document list of condition search type and narrowed search type.

FIG. 24 is a diagram showing a refined search type browsing program.

FIG. 25 is a diagram showing a narrow-down search type display program.

FIG. 26 is a diagram showing a narrow-down search type document acquisition program.

[Explanation of symbols]

109 document information management unit 110 that manages information of documents 110 information node management unit that manages information nodes and has a relationship with documents 111 data operation management table 112 used when narrowing down documents 113 database having document information and information nodes 113 documents Document information storage unit 114 for storing information Information node storage unit 200 for storing information of information node Table 300 for holding data of information node of document class 300 Table for holding data of information node 400 Table for holding data of document information 2900 Conditional Search Browsing Algorithm Shown Conditional Search Browsing Program 2914 Conditional Search Browsing Program 3013 Showing Conditional Search Browsing Document Acquisition Algorithm 3013 Conditional Search Browsing Program Displaying Documents Resulting by Conditional Browsing RAM 3200 Refined search type browsing algorithm Shown refined search type browsing program 3217 Refined search type browsing document acquisition algorithm Shown with refined search type display program 3305 Refined search type browsing information Document acquisition program

─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Satoshi Wakayama 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Stock company Hitachi Software Development Division (72) Inventor Yoshiki Matsuda 1099, Ozen-ji, Aso-ku, Kawasaki-shi, Kanagawa Ceremony Company Hitachi, Ltd. System Development Laboratory (72) Inventor Tetsuya Hashimoto 1099 Ozenji, Aso-ku, Kawasaki City, Kanagawa Prefecture Stock Company Hitachi Systems Development Laboratory (72) Inventor Keiji Kojima 1099 Ozenji, Aso-ku, Kawasaki City, Kanagawa Prefecture Address Company Hitachi, Ltd. System Development Laboratory (72) Inventor Takayoshi Yamamoto 3-529 Kitahama, Chuo-ku, Osaka City, Osaka Prefecture Hitachi Hitachi Software Co., Ltd. (56) Reference JP-A-5-128157 ( JP, A) UNIX System V User Reference Machine Yuaru second Banri lease 3.0, Japan, AT & T UNI X software operation Pasi fit, October 15, 1985, p. 181-185 (58) Fields investigated (Int.Cl. ⁷ , DB name) G06F 17/30 G06F 12/00 JISST file (JOIS)

Claims (2)

(57) [Claims] 1. Each of a plurality of top nodes is a vertex
Corresponds with each node that belongs to the node set that constitutes the hierarchy
Information of documents directly related to the node and the node
The first table that stores the information of the lower nodes of
About the target node of the book search process and the node
The first to store the retrieved document list in association with each other
A document management system having a storage unit for holding a second table
In the document management method in the system, when the designation of the first top node is accepted,
Belongs to the first node set with one top node as the vertex
Of the displayed nodes, and among the displayed nodes,
Stored in the second table in association with the second node
Add a code to the node that is not related to the document list
And, receiving the designation of the first node belonging to the first set of nodes
And the second node stored in the second table
Associated with the second node and the document directly related to
With documents directly related to each of the subnodes
The first document list consisting of Riwa is extracted, and the documents directly related to the first node and the first node are extracted.
Directly to each of the subordinate nodes associated with the
Extracts the second document list that is the logical sum of consecutive documents
The extracted first document list and the second document list
To display the document list obtained as the logical product of
Characteristic document management method. 2. Each of a plurality of top nodes is a vertex
Corresponds with each node that belongs to the node set that constitutes the hierarchy
Information of documents directly related to the node and the node
The first table that stores the information of the lower nodes of
About the target node of the book search process and the node
The first to store the retrieved document list in association with each other
A document management system having a storage unit for holding a second table
In the document management method in the system, when the designation of the first top node is accepted,
Belongs to the first node set with one top node as the vertex
Of the displayed nodes, and among the displayed nodes,
Stored in the second table in association with the second node
Add a code to the node that is not related to the document list
And, it specifies a sentence of the first node belonging to the first set of nodes
The second node stored in the second table, accepting the selection of the operation mode that defines the search range of the book
Associated with the second node and the document directly related to
With documents directly related to each of the subnodes
The calculation mode in which the first document list consisting of Riwa is extracted and the selection is accepted is the first mode.
In this case, only documents directly related to the first node are extracted.
The logical product of the extracted and extracted relevant document and the first document list
The second document list obtained by displaying the selected document is displayed, and the operation mode in which the selection is accepted is the second mode.
If the document directly related to the first node and the
Each of the subordinate nodes associated with the first node
A third document list consisting of the logical sum of the documents directly related to each
List of extracted documents , and the extracted first document list and the third document list
Display the fourth document list obtained as the logical product of
A document management method characterized by the above.