JP2005215743A - File attribute information management program, file attribute information management method, and file attribute information management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To flexibly set attribute information for each file. <P>SOLUTION: A document management server 10 comprises a document attribute information database 14 registering, to each document, unique static attribute information of the document concerned and, to each document belonging to the same document group (context) as the document concerned, dynamic attribute information effective in the same document group (context); and a context information database 15 setting and registering information for contexts. In a document storage part 33 of a user client 30, the document ID of a document used by a user and a context ID capable of identifying the context the document belongs to are stored together with this document. When a stored document is used, a display processing part 32 acquires the dynamic attribute information corresponding to the context the document belongs to by transmitting an acquisition request including the document ID and the context ID to the document management server 10, and displays it on a screen. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a file attribute information management apparatus and method, and more particularly, to an extended usage method of file attribute information.

  For files used and stored electronically by a computer, attribute information such as creation date and time and owner is usually added to the file header by a function of an operating system (OS). However, apart from that, in a system that uses files, for example, a document management system that is used when a document managed in a file format is shared by multiple users, unique attribute information is associated with each document. There are many cases to manage.

  Patent Documents 1 and 2 are examples of techniques for grouping and managing documents.

JP 2002-140323 A JP 2002-538554 A

  However, in a file management system such as a document management system, attribute information is set and managed efficiently and effectively in a format that is easy to use for the application programs that make up the system. Only one set of attributes can be set for.

  In other words, even when a document is used in various ways by various users in various usage situations, only one set of attribute information is set for the document. Inevitably, it must be used as common attribute information in each scene.

  The present invention has been made to solve the above-described problems, and an object thereof is to provide a file attribute information management method and apparatus capable of flexibly setting attribute information for each file.

  In order to achieve the above object, the present invention provides a program for causing a computer to function as a file attribute information management apparatus that manages file attribute information. Static attribute information storage means for storing static attribute information set as a unique attribute of the file, and dynamic attribute information set as an effective attribute in the file group for each file belonging to the file group The dynamic attribute information storage means to be stored and the dynamic attribute information corresponding to the file group to which the file included in the received file attribute information acquisition request belongs are read out from the dynamic attribute information storage means and returned. It functions as attribute information notification means.

  The attribute information notification unit reads out the static attribute information of the file from the static attribute information storage unit and returns the static attribute information together with the dynamic attribute information.

  In addition, the client device used by the user of the computer includes an acquisition unit that acquires a file to be managed by the file attribute information management device, and the file that clearly indicates a group to which the file acquired by the acquisition unit belongs The attribute information acquisition request is transmitted, and the dynamic attribute information of the file returned from the file attribute information management apparatus in response to the attribute information acquisition request is acquired and displayed.

  Furthermore, the display processing means has a function of changing a group specified in the attribute information acquisition request of the file.

  Further, the client device used by the provider of the file managed by the computer functions as dynamic attribute information registration means for setting and registering the dynamic attribute information for each group to which the created file belongs in the file attribute information management device. .

  In addition, information necessary for identifying the file that is explicitly indicated in the attribute information acquisition request of the file is stored in the file.

  Further, the display processing means stores the group information specified in the attribute information acquisition request of the file in the file.

  Further, the group information specified in the attribute information acquisition request of the file is stored in the file.

  The file attribute information management method according to the present invention is a file attribute information management method for managing file attribute information.For each file, static attribute information as an attribute unique to the file, For each file belonging to each of one or more groups to which the file belongs, the file attribute is managed by setting dynamic attribute information as an effective attribute in the file group.

  The file attribute information management apparatus according to the present invention includes, for each file, static attribute information storage means for storing static attribute information set as an attribute unique to the file, and for each file belonging to the file group. Corresponding to the dynamic attribute information storage means for storing the dynamic attribute information set as an effective attribute in the file group and the file group to which the file included in the sent file attribute information acquisition request belongs Attribute information notifying means for reading at least the dynamic attribute information to be read from the dynamic attribute information storage means and returning the dynamic attribute information.

  The client device according to the present invention is acquired by the acquisition unit for acquiring a file to be managed by the file attribute information management device in the client device used by the user of the file attribute information management device, and the acquisition unit. The attribute information acquisition request for the file specifying the group to which the file belongs is transmitted, and the dynamic attribute information of the file returned from the file attribute information management device in response to the attribute information acquisition request is acquired and displayed. Display processing means.

  Also, in the client device used by the file provider managed by the file attribute information management device, dynamic attribute information registration for setting and registering in the file attribute information management device dynamic attribute information for each group to which the created file belongs It has the means.

  According to the present invention, it is possible to set dynamic attribute information having different contents depending on the file group to which the file belongs to one file. From the viewpoint of a file group, in addition to file-specific attribute information (static attribute information), attribute information (dynamic attribute information) effective in the file group is set for each file belonging to each file group. Therefore, document management in file group units can be easily performed.

  Hereinafter, preferred embodiments of the present invention will be described with reference to the drawings. In this embodiment, an electronic document is taken as an example of a file used by the computer system, and the electronic document (hereinafter simply referred to as “document”) is a document management server corresponding to the file attribute information management apparatus according to the present invention. The case of centralized management will be described as an example.

  FIG. 1 is a block diagram showing a document management system according to this embodiment. The document management system according to the present embodiment includes a document management server 10 that manages documents managed by the system and attribute information thereof, one or more provider clients 20, and user clients 30. ) 1 is connected. In FIG. 1, one client 20 and 30 is shown for convenience. The document management server 10 can be realized by a general-purpose server computer in terms of hardware. The provider client 20 is used by a user (document provider) who creates a document managed by this system. The user client 30 is used by a user (document user) who uses a document created by a document provider for reference, printing, and the like. Each client 20 and 30 can be realized by a general-purpose personal computer (PC) in terms of hardware. In the present embodiment, the client device is illustrated and described separately for the sake of convenience, the client 20 used by the document provider and the client 30 used by the document user. And a user of a document created by another user, one PC can be both the provider client 20 and the user client 30.

  The provider client 20 includes a document registration processing unit 21 and a created document database 22. The document registration processing unit 21 newly creates a document to be managed by this system, and registers the document and its attribute information in the created document database 22 and the document management server 10. Furthermore, when the information regarding the context to which the document belongs is not set, the information regarding the context is set. In the present embodiment, a group of one or more documents is particularly referred to as a “context”. Information set for each context is set as dynamic attribute information of the document by associating it with the document. That is, in the document handled in the present embodiment, the static attribute information unique to the self and the dynamic attribute information corresponding to the document group to which the self belongs are set as the attribute information of the document. Details of the attribute information set in this document will be described later. In this embodiment, a description will be given on the assumption that a document created by itself is stored in a disk device (created document database 22) mounted on a provider client 20 used by itself. You may make it preserve | save in other storage means, such as a shared disk apparatus and a database server.

  The user client 30 includes a document acquisition processing unit 31, a display processing unit 32, and a document storage unit 33. The document acquisition processing unit 31 acquires a document by downloading from the document management server 10 by a user operation. Alternatively, a document transmitted from the provider client 20 is acquired. Then, the acquired document is stored in the document storage unit 33. The display processing unit 32 displays the attribute information of the document whose attribute information is held and managed by the document management server 10.

  The document management server 10 includes a document management unit 11, a notification processing unit 12, a shared document database 13, a document attribute information database 14, and a context information database 15. The document management unit 11 cooperates with the document registration processing unit 21 at the time of document registration to register a newly created document sent from the provider client 20 in the shared document database 13 and to register the attribute information of the document. General management of documents handled by this system is performed, such as registration in the document attribute information database 14 and further registration of context information in the context information database 15. Further, the document management unit 11 cooperates with the document acquisition processing unit 31 when using a document to read out the corresponding document from the shared document database 13 in response to a request sent from the user client 30 and use the document. Download to the client 30. The notification processing unit 12 transmits the attribute information of the corresponding document to the user client 30 in response to a request sent from the user client 30.

  In the present embodiment, various functions are provided by the above-described components, but each processing function in the document management server 10 and each client 20 and 30 is realized by operating an application on each computer.

  2 shows a configuration example of attribute information registered in the document attribute information database 14 by the document attribute setting process, and FIG. 3 shows a configuration example of context information registered in the context information database 15 by the context setting process. Each is shown. FIG. 4 is a conceptual diagram showing the relationship between the document and the context. Here, the concept of context and the attribute information characteristic in the present embodiment will be described with reference to FIGS.

  In this embodiment, two types of attribute information, static attribute information and dynamic attribute information, are set for a document. The static attribute information is an attribute unique to each document, and is unique information depending on each document such as a document name, a document ID, and a creator as illustrated in FIG. On the other hand, the dynamic attribute information is an attribute that is set to be effective for each document belonging to the document group when the documents are handled in groups. In the present embodiment, each document attribute is set for each document group called “context”, so that it is set as dynamic attribute information of the document. If one document belongs to a plurality of groups, the single static attribute information described above and dynamic attribute information for the number of groups to which the document belongs are set as attribute information. Valid / invalid included in the dynamic attribute information is information indicating whether the document is valid or invalid in the context. The presence / absence of notification sets whether to notify a client user who opened a document that previously belonged to the context to the context that the document newly belongs. Here, the relationship between the document and the attribute information will be further described with reference to FIG.

  FIG. 4 shows two contexts of “development work” and “functional specification”. A “development work” is a document group of specifications created for a project, and this document group includes requirement specifications, basic specifications, and functional specifications. On the other hand, a document group called “functional specifications” is a document group of functional specifications, and each version of the functional specifications is included in this document group. In FIG. 4, a group to which each document belongs is schematically indicated by an arrow. It is assumed that context identification information (ID) C1 is assigned to “development work”, and context ID C2 is assigned to “functional specification”.

  Here, attention is paid to identification information (ID) assigned to each document. First, each document is assigned a unique document ID = D1 to D5 as static attribute information. Furthermore, since the required specification and the basic specification belong to “development work”, the context ID = C1 is assigned separately from the document ID. Further, since the functional specification first edition and the functional specification second edition belong to the “functional specification”, the context ID = C2 is assigned separately from the document ID. Here, since the functional specification version 3 belongs to two contexts “development work” and “functional specification”, two context IDs = C1 and C2 are assigned.

  As shown in FIG. 3, the dynamic attribute information set in correspondence with the context includes the context ID and context name for identifying each context, the attribute information, and the document ID of the document belonging to the context. Yes. The document ID is a document group belonging to the context. According to the example of FIG. 3, it can be seen that the context “development work” includes document IDs = D1, D2, and D5.

  Next, a document registration process performed when a document is newly created in the present embodiment will be described with reference to the flowchart shown in FIG.

  In the provider client 20, when a document provider creates a document, as will be described later, a predetermined operation is performed on the created document from a predetermined setting screen, and the behavior corresponding to the context to which the created document belongs. However, in order to set dynamic attribute information, information related to the context to which the created document should belong must be set in advance.

  Therefore, when the context information has not been set yet, the document registration processing unit 21 causes the document provider to input the context name and attribute information from a predetermined setting screen, and cooperates with the document management unit 11 to operate the context information database 15. The context information having the configuration illustrated in FIG. 3 is set and registered (step 101). The document management unit 11 automatically assigns a unique context ID to a newly set and registered context.

  Subsequently, the document registration processing unit 21 inputs information to be specified by the user such as a document name, a creator, and usage restriction information from a predetermined setting screen by the document provider, and operates in cooperation with the document management unit 11. Static attribute information is set and registered in the document attribute information database 14 (step 102). In the data configuration example illustrated in FIG. 2, a unique ID is automatically assigned to the document ID by the document management unit 11. In addition, the system automatically designates information that the system can obtain, such as the creation date and time.

  Subsequently, the document registration processing unit 21 causes the document provider to input information that needs to be specified by the user, such as a default flag and attribute information, from a predetermined setting screen, and cooperates with the document management unit 11 to input the information. The dynamic attribute information is set and registered in the document attribute information database 14 in association with the static attribute information (step 103). The context ID included in the dynamic attribute information is written by the document management unit 11 in the above series of operations. On the other hand, the document ID of the document is additionally registered in the corresponding context information as shown in FIG.

  Finally, the document registration processing unit 21 cooperates with the document management unit 11 to register the created document in the shared document database 13 (step 104). As a result of the above processing, the information exemplified in FIGS. 2 and 3 is set and registered in the document management server 10. However, in this embodiment, the provider client 20 also stores the self-created document and attribute information of the document locally in the created document storage unit 23.

  In another preferred embodiment, the document registration processing unit 21 cooperates with the document management unit 11 to store the document ID and context ID assigned in step 103 in the created document file, and to share the document. Register in the database 13.

  As described above, according to the present embodiment, a document group (context) is newly defined as necessary, and each document has static attribute information unique to the document and a context to which the document belongs. Based on the dynamic attribute information. In the above description, the processing procedure for setting and registering the information to be handled as context information, static attribute information, and dynamic attribute information has been described. For example, after the setting process in the provider client 20, the document management server 10 The processing procedure is not limited to the example of the processing procedure described above, such as performing registration processing in each database together. This setting registration process generates a wizard that is classified according to cases such as setting a new context or registering a document in an existing context, and operates the document creator according to the process flow according to the situation. It is preferable to do so.

  When a document user uses a document, he / she does not acquire the document from outside each time, but saves the document once acquired actively or passively from the outside in the document storage unit 33 and uses it. In this case, it is taken out from the document storage unit 33 and used.

  Here, actively acquiring a document corresponds to a case where a document is downloaded from the document management server 10 by a mouse operation by a document user such as drag and drop. At this time, the document user declares to which context the acquired document belongs. Specifically, referring to FIG. 4, when a document user tries to acquire “functional specification 3rd edition” by a document acquisition operation such as drag and drop, the document acquisition processing unit 31 specifies the operation by the operation. By searching the document attribute information database 14 based on the document ID of the “functional specification third edition”, it can be confirmed that the document belongs to a plurality of contexts “development work” and “functional specification”. . At this time, the document acquisition processing unit 31 displays a list of context names in a predetermined window and causes the document user to select one. In this way, the document user is made to declare the context to which the document belongs. In this way, the document acquisition processing unit 31 stores the document ID and context ID of the document in association with the document to be acquired in the document storage unit 33. As shown in FIG. 2, a default flag is set in each context to which each document belongs. Therefore, when declaring a context, it is possible to omit the selection operation by setting the context in which the default flag is set as the default context.

  In another preferred embodiment, the document ID and the context ID are stored in the document file, and the selection operation may be omitted by setting the context ID stored in the document file as a default context. Is possible. In such an embodiment, a document user who obtains a document can create a plurality of document files with different settings as to which context the document user should use the document. It is possible to publish as a shared document so that a document file in which the context is set can be acquired. In addition, since special processing associated with document acquisition processing is not required, the document acquisition processing unit 31 can be configured by widely and generally used document acquisition processing means such as a Web browser.

  Also, passively acquiring a document corresponds to receiving an e-mail with the corresponding document as an attached file. In this embodiment, the document provider associates and registers the document and the document attribute information in the created document database 22 so that the document provider may directly distribute the document. Send the document with the context to which the belongs. Since it is necessary to clearly indicate the context to which the transmission document belongs, in the present embodiment, flag information called default context is included in the dynamic attribute information and registered in the document attribute information database 14 and held in the created document database 22. The default context is added to the transmission document and the mail is transmitted. Thereby, the document acquisition processing unit 31 can specify the context to which the received document belongs, and stores the received document in the document storage unit 33 in association with the document ID and context ID of the document.

  In another preferred embodiment, the document ID and the context ID are stored in the document file. By using the context ID stored in the document file as a default context, the created document database 22 and the document are stored. Since there is no need to store the default context in each of the storage units 33, each of the created document database 22 and the document storage unit 33 can be configured by widely used document storage means such as a file system provided by the OS. . In such an embodiment, the context in which the document user who acquires the document should use the document can be individually set when the document provider transmits it to the document user. In addition, even when a document user sends a document to another document user and uses it, the document user who obtains the document transmits the document in which context the document should be used. Can be set individually.

  As described above, when a document user acquires a document to the user client 30, the context to which the document belongs is specified together with the document.

  Next, an operation when a document user uses a document managed by this system in the present embodiment will be described with reference to the flowchart shown in FIG.

  When the document user selects a document to be used by clicking the icon of the document stored in the local document storage unit 33 displayed on the screen (step 121), the display processing unit 32 displays the document ID of the selected document. And the context ID are read from the document storage unit 33, an attribute information acquisition request including each ID is generated and transmitted to the document management server 10 (step 122).

  In the document management server 10, upon receiving the attribute information acquisition request sent from the user client 30, the notification processing unit 12 searches the document attribute information database 14 based on the document ID and context ID included in the request. Then, the dynamic attribute information corresponding to the context ID is extracted from the registered ones and returned to the user client 30 that is the request source.

  In the user client 30, when receiving the attribute information returned in response to the transmitted attribute information acquisition request, the display processing unit 32 displays the received dynamic attribute information on the property screen as exemplified in FIG. (Step 123). According to the example shown in FIG. 7, the document user is a user of “functional specification 3rd edition” belonging to the context of “development work”, and therefore, the static attribute of the document is displayed on the property screen. The dynamic attribute information corresponding to the information and the context “development work” is displayed, and the dynamic attribute information corresponding to the context “functional specification” is not displayed.

  In the present embodiment, context information, file information, and registration information can be referred to in addition to attribute information from the property screen. Various information can be displayed on the property screen by clicking the tab 40 on the corresponding screen (steps 124 and 125). FIG. 8 shows a display example when the context information tab 40 is click-selected. As shown in FIGS. 2 to 4, the context “development work” includes requirement specifications, basic specifications, and functional specifications 3rd edition. According to the example shown in FIG. Is displayed on the screen. When the button 44 provided in the context name display field is clicked, a list of contexts to which “functional specification 3rd edition” belongs is displayed. When another context, that is, “functional specification” according to the above example is selected by the document user from this list, information on the document belonging to the corresponding context is switched and displayed in the display area 42. A display example at this time is shown in FIG.

  FIG. 10 shows a display example when the attribute information tab 40 is click-selected after changing the context. From this display example and FIG. 2, the dynamic attribute information of the document “functional specification third edition” is the same. But you can see that the contents are different.

  Since the information displayed on the screen is registered in the document management server 10, the display processing unit 32 sends an information acquisition request including the document ID and the context ID to the document management server 10 at the timing when the selection operation such as tab click is performed. Send and acquire and display information required for display. However, various information related to the document selected in step 121 can be displayed on the property screen. In the above description, only attribute information is acquired from the document management server 10 when a document is selected (steps 121 to 123). However, all information that can be displayed in relation to the selected document is displayed. You may make it acquire collectively at the time of document selection.

  When the file information tab is selected, static attribute information such as the file name and file size of the document is displayed on the screen. When registration information is selected, static attributes such as the creator of the document and the creation date and time are displayed. Information is displayed on the screen.

  In the present embodiment, the property screen exemplified above is displayed according to the document selection operation, and attribute information and the like are displayed in the screen. However, the information display using the property screen shown in FIG. The form need not be limited to this. For example, it may be possible to select whether or not to display the property screen. In this embodiment, static attribute information and dynamic attribute information are handled and displayed as different information, but may be displayed together as the same attribute information.

  FIG. 11 shows the relationship between the document and the context when the document with the document ID = D6 “system design specification” is added to the context “development work” in FIG. After the “system design document” is registered in the document management server 10, when “functional specification 3rd edition” stored in the document storage unit 33 is selected in the same manner as described above, the context as shown in FIG. Information related to the “system design specification” is displayed. On the other hand, when “functional specification” is selected as the context, information related to the document belonging to the corresponding context is switched and displayed in the display area 42. At this time, the context “functional design” includes “system design”. Since the “specification” is not included, the display content is the same as in FIG. Note that the attribute information displayed at this time remains the same as in FIG.

  According to the present embodiment, it is possible to set different attribute information for each context to which the document belongs in the same document. Thus, when document management is performed using the concept of context, for example, when it is desired to notify a document user that a description error has been found in a basic specification, the document ID of “functional specification 3rd edition” and “development work” By clearly indicating the context ID “”, it is possible to notify only the corresponding document user, that is, the user who uses the “functional specification 3rd edition” belonging to the context of “development work”. . In other words, even a user of “functional specification 3rd edition” can be prevented from notifying a user who uses “functional specification 3rd edition” belonging to the context of “functional specification”.

  Focusing on this from the viewpoint of a context (document group), in addition to document-specific attribute information (static attribute information), attribute information (dynamic attribute information) effective in the context for each document belonging to each context Therefore, it is possible to easily manage documents in context units.

It is the block block diagram which showed the document management system in this Embodiment. It is the figure which showed the example of a structure of the attribute information registered into the document attribute information database in this Embodiment. It is the figure which showed the structural example of the context information registered into the context information database in this Embodiment. It is the conceptual diagram which showed the relationship between the document and context handled in this Embodiment. It is the flowchart which showed the document registration process in this Embodiment. It is the flowchart which showed the operation | movement at the time of a document user using a document in this Embodiment. It is the figure which showed the example when attribute information is displayed on the property screen displayed at the time of document utilization in this Embodiment. It is the figure which showed the example when context information is displayed on the property screen displayed at the time of document utilization in this Embodiment. It is the figure which showed the example of a display when a context is changed on the property screen displayed at the time of document utilization in this Embodiment. It is the figure which showed the example when attribute information is displayed after changing a context on the property screen displayed at the time of document utilization in this Embodiment. It is the conceptual diagram which showed the relationship between the document and the context after the document which belongs to a context is newly registered in this Embodiment. It is the figure which showed the example when context information is displayed on the property screen displayed at the time of document utilization after the document which belongs to a context is newly registered in this Embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 Document management server, 11 Document management part, 12 Notification process part, 13 Shared document database, 14 Document attribute information database, 15 Context information database, 20 Provider client, 21 Document registration process part, 22 Created document database, 23 Created document Storage unit, 30 user client, 31 document acquisition processing unit, 32 display processing unit, 33 document storage unit.

Claims (12)

A program for causing a computer to function as a file attribute information management device for managing file attribute information,
For each file, static attribute information storage means for storing static attribute information set as an attribute unique to the file,
Dynamic attribute information storage means for storing dynamic attribute information set as an effective attribute in the file group for each file belonging to the file group;
Attribute information notifying means for reading out the dynamic attribute information corresponding to the file group to which the file included in the file attribute information acquisition request sent from the dynamic attribute information storage means returns,
File attribute information management program characterized in that In the file attribute information management program according to claim 1,
The attribute information notification unit reads out the static attribute information of the file from the static attribute information storage unit, and returns the file with dynamic attribute information. A client device used by a computer user according to claim 1,
Obtaining means for obtaining a file to be managed by the file attribute information management device;
The attribute information acquisition request for the file specifying the group to which the file acquired by the acquisition unit belongs is transmitted, and the file dynamic information returned from the file attribute information management device in response to the attribute information acquisition request Display processing means for acquiring and displaying attribute information;
A program characterized by making it function. The program according to claim 3,
The display processing means has a function of changing a group specified in an attribute information acquisition request of the file.   A dynamic attribute information registering unit configured to register, in the file attribute information management apparatus, dynamic attribute information for each group to which the created file belongs a client device used by a file provider managed by the computer according to claim 1. A program characterized by functioning. The program according to claim 5,
A program characterized in that information necessary for identifying the file specified in the attribute information acquisition request for the file is stored in the file. The program according to claim 4, wherein
The display processing means stores information on a group specified in an attribute information acquisition request of the file in the file. The program according to claim 5 or 6,
A program storing information of a group specified in an attribute information acquisition request of the file in the file. In the file attribute information management method for managing file attribute information,
By using management means, each file is set by setting static attribute information as an attribute unique to the file and dynamic attribute information as an attribute effective in one or more groups to which the file belongs. A file attribute information management method characterized by managing attributes. For each file, static attribute information storage means for storing static attribute information set as an attribute unique to the file,
Dynamic attribute information storage means for storing dynamic attribute information set as an effective attribute in the file group for each file belonging to the file group;
Attribute information notifying means for reading out and returning at least dynamic attribute information corresponding to the file group to which the file included in the file attribute information acquisition request sent from the dynamic attribute information storage means;
A file attribute information management apparatus comprising: In the client device used by the user of the file attribute information management device according to claim 10,
Obtaining means for obtaining a file to be managed by the file attribute information management device;
A dynamic attribute of the file that is sent back from the file attribute information management device in response to the attribute information acquisition request is transmitted together with the attribute information acquisition request of the file specifying the group to which the file acquired by the acquisition unit belongs Display processing means for acquiring and displaying information;
A client device comprising: In the client device used by the file provider managed by the file attribute information management device according to claim 10,
A client apparatus comprising dynamic attribute information registration means for setting and registering dynamic attribute information for each group to which the created file belongs in the file attribute information management apparatus.

Images