JP2008090677A - Data management device, data management method and computer program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable a user to store data in locations appropriately and to further easily retrieve data. <P>SOLUTION: The data management device 1 includes folders for each knowledge base category. An identification file SF for management object file is stored in the folder for each knowledge base category relevant to a management object file concerned. When the user retrieves a desired management object file, a knowledge base reference part 105 retrieves the identification file SF for management object file corresponding to a knowledge base category designated by the user. Names of management object files shown in the retrieved identification file SF are list-displayed. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an apparatus and method for managing data such as files.

  Conventionally, in a computer such as a personal computer or a workstation, a folder (directory) is used so that a user can easily manage data such as files. As described in Non-Patent Document 1, according to folders, the user can prepare a plurality of folders and classify files into any one of the folders for management.

  In recent years, recording media such as hard disks, DVD-RAMs, and USB memories have become increasingly large in capacity. In addition, various types of applications are distributed, and the use of computers is becoming increasingly diverse. Along with these changes, a large number of various files have been stored on recording media used in computers.

  Therefore, in the method of simply classifying files into folders, the user may not be able to manage the files sufficiently in the future.

Therefore, it is conceivable to use a method as described in Patent Document 1. According to this method, when a user drags and drops a folder icon onto another folder icon, a new folder is created in the same hierarchy as the dragged and dropped folder. Then, the shortcut file of the file stored in both folders is stored in the newly created folder.
JP 2005-198064 A "Standard PC Glossary of Terms Latest 2007-2008 Edition", edited by Hidekazu System First Publishing Editorial Department, published on May 15, 2006

  By the way, with the development of the technology as described above, an opportunity that one file has various uses or is used by various users is increasing. Therefore, it may be difficult for the user to determine which file should be classified into which folder. In addition, it may be difficult for the user to search in which folder the desired file is stored.

  However, the conventional technology described in Patent Document 1 cannot sufficiently solve these problems.

  In view of these points, the present invention enables a user to save data such as a file without losing the storage location, and allows the user to search for data such as a file more easily than in the past. The purpose is to make.

  The data management apparatus according to the present invention includes a data identification information storage unit that stores identification information of each piece of data in association with one or more of a plurality of categories, and a user specifies the plurality of categories. Data identification information search means for searching the data identification information storage means for the identification information of the data corresponding to the data, and data identification information for outputting to the user all or part of the searched identification information Output means.

  Preferably, the category is defined by combining a plurality of sections of different classes.

  Alternatively, the data identification information storage unit includes: a category definition unit for causing the user to perform an operation for defining the category; and an association unit for causing the user to perform an operation for associating the data with the category. When the user associates the data with the category, the identification information of the data is newly associated with the category and stored.

  According to the present invention, it is possible to allow a user to save data such as a file without losing the storage location, and to allow the user to search for data such as a file more easily than before.

  According to the invention of claim 2, the user can more easily search for data. According to the third aspect of the present invention, it is possible to accumulate knowledge about data and construct a knowledge base valuable to the user.

  FIG. 1 is a diagram showing an example of the external appearance and hardware configuration of the data management device 1, and FIG. 2 is a diagram showing an example of the functional configuration of the data management device 1.

  The data management apparatus 1 according to the present invention is an apparatus that manages various data in units of files. As the data management apparatus 1, a personal computer as shown in FIG. A workstation or a PDA (Personal Digital Assistant) can also be used.

  As shown in FIG. 1B, the data management apparatus 1 includes a CPU 10a, RAM 10b, ROM 10c, hard disk 10d, display 10e, keyboard 10f, pointing device 10g, NIC (Network Interface Card) 10h, USB port 10i, and other various types. It consists of a circuit.

  An operating system is installed in the hard disk 10d. As an operating system, for example, Windows (registered trademark) of Microsoft Corporation, MAC OS of Apple Corporation, or Linux can be used. According to these operating systems, a plurality of folders can be provided on the hard disk 10d, and various files can be classified and managed as one of the folders. In addition, a folder can be provided (subordinate) within the folder. In other words, the folder can have a hierarchical structure (tree structure). Folders are sometimes called “directories”.

  Further, the hard disk 10d has functions such as a classification data storage unit 101, a knowledge base storage unit 102, a new category registration processing unit 103, a new knowledge registration processing unit 104, and a knowledge base reference unit 105 as shown in FIG. The knowledge base management application to be realized is installed. According to this knowledge base management application, knowledge about a category can be given to a file stored in the hard disk 10d to construct a knowledge base. Hereinafter, a file managed by the knowledge base management application is referred to as “management target file KF”.

  Hereinafter, functions of each unit of the data management apparatus 1 illustrated in FIG. 2 and processing contents will be described.

  FIG. 3 is a diagram illustrating an example of the large partition table TB1, FIG. 4 is a diagram illustrating an example of the small partition table TB2, and FIG. 5 is a diagram illustrating an example of the hierarchy table TBN.

  The classification data storage unit 101 in FIG. 2 stores a large classification table TB1, a small classification table TB2, and a hierarchy table TBN. These tables are used when defining categories for classifying the management target file KF. Hereinafter, a category for classifying the management target file KF is referred to as a “knowledge base category”. The user of the data management device 1 can define the knowledge base category in various ways by appropriately combining large and small classes (levels). In the present embodiment, for the sake of simplicity of explanation, the knowledge base category is defined by combining two classes of categories “large category” and “small category”.

  In the major classification table TB1, one record is stored for each major classification, as shown in FIG. The “title” is a title for the user to easily recognize the major division. The “knowledge base large ID” is management identification information for distinguishing the large classification from other large classifications.

  In the small section table TB2, one record is stored for each small section as shown in FIG. “Title” is a title for the user to easily recognize the sub-section. The “knowledge base small ID” is management identification information for distinguishing the small section from other small sections.

  The hierarchy table TBN stores one record for each knowledge base category as shown in FIG. “Knowledge base large ID” and “Knowledge base small ID” indicate the knowledge base large ID and the knowledge base small ID of the large and small sections constituting the knowledge base category, respectively. The “knowledge base category ID” is identification information for identifying the knowledge base category from other knowledge base categories.

  For example, in the first record of the hierarchical table TBN shown in FIG. 5, the knowledge base category having the knowledge base category ID “T01” is classified into the large classification of the knowledge base large ID “L01” (that is, the large classification “password”). ) And “S02”, which is defined by a combination of large classifications of knowledge base small IDs (that is, small classification of “site entry”).

  FIG. 6 is a diagram showing an example of folder layers corresponding to the hierarchical structure of the classification root folder FL0 and the knowledge base category.

  Returning to FIG. 2, the knowledge base storage unit 102 stores data relating to the classification of each management target file KF stored in the hard disk 10 d into the knowledge base category. That is, knowledge base data is stored.

  Specifically, the knowledge base storage unit 102 stores data indicating in which knowledge base category each management target file KF is classified by the following method.

  A folder for classification is prepared in advance on the hard disk 10d. Hereinafter, this folder is referred to as “classification root folder FL0”. In the classification root folder FL0 (subordinate), a folder layer (directory layer) corresponding to the structure of each knowledge base category is created.

  For example, when seven knowledge base categories having knowledge base category IDs “T01” to “T07” shown in FIG. 5 are defined, a folder layer is formed as shown in FIG.

  Then, a file (hereinafter referred to as “identification file SF”) indicating identification information (for example, the file name and the folder name of the storage location folder) of the management target file KF is created, and the management target file KF is classified. The identification file SF of the management target file KF is stored in the lowest folder in the folder layer corresponding to the knowledge base category to be stored. As the identification file SF, a shortcut in Windows or an alias in Mac OS can be used.

  For example, when a certain management target file KF is classified into the knowledge base category “T01” shown in FIG. 5, the identification file SF of the management target file KF is a folder “L01” in the classification root folder FL0. It is sufficient to store in a folder with a folder name “S02” in the folder with the name.

  When the knowledge base data is managed by the method of FIG. 6, it can be said that the classification root folder FL0 is the knowledge base storage unit 102.

  The user can classify one managed file KF into a plurality of knowledge base categories. In such a classification, the identification file SF of the management target file KF may be stored one by one in the lowermost folder of the folder layer corresponding to each knowledge base category.

  7 and 8 are diagrams showing examples of the knowledge base management window WN1, and FIGS. 9 and 10 are diagrams showing examples of the large category window WN2.

  Returning to FIG. 2, the new category registration processing unit 103 performs processing for registering a new knowledge base category in the classification data storage unit 101, that is, processing for newly defining a knowledge base category. Such processing is performed in the following procedure.

  When a user inputs a predetermined command to the data management apparatus 1, a knowledge base management application is activated in the data management apparatus 1. After startup, a knowledge base management window WN1 as shown in FIG. 7 is displayed on the desktop of the data management apparatus 1.

  Here, the user clicks either the category list button BT13 or the new category creation button BT14. When defining a new knowledge base category already registered in the large category table TB1 in FIG. 3, the category list button BT13 is clicked. When a new major category is newly created and a knowledge base category is defined using the new category, the new category creation button BT14 is clicked.

  When the category list button BT13 is clicked, the new category registration processing unit 103 selects the major category registered in the major category table TB1 of the classification data storage unit 101 in the knowledge base management window WN1 as shown in FIG. The large division list LT11 shown is arranged in the display area RY12 and displayed again.

  The user finds a major category of the newly defined knowledge base category and selects the major category by clicking on the row. Then, the new category registration processing unit 103 displays a large category window WN2 related to the large category selected by the user as shown in FIG. 9A on the desktop.

  In the large category window WN2, the text box TX21 shows the title of the large category selected by the user. The subsection list LT2 shows the titles of the subsections used for defining existing knowledge base categories in combination with the large sections. These subdivisions and respective titles are based on the hierarchical table TBN of FIG. 5 and the subdivision table TB2 of FIG.

  The user confirms by looking at the subdivision list LT2 that the knowledge base category to be defined is undefined. Once confirmed, the new creation button BT21 is clicked.

  Then, as shown in FIG. 9B, the new category registration processing unit 103 arranges the definition button BT22 in place of the new creation button BT21, and adds a blank line at the very end of the small classification list LT2, The division window WN2 is displayed again.

  The user places the character cursor on a blank line in the small section list LT2 and inputs the title of the small section to be combined with the large section. Then, the definition button BT22 is clicked.

  Then, the new category registration processing unit 103 issues a new knowledge base small ID, and adds a new record indicating the knowledge base small ID and the title input by the user to the subdivision table TB2 of FIG.

  Further, a new knowledge base category ID is issued, and a new record indicating the knowledge base category ID, the large knowledge base large ID, and the small knowledge base ID is added to the hierarchy table TBN of FIG. A new knowledge base category is defined by the above processing.

  On the other hand, when the new category creation button BT14 is clicked in the knowledge base management window WN1 of FIG. 7, the new category registration processing unit 103 displays the large category window WN2 on the desktop. However, here, unlike the above example, the text box TX21 is left blank as shown in FIG. In addition, no subsection is shown in the subsection list LT2.

  The user inputs the title of the major category of the knowledge base category to be newly defined in the text box TX21 and clicks the new creation button BT21.

  Then, as shown in FIG. 10B, the new category registration processing unit 103 arranges the definition button BT22 instead of the new creation button BT21, adds a blank line to the small category list LT2, and sets the large category window WN2. Is displayed again.

  As in the case of FIG. 9B, the user inputs the title of the small section to be combined with the large section in the blank line and clicks the definition button BT22.

  Then, the new category registration processing unit 103 issues a new knowledge base small ID, and displays a new record indicating the knowledge base small ID and the title entered by the user in the blank line of the subdivision list LT2 in FIG. Add to the subdivision table TB2.

  In parallel or before and after this, a new knowledge base large ID is issued, and a new record indicating the knowledge base large ID and the title entered by the user in the text box TX21 is displayed in the large division table TB1 of FIG. Add to.

  Further, a new knowledge base category ID is issued, and a new record indicating the knowledge base category ID, the knowledge base large ID, and the knowledge base small ID is added to the hierarchy table TBN of FIG. A new knowledge base category is defined by the above processing.

  After the new knowledge base category is defined, the new category registration processing unit 103 prepares a folder layer corresponding to the knowledge base category in the knowledge base storage unit 102 (classification root folder FL0 in FIG. 6).

  FIG. 11 is a diagram showing an example of the file management window WN3, and FIG. 12 is a diagram showing an example of the category hierarchy window WN4.

  Returning to FIG. 2, the new knowledge registration processing unit 104 performs a process for registering new knowledge in the knowledge base storage unit 102. Such processing is performed in the following procedure.

  When the user creates a new file in the hard disk 10d and wants to immediately register the knowledge related to the file, the user clicks the new file management button BT12 in the knowledge base management window WN1 of FIG.

  Then, the new knowledge registration processing unit 104 displays a file management window WN3 as shown in FIG. 11A on the desktop.

  The user inputs the file name of the new file, the folder name of the save destination folder, the creator, and the creation date in the text boxes TX31, TX32, TX33, and TX34, respectively. Then, a new creation button BT31 is clicked.

  Then, the new knowledge registration processing unit 104 generates a file having attributes of contents input by the user in the text boxes TX31, TX33, TX34, and stores the file in a folder input by the user in the text box TX32. Is executed by the operating system.

  When the file is generated and saved, the new knowledge registration processing unit 104 arranges the knowledge base category list LT3, the hierarchy display button BT32, and the registration button BT33 as shown in FIG. 11B, and opens the file management window WN3. Display again.

  The knowledge base category list LT3 normally indicates a knowledge base category into which files specified by information indicated in the text boxes TX31 and TX32 are classified. However, since the file is immediately generated, no knowledge base category is shown in the knowledge base category list LT3.

  The user specifies in which knowledge base category the generated file is classified in a blank line of the knowledge base category list LT3. The user can specify the knowledge base category by inputting the major category and the minor category of the knowledge base category with the keyboard 10f. However, the user can also specify by performing a drag-and-drop operation with the pointing device 10g as follows. can do.

  When the user clicks the hierarchy display button BT32, the new knowledge registration processing unit 104 displays a category hierarchy window WN4 as shown in FIG. 12 on the desktop. In the category hierarchy window WN4, a list of knowledge base categories registered in the hierarchy table TBN of FIG. 5 is shown in a hierarchical structure. The user can operate this list in the same manner as Windows Explorer or File Manager. In other words, the plus (+) button can be clicked to expand the lower category, or the minus (−) button can be clicked to omit (close) the lower category.

  The user searches for a knowledge base category in which the file is to be classified from the category hierarchy window WN4, and displays an icon corresponding to the lowest layer category (in this embodiment, a small category) related to the knowledge base category in the file management window WN3. Drag and drop to the blank line of the knowledge base category list LT3.

  Then, the new knowledge registration processing unit 104 automatically inputs the information (for example, each title) of the major category and the minor category of the knowledge base category into the blank line.

  When the user designates the knowledge base category by any of the above methods, the user clicks the registration button BT33.

  Then, the new knowledge registration processing unit 104 generates an identification file SF (shortcut) of the file and stores it in the knowledge base category designated by the user in the knowledge base storage unit 102 (classification root folder FL0 in FIG. 6). The identification file SF is registered in the corresponding lowermost folder. As a result, new knowledge is stored in the knowledge base storage unit 102. The generated file is handled as the management target file KF after the above processing.

  Alternatively, when the user newly designates a file already stored in the hard disk 10d as the management target file KF and wants to register knowledge related to the management target file KF, the new file is displayed in the knowledge base management window WN1 of FIG. Click the create button BT11.

  Then, the new knowledge registration processing unit 104 displays a file management window WN3 configured as shown in FIG. 11B on the desktop. However, here, the text boxes TX31 to TX34 are blank.

  The user inputs a path of a file to be newly managed, that is, a file name and a storage location in the text boxes TX31 and TX32. Explorer may be displayed, and the icon of the file may be input by dragging and dropping.

  Then, new knowledge about the file is registered in the knowledge base storage unit 102 by the same operation and processing as described above. That is, the user designates in the blank line of the knowledge base category list LT3 which knowledge base category the file is classified into. The new knowledge registration processing unit 104 generates an identification file SF of the file, and in the knowledge base storage unit 102 (classification root folder FL0 in FIG. 6), the lowest layer corresponding to the knowledge base category designated by the user. Register to a folder. After the above processing, the file is handled as the management target file KF.

  Alternatively, the user can additionally register knowledge related to the existing management target file KF. This will be described later.

  FIG. 13 is a diagram showing an example of the knowledge base management window WN1, and FIG. 14 is a diagram showing an example of the file management window WN3.

  Returning to FIG. 2, the knowledge base reference unit 105 performs processing for causing the user to refer to the contents of the knowledge base stored in the knowledge base storage unit 102. Such processing is executed in the following procedure.

  When the user wants to refer to the contents of the knowledge base, the user clicks the hierarchy display button BT15 in the knowledge base management window WN1 of FIG.

  Then, the knowledge base reference unit 105 arranges a list of knowledge base categories registered in the hierarchy table TBN of FIG. 5 in a hierarchical structure in the display area RY11 as shown in FIG. This list can be operated in the same way as Explorer.

  When the user clicks on an icon corresponding to the lowermost category (small category) of the knowledge base category from the list, the knowledge base reference unit 105 displays a list of managed files KF classified in the knowledge base category. A management target file list LT12 is generated and arranged in the display area RY12. The management target file list LT12 can be generated based on the identification file SF stored in the subfolder folder related to the knowledge base category in the knowledge base storage unit 102.

  When the user wants to refer to the contents of any one of the management target files KF, the user selects the management target file KF by double-clicking the corresponding line in the management target file list LT12.

  Then, the knowledge base reference unit 105 notifies the operating system of the path (file name and folder name that is the storage location) indicated in the identification file SF of the management target file KF, and the management target file KF. To open. Then, the operating system activates an application corresponding to the management target file KF and opens the management target file KF as usual.

  Further, when the user wants to refer to the detailed knowledge about the management target file KF, the user selects the management target file KF by clicking the corresponding line in the management target file list LT12.

  Then, the knowledge base reference unit 105 displays a file management window WN3 indicating knowledge about the management target file KF, as shown in FIG. The role of each object in the file management window WN3 is as described above with reference to FIG. Here, in particular, the knowledge base category to which the management target file KF is classified is shown in the knowledge base category list LT3. These knowledge base categories can be obtained by searching the knowledge base storage unit 102 (F classification root folder FL0 in FIG. 6) for the hierarchy in which the identification file SF of the management target file KF is stored. it can.

  Here, the user can classify the management target file KF into yet another knowledge base category by performing the operation described above with reference to FIG. At this time, the new knowledge registration processing unit 104 in FIG. 2 registers new knowledge in the knowledge base storage unit 102 according to the procedure described above in accordance with the user's operation.

  FIG. 15 is a flowchart for explaining an example of the overall processing flow of the data management apparatus 1.

  Next, the flow of management processing of the management target file KF in the data management apparatus 1 will be described with reference to the flowchart of FIG.

  When the knowledge management application is activated or the user performs a predetermined operation, the data management device 1 displays a knowledge base management window WN1 (see FIG. 7) on the desktop (# 1).

  Until the user closes the knowledge base management window WN1 or ends the knowledge base management application, the data management apparatus 1 appropriately performs the processes of steps # 2 to # 12 according to the user's operation.

  When the user clicks the category list button BT13 or the new category creation button BT14 (Yes in # 3), the data management device 1 performs a process for defining a new knowledge base category.

  That is, the data management apparatus 1 displays the large category window WN2 (see FIGS. 9 and 10) on the desktop (# 4), and allows the user to specify a combination of the major category and the minor category of the new knowledge base category. Then, a knowledge base category is defined by registering a record indicating the combination in the hierarchy table TBN (see FIG. 5) (# 5). Note that the contents of the process are slightly different depending on which of the category list button BT13 and the new category creation button BT14 is clicked, but the contents are as described above. The same applies to the difference in processing when the next new file creation button BT11 or new file management button BT12 is clicked.

  When the user clicks the new file creation button BT11 or the new file management button BT12 (Yes in # 6), the data management apparatus 1 accumulates knowledge by newly classifying the management target file KF into one of the knowledge base categories. Perform the process.

  That is, the data management apparatus 1 displays the file management window WN3 (see FIG. 11) (# 7), and allows the user to specify the management target file KF to be classified and the knowledge base category to be classified. Then, the identification file SF of the management target file KF is stored in a subdivision folder corresponding to the knowledge base category in the classification root folder FL0 (see FIG. 6) (# 8). Thereby, the management target file KF is classified into the knowledge base category.

  When the user clicks the hierarchy display button BT15 (# 9), the data management apparatus 1 displays a list of knowledge base categories in the display area RY11 of the knowledge base management window WN1 as shown in FIG. Display in the format (# 10).

  Further, when the user clicks on the icon of a subdivision of any knowledge base category from the list (Yes in # 11), the data management device 1 stores the management target file KF classified in the knowledge base category. The management target file list LT12 as a list is displayed in the display area RY12 (# 12).

  Here, the user can newly classify the management target file KF shown in the management target file list LT12 into another knowledge base category and accumulate knowledge. In this case, the data management apparatus 1 displays the file management window WN3 (see FIG. 14) regarding the management target file KF selected by the user, and classifies the management target file KF into the knowledge base category designated by the user (#). 6 Yes, # 7, # 8).

  Alternatively, the user can check the contents of the management target file KF shown in the management target file list LT12. In this case, it may be selected by performing a predetermined operation (for example, double-clicking) on the row of the management target file KF to be confirmed. Then, the application corresponding to the management target file KF is started by the operating system, and the management target file KF is opened.

  According to the present embodiment, one managed file KF can be classified into a plurality of knowledge base categories. Therefore, the user can search for the management target file KF desired by the user more easily than in the past.

  In addition, it does not matter in which folder the management target file KF should be stored. In other words, the user can classify the management target file KF as described above regardless of the folder in which the management target file KF is stored as long as it is a folder under the management of the operating system of the data management apparatus 1. it can. Therefore, even when the management target file KF has various uses or is used by various users, the user does not have to worry about the storage location.

  Furthermore, according to the present embodiment, knowledge about the management target file KF can be accumulated in the knowledge base storage unit 102 more and more. Therefore, every time the user uses the data management apparatus 1, a knowledge base valuable to the user can be constructed.

  In this embodiment, the case where data is managed in units of management target files KF has been described as an example. However, the present invention can also be applied to cases where data is managed in other units. For example, if the present invention is applied to a database application, the unit data uniquely adopted in the database application may be associated with the knowledge base category. In this case, the identification file SF including information that can specify the data may be stored in a subfolder folder related to the knowledge base category.

  In the present embodiment, the knowledge base category is defined by combining the classifications of the second class, but the data management apparatus 1 may be configured to combine the classifications of three or more classes.

  In addition, the configuration of the entire data management device 1 or each unit, processing contents, processing order, table configuration, and the like can be appropriately changed in accordance with the spirit of the present invention.

It is a figure which shows the example of the external appearance and hardware constitutions of a data management apparatus. It is a figure which shows the example of a functional structure of a data management apparatus. It is a figure which shows the example of a large division table. It is a figure which shows the example of a small division table. It is a figure which shows the example of a hierarchy table. It is a figure which shows the example of the folder layer corresponding to the hierarchical structure of a classification | category root folder and a knowledge base category. It is a figure which shows the example of a knowledge base management window. It is a figure which shows the example of a knowledge base management window. It is a figure which shows the example of a large division window. It is a figure which shows the example of a large division window. It is a figure which shows the example of a file management window. It is a figure which shows the example of a category hierarchy window. It is a figure which shows the example of a knowledge base management window. It is a figure which shows the example of a file management window. It is a flowchart explaining the example of the flow of the whole process of a data management apparatus.

Explanation of symbols

1 Data Management Device 102 Knowledge Base Storage Unit (Data Identification Information Storage Unit)
103 New category registration processing section (category definition means)
104 New knowledge registration processing unit (association means)
105 Knowledge base reference section (data identification information retrieval means, data identification information output means)
10e Display (data identification information output means)
10f Keyboard (category definition means, association means)
10g pointing device (category definition means, association means)
KF managed file (data)
SF identification file (identification information)

Claims (5)

A data management device for managing data,
Data identification information storage means for storing identification information of each of the data in association with one or more of a plurality of categories;
Data identification information search means for searching the data identification information storage means for the identification information of the data corresponding to a user-specified one of the plurality of categories;
Data identification information output means for outputting to the user all or part of the retrieved identification information;
A data management apparatus comprising: The category is defined by combining a plurality of divisions of different classes.
The data management apparatus according to claim 1. Category defining means for allowing a user to perform an operation of defining the category;
Association means for causing a user to perform an operation of associating the data with the category,
The data identification information storage means newly stores the identification information of the data in association with the category when the user associates the data with the category.
The data management apparatus according to claim 1 or 2. A data management method for managing data,
The identification information of each of the data is stored in the data identification information storage means in association with one or more of a plurality of categories,
Search the data identification information storage means for the identification information of the data corresponding to the category specified by the user among the plurality of categories,
Outputting all or part of the retrieved identification information to the user;
A data management method characterized by the above. A computer program used in a computer for managing data,
A process of storing identification information of each of the data in a data identification information storage unit in association with one or more of a plurality of categories;
A process of searching the data identification information storage means for the identification information of the data corresponding to a user-specified one of the plurality of categories;
A process of outputting all or part of the retrieved identification information to the user;
A computer program for causing a computer to execute.