JPH10116216A - Data management system and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a data management system, which stores and manages various data such as document data are spread sheet data that a user has generated in a data server, to easily perform retrieval, etc., at a high speed while providing understandability that hierarchical directory constitution has for the user. SOLUTION: The user specifies the storage location of data to be registered in the data server through the hierarchical directry constitution represented as hierarchical structure deeper than the directry structure wherein the data are actually stored by the data server. The data server records the name of a relatively lower directry (drawer) in a hierarchical directry structure used when the storage location is specified as an identification mark 62 in the record 36 corresponding to the data to be registered.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data management system capable of storing various data such as document data and spreadsheet data and searching for corresponding data based on input search conditions. The present invention relates to a data management system and a recording medium for making the user aware of file management in a hierarchical directory structure.

[0002]

2. Description of the Related Art As various types of data, such as document data by word processor software and calculation data by spreadsheet software, are accumulated, these data can be efficiently managed and shared by a plurality of users. The need increases. To respond to such requests,
2. Description of the Related Art Data created by a plurality of users is stored in a common data server, and data is centrally managed and shared in the data server. In general, the data server and the client terminal of each user are connected via a LAN (local area network), and further, a remote data server and the client terminal of the user are connected via the Internet. Are also increasing.

When storing various data created by a user in a data server, most of recent operating systems perform file management in a hierarchical directory structure in which subdirectories are arranged in a tree structure under a root directory. Therefore, in general, each of these data is set as a file, and these files are classified according to departments, contents, and the like, and are arranged in subdirectories in a hierarchical directory configuration. When the number of files such as document data and spreadsheet data is large, a multi-level sub-directory structure is adopted. By arranging each file in the tree-like hierarchical directory structure, the user can easily access a desired file from among a large number of files.

FIG. 8A is a diagram showing an example in which each of document data and spreadsheet data is stored as a file in a file system having a hierarchical directory structure of a data server. Root directory 9
Below 0, for example, a document directory for each user is arranged as a sub-directory 91 of the first layer. Here, in order to clearly show the directory structure to the user, a document directory (subdirectory 91) for each user is set as a home directory or a working directory of the user, and each of the documents is arranged under the subdirectory. The subdirectories of the columns are called cabinets 92, drawers 93, and the like, respectively.

In the illustrated example, a cabinet 92 is provided with a detailed specification cabinet, a basic specification cabinet, an operation manual cabinet, and an internal specification cabinet. The basic specification cabinet is provided with a design-related drawer, a development-related drawer, and a business-related drawer as a drawer 93. Each of the drawers 93 stores a file 94 such as document data or spreadsheet data. . The user can understand which data should be stored in which drawer of which cabinet by referring to the cabinet name and the drawer name. For example, a file corresponding to the development-related document data A in the basic specification is represented as “(home directory) / basic specification / development-related / A” as a path name. In this example, the drawer 93 is the lowest layer. However, a folder may be further provided as a subdirectory under the drawer 93, and the file 94 may be stored in the folder.

FIG. 8 (b) is a diagram schematically showing how the file arrangement based on the hierarchical directory structure shown in FIG. The drawing shows what kind of drawers 93 are provided in the basic specification cabinet, and how each drawer 93 stores a file 94 such as document data. At the head of each file 94, a title and a creation date (not shown) of the file 94 are recorded as a header.

By arranging the data files 94 in the data server according to the hierarchical directory structure as described above, it becomes easy to handle as a file system. By defining the organization of each subdirectory according to the classification intended by the user, the user can
A desired file can be easily accessed from a large number of files.

[0008]

However, when files are arranged in a hierarchical directory structure, if the sub-directory is deep, the operation for reaching the sub-directory storing the desired file becomes complicated. In particular, when searching for a file from a viewpoint different from the one assumed when defining the subdirectory organization, for example, when performing a keyword search, it is necessary to search the file in all subdirectories after all, and The operation of the directory (cd; change directory) or the like is required many times, and it takes time to execute the search program, and the search program itself becomes complicated.

[0009] It is an object of the present invention to provide the user with the intelligibility of the hierarchical directory structure,
An object of the present invention is to provide a data management system capable of performing a search and the like quickly and easily and a recording medium for the data management system.

[0010]

According to a data management system of the present invention, when data is stored in a data management system for storing and managing data in a data server, the data is actually stored in the data server. The storage location of the data in the data server is specified by a hierarchical directory structure represented by a hierarchical structure deeper than the directory structure.

[0011] The recording medium of the present invention is a recording medium storing a program for realizing a data management system for storing and managing data in a data server. Is a recording medium that records a program for realizing a function of designating a storage location of the data in the data server by a hierarchical directory structure represented by a hierarchical structure deeper than a directory structure in which is stored.

[0012]

Next, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a data management system according to an embodiment of the present invention.

This data management system is configured as a client / server system via a network. Specifically, a network in which a network in a head office and a network in another business office are connected via the Internet 20. belongs to. First, the network configuration of the head office department will be described. The first LAN 10, which is a network dedicated to the company, stores various data such as document data, spreadsheet data, and drawing data created by each user and manages them. A data server 11 for searching data corresponding to a search condition given by a user, a plurality of client terminals 13 provided for each user,
A browser 14, which is a dedicated terminal for browsing data, is connected. The data server 11 is connected to a data stocker 12 which is a huge external storage device for storing actual data. In addition, the head office department has a second LAN for connection to the Internet 20.
16 are provided, the first LAN 10 and the second LA
N16 is connected via a firewall 15. The second LAN 16 is connected to a WWW server 18 for providing a WWW (World Wide Web) service, and is also connected to the Internet 20 via a gateway 17. On the other hand, LAN2
The LAN 22 is connected to the Internet 20 via a gateway 21 and is connected to a plurality of client terminals 23 provided for each user.

In this client / server system, the user operates the client terminals 13 and 23
Create document data and spreadsheet data. At the time of creation, these data are stored in the user's client terminal 13,
23 are stored in the local disk. When the user wants to register and accumulate the created data in the data server 11, the user performs a data registration process and stores the corresponding data in the client terminal 13.
23 to the data server 11. As a result, information for search and data management is added, and the data is stored in the data stocker 12, and thereafter, is subjected to centralized management and search processing in the data server 11.

Here, registration processing by the user will be described.

FIG. 2A is a diagram showing a directory configuration (file system configuration) of the data server 11 as viewed from the user. From the user's point of view, the document directory 31 is viewed as a top-level directory by the hierarchical directory structure.
In the same manner as described above, the cabinet 32 and the drawer 33 appear as sub-directories of each stage, and the drawer 33 looks as if files 34 such as document data are arranged. Therefore, when registering data in the data server 11, the user performs a data registration process by specifying a cabinet name and a drawer name in which data to be registered is stored. In the client / server system of the present embodiment, a cabinet name and a drawer name can be specified by a graphical user interface (GUI). FIG. 2 (b) shows the client terminals 13, 23 when designating the cabinet name and the drawer name.
Screen (window) that appears on the screen
FIG.

The cabinet selection screen 40 is roughly divided into a registration candidate input window 41 for inputting a name of a file (on a local disk) to be registered in the data server 11, and a name and a host name of the data server 11. And a server display window 42 for inputting which data server to select when there are a plurality of data servers.
And a cabinet display window 43 for displaying the name of the cabinet in the data server 11 and selecting a cabinet for storing the data, and displaying the data of the drawer in the cabinet selected in the cabinet display window 43. And a drawer display window 44 for selecting a drawer as a storage destination of the storage device. Cabinet display window 43
In the drawer display window 44, a cabinet name and a drawer name can be respectively selected by selecting a specific one from the displayed ones with a pointing device such as a mouse.

A user inputs a file name of data to be registered in a registration candidate input window 41, selects a cabinet and a drawer respectively by a cabinet display window 43 and a drawer display window 44, and uses a mouse or the like to select a cabinet and a drawer at the lower left of the figure. Click the "Execute selection" button 45. "Selective execution"
When the button 45 is clicked, the file to be registered and the cabinet and drawer of the storage destination are determined. If the "cancel" button 46 in the lower right of the figure is clicked here, the input and selection up to that point are returned to blank, and the file name to be registered and the cabinet name and drawer name of the storage destination are specified again. It can be performed.

When the input of the file name and the selection of the cabinet and the drawer are completed as described above, the user inputs additional information for data management and search in the data server 11. FIG. 3 shows an example of an input screen (window) 50 displayed on the client terminals 13 and 23 for inputting such information. This input screen 50
Indicates the cabinet name and the drawer name specified previously, respectively, in the cabinet name display window 51 and the drawer name display window 52.
And an input window 53 for inputting items such as a management code, a registration date, a registration time, a creator, a registrant, a data category, a title, and a keyword for data to be registered. . Some of these input items (for example, creator, registrant, registration date, etc.) may be automatically input based on local management information in the client terminals 13, 23. The user inputs necessary items through the input window 53, and then performs a “register” button 54
Click. Thus, the registration processing is completed, and the specified file is transferred from the client terminals 13 and 23 to the data server 11 together with the cabinet name and the drawer name of the storage destination and the additional information. If the “cancel” button 55 is clicked here, the input screen 5
The input to 0 is canceled and the input can be redone.

Next, the files to be registered are transmitted from the client terminals 13 and 23 to the data server 1 as described above.
The operation on the data server 11 side when it is sent to the server 1 will be described. By the way, the data management system according to the present embodiment requires the data server 11 to be recognized by the user.
Is characterized in that the actual directory structure is not hierarchized. Hereinafter, the processing in the data server 11 will be described while exemplifying some actual directory configurations in the data server 11.

FIG. 4A is a diagram showing a first example of an actual directory structure in the data server 11. In this example, a detailed specification cabinet, a basic specification cabinet, an operation manual cabinet, and an internal specification cabinet are arranged as a cabinet 32 under a document directory 31 (a top-level directory visible to the user). 32, one file 35 is stored. That is, the drawer seen by the user does not actually exist. Cabinet 3
2 contains several records 36
, And each record corresponds to each one of the data from the user.

FIG. 4B is a diagram showing the structure of the record 36. The record 36 includes a title field 61 for recording a title, an identification mark 62, a date field 63 for recording a date, an additional information field 64 for recording additional information other than the title and date, and a data body section 65.
It is composed of The entity of the data main body 65 is the data (file) itself transferred from the user's client terminals 13 and 23. As the identification mark 62, a drawer name designated by the user (“design related” in the illustrated example) is recorded. FIG. 4C shows a data storage state in the cabinet 32, for example, as the cabinet 32.

Upon receiving the data to be registered from the client terminals 13 and 23, the data server 11 adds the data as a record 36 to the file 35 in the designated cabinet 32. At this time, various kinds of additional information are recorded in a title field 61, a date field 63, and an additional information field 64, and a drawer name designated by a user is recorded as an identification mark 62. By combining with the main body 65, the record 36 corresponding to one data (one file in the client terminals 13 and 23) is assembled. Here, it has been described that only the file 35 including the above-described record 36 exists in the cabinet 32,
Auxiliary files used at the time of search, for example, index files, may exist in the same cabinet.

Next, search processing in the data server 11 having such a directory structure will be described. Here, the term “search” refers to searching for data corresponding to a search condition from data previously stored by the user. Examples of the search condition include a keyword and a drawer name (the data should be stored when viewed from the user). When a keyword is given as a search condition, the data server 11 opens the file 35 and searches the additional information field 64 of each record 36 to find a record including the corresponding keyword. If there is an index file, the search may be performed using the index file.
On the other hand, when a drawer name is given as a search condition, a file in the drawer (subdirectory) of the drawer name has been searched conventionally, whereas in the present embodiment, a file in the subdirectory is There is no drawer, and the drawer name is replaced with the identification mark 62 for each record 3
6, the identification mark 6 of each record 36 of the file 35 as in the case of the search by the keyword.
Search for 2.

As a file operation viewed from the user, for example, copying specific data represented by a path name “/ directory name / drawer name / file name” from the data server 11 to the client terminals 13 and 23 is performed. However, since this is nothing but search processing in a broad sense, a record is found in the same procedure as the above-described search processing, and the data body of the record is stored in the client terminal 1.
3 and 23.

Here, since the drawer as a subdirectory is recognized by the user but does not actually exist,
The number of directory changes accompanying a search can be reduced while maintaining the clarity of the hierarchical directory structure, and the search can be speeded up and the search program can be simplified.
In addition, since the data created by the user is used as a record, and a plurality of records are bundled into one file, the number of file open times at the time of the search is reduced, so that the search can be performed at a higher speed. File management becomes easy.

FIG. 5A is a diagram showing a second example of the actual directory structure in the data server 11. In this example, a detailed specification cabinet, a basic specification cabinet, an operation manual cabinet, and an internal specification cabinet are arranged as cabinets 32 under the document directory 31, and each cabinet 32 has data created by a user. And one or a plurality of files 37 respectively corresponding to. Also in this example, the drawer that was visible to the user does not actually exist.

FIG. 5B shows the structure of the file 37. The file 37 includes a title field 71 for recording a title, an identification mark 72, a date field 73 for recording a date, an additional information field 74 for recording additional information other than a title and a date, and a data body section 75.
It is composed of The entity of the data body 75 is the data itself transferred from the client terminals 13 and 23 of the user. As the identification mark 72, a drawer name designated by the user (“design related” in the illustrated example) is recorded. FIG. 5C shows a data storage state in, for example, a basic specification cabinet as the cabinet 32, and shows that a plurality of files 37 are included in the cabinet 32.

In the second example, since each record in the first example is independent as a file, the number of files cannot be reduced.
Compared with the conventional one, the number of directory changes and the like can be reduced, and the search can be speeded up and the search program can be simplified.

FIG. 6A is a diagram showing a third example of the actual directory structure in the data server 11. In this example, as in the first example, a file 35a which is a set of several records 36a is provided. However, not only the drawer but also the cabinet which is a subdirectory under the document directory 31 is actually used. Does not exist.
That is, the file 35a is directly stored in the document directory 31. Each record corresponds to each one of the data from the user.

FIG. 6B shows the structure of the record 36a. The record 36a is, as in the case of the first example,
A title field 61 for recording a title, an identification mark 62 for recording a drawer name, a date field 63 for recording a date, an additional information field 64 for recording additional information other than a title and a date, and a data body section 65. In addition to this, an identification mark 66 for recording a cabinet name (“basic specification” in the illustrated example) designated by the user in response to the fact that no cabinet is actually provided. FIG. 6C shows a data storage state in the document directory 31.

In the third example, since the directory structure is completely flat (that is, not hierarchical) from the viewpoint of data access, directory changes do not occur in principle and the search can be speeded up. And further simplify the search program. Further, since the number of files to be searched is extremely reduced, file management becomes easy.

FIG. 7A is a diagram showing a fourth example of the actual directory structure in the data server 11. In this example, one or a plurality of files 37a respectively corresponding to the data created by the user are stored in the document directory 31. Also in this example, the cabinet and the drawer that were visible to the user do not actually exist.

FIG. 7B shows the structure of the file 37a. As in the second example, each file 37a includes a title field 71 for recording a title, an identification mark 72 for recording a drawer name, a date field 73 for recording a date, and additional information other than the title and date. Information field 74 for recording the
And an identification mark 76 for recording the cabinet name (“basic specification” in the illustrated example) designated by the user in response to the fact that the cabinet was not actually provided. I have. FIG. 7C shows a data storage state in the document directory 31, which indicates that the document directory 31 includes a plurality of files 37a.

In the fourth example, since each record in the third example is independent as a file, the number of files cannot be reduced.
Compared with the conventional example, the search can be speeded up and the search program can be simplified as in the above-described examples.

The program for executing the above-described operation is recorded in whole or in part or in a portable medium such as a floppy disk, a CD-ROM, or a storage device such as a hard disk. . The program is read by the computer, and all or part of the operation is executed.

[0037]

As described above, according to the present invention, when storing data, the data server stores the data in a hierarchical directory structure represented by a hierarchical structure deeper than the directory structure actually constructed in the data server. By specifying the storage location and recording information about the directory relatively lower in the directory path used to specify the storage location in the record or file corresponding to the data to be stored, This makes it possible to provide a user with the intelligibility of the hierarchical directory structure, and to perform a search and the like quickly and easily.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a data management system according to an embodiment of the present invention.

FIG. 2A is a diagram showing a directory structure recognized by a user, and FIG. 2B is a diagram showing an example of a screen displayed for designating a registration place at the time of data registration.

FIG. 3 is a diagram showing an example of a screen displayed for setting additional information and the like at the time of new registration.

4A is a diagram showing a first example of an actual directory configuration in a data server, FIG. 4B is a diagram showing a configuration example of a record, and FIG. 4C is a diagram showing a data configuration in a cabinet; It is a figure showing a storing situation.

5A is a diagram showing a second example of an actual directory configuration in the data server, FIG. 5B is a diagram showing an example of a file configuration, and FIG. It is a figure showing a storing situation.

6A is a diagram showing a third example of an actual directory configuration in the data server, FIG. 6B is a diagram showing an example of a record configuration, and FIG. 6C is a diagram showing data in the document directory. It is a figure showing the storage situation of.

7A is a diagram illustrating a fourth example of an actual directory configuration in the data server, FIG. 7B is a diagram illustrating an example of a file configuration, and FIG. 7C is a diagram illustrating data in a document directory. It is a figure showing the storage situation of.

FIG. 8A is a diagram illustrating an example of a conventional file arrangement based on a hierarchical directory structure, and FIG. 8B is a diagram illustrating how a file arrangement based on a hierarchical directory structure is recognized by a user. FIG.

[Explanation of symbols]

 10, 16, 22 LAN 11 Data server 12 Data stocker 13, 23 Client terminal 17, 21 Gateway 20 Internet 31 Document directory 32 Cabinet 33 Drawer 34, 35, 35a, 37, 37a File 36, 36a Record 62, 66, 72, 76 Identification mark 65,75 Data body

Claims (8)

[Claims] In a data management system for storing and managing data in a data server, when storing data, a hierarchy represented by a hierarchical structure deeper than a directory structure in which the data is actually stored in the data server. A data management system, wherein a storage location of the data in the data server is specified by a dynamic directory configuration. 2. A file including a record corresponding to the data is stored in the data server, and a relatively higher directory in the hierarchical directory structure used when specifying the storage location corresponds to the file. 2. The data management system according to claim 1, wherein information on a relatively lower directory is included in the record. 3. A file corresponding to the data is stored in the data server, and a directory corresponding to a relatively higher directory in a hierarchical directory structure used when designating the storage location is stored in the data server. The data management system according to claim 1, wherein information on a real and relatively lower directory is included in the file. 4. The data management system according to claim 2, wherein the relatively lower directory is a directory having two or more layers in a directory hierarchy. 5. The data management system according to claim 2, wherein the information about the relatively lower directory is a name of the relatively lower directory used when designating the storage location. 6. A storage medium storing a program for realizing a data management system for storing and managing data in a data server, wherein when the data is stored, the data is actually stored in the data server. A recording medium recording a program for realizing a function of designating a storage location of the data in the data server by a hierarchical directory structure represented by a hierarchical structure deeper than a directory structure. 7. The storage medium, wherein a function of storing a file including a record corresponding to the data in the data server, a relatively higher rank in a hierarchical directory structure used when designating the storage location 7. The recording medium according to claim 6, wherein a program for realizing: a function in which a directory corresponds to the file and information about a relatively lower directory is included in the record. 8. The recording medium, wherein: a function of storing a file corresponding to the data in the data server; and a function corresponding to a relatively higher directory in a hierarchical directory structure used when designating the storage location. 7. The recording medium according to claim 6, wherein a directory to be stored actually exists in the data server, and a program for realizing: a function of including information on a relatively lower directory in the file;