JP2006031249A - File management device, version number renumbering method and version number numbering program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a version controller and a version controlling method and a program for changing version numbers into version numbers in a new management system without changing the attribute values, preparation dates or update dates of objects to which the version numbers are added. <P>SOLUTION: Key attributes being attributes being the key of version numbers in a new management system and order attributes to specify the order and the arrangement order are inputted by an operation information input part 110, and object ID based on the combination of the key attributes is acquired by a control part 120 from an object information storage table stored in a table storing part 140, and the items of line numbers are set for each object ID. The items of the "version numbers" of the object information storage table are made "blank" by a table control part 130. Then, the object ID is aligned in an ascendent order based on the order attributes, and the numbers of the lines are numbered in the items of the line numbers, and the items of the line numbers are updated to the items of "version numbers" which have been made "blank". <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a file management apparatus that manages a document, an image file, and other objects with a version number, and a version number renumbering method and a version number renumbering program. File management apparatus, version number renumbering method, and version capable of changing the key attribute of an object and enabling automatic renumbering of the version number in accordance with the change of the key attribute Renumbering program.

  Generally, the version number assigned to an object such as a document or an image file is a value that is automatically assigned in the order of creation / update, so that it cannot be arbitrarily changed.

  For this reason, version number operations such as changing the version number management system or rearranging objects by version number cannot be performed.

  The version number assigned when registering an object can be specified, and if the specified version number is the same as the version number of the registered object, the registration cannot be performed so as not to cause inconsistency of the version number. As a prior art, there is one disclosed in Patent Document 1.

In the prior art disclosed in Patent Document 1, it is also possible to register an old version of an object after registering the latest version of the object.
JP 2002-123414 A

  However, in the prior art disclosed in Patent Document 1, it is necessary to select an object whose version is to be changed manually and repeat the renumbering process. In order to renumber existing objects, it must be taken out to another storage location, renumbered, and registered again. There is a problem that existing data may not be available.

  Therefore, the present invention provides a version control device, method, and program which can be changed to a version number in a new management system without changing the attribute value, creation date / time and update date / time of an object to which a version number is assigned. The purpose is to provide.

  In order to achieve the above object, the invention of claim 1 assigns a version number to an object stored as a key attribute serving as a reference for a version number management system, such as a document or an image file. In the file management apparatus to be managed, an object for specifying the order of the version number by the key attribute changing means for changing the key attribute which is a standard of the version number management system and the key attribute changed by the key attribute changing means The attribute having the key attribute changed by the key attribute changing unit is extracted, and the version number of the object is renumbered in the order specified by the order attribute specifying unit. And a version number renumbering means.

  According to a second aspect of the present invention, there is provided a file for managing at least one attribute of an object such as a document or an image file by assigning a version number to the object stored as a key attribute which is a standard of a version number management system. In the version number renumbering method of the management apparatus, the key attribute that is the basis of the version number management system is changed by the key attribute changing unit, and the order of the version number by the key attribute changed by the key attribute changing unit is specified The attribute of the object to be specified is specified by the order attribute specifying means, the object having the key attribute changed by the key attribute changing means is extracted, and the version number of the object is assigned in the order specified by the order attribute specifying means. It is characterized by renumbering by a renumbering means.

  According to a third aspect of the present invention, there is provided a file for managing at least one attribute of an object such as a document or an image file by assigning a version number to the object stored as a key attribute serving as a reference of a version number management system. A version number renumbering program for causing a computer to execute a version number renumbering process of a management apparatus, wherein the key attribute serving as a reference of the version number management system is changed, and the first step A second step of designating an attribute of an object for specifying the order of version numbers by the key attribute changed in the step; an object having the key attribute changed in the first step is extracted; and the second step The third step of renumbering object version numbers in the order specified in Characterized in that it comprises a.

  According to the present invention, a key attribute is specified from attribute information assigned to an object such as a document or an image file, and the key attribute is held based on an object attribute indicating the order of assigning version numbers. Since it is configured so that a unique version number is renumbered to the object, it is possible to renumber the object already assigned a version number with a new version number management system. Play.

  Hereinafter, an embodiment of a version control apparatus and method according to the present invention will be described in detail with reference to the accompanying drawings.

  Note that the version control device, method and program of the present invention can be applied to version number assignment in a device that manages versions such as documents, image files, source files, etc. Now, renumbering of version numbers in a document will be described.

  FIG. 1 is a system configuration diagram for performing version number renumbering by a file management apparatus according to the present invention.

  1 includes an operation information input unit 110, a control unit 120, a table control unit 130, a table storage unit 140, an object storage unit 150, and a temporary storage area 160.

  The operation information input unit 110 inputs conditions for renumbering the version number using the screen shown in FIG. The information to be input includes a “key attribute item” that is an attribute that is a key of the new version management system, and a “order specification item” that specifies the order of version numbers. An “order attribute” that is an attribute that designates the order and an “arrangement order” that is the order (ascending or descending order) can be input, and the version number is renumbered according to these pieces of information.

  The control unit 120 includes an extraction unit 121, a rearrangement unit 122, and a version number numbering unit 123, and controls renumbering of version numbers in a table in which version numbers are managed.

  The extraction unit 121 extracts a combination of key attribute items (hereinafter referred to as “attribute value set”) input by the operation information input unit 110 from the object information storage table stored in the table storage unit 140 without duplication, and further extracts them. The object ID corresponding to the set attribute value is acquired from the object information storage table.

  The rearrangement unit 122 sorts the object IDs acquired by the extraction unit 121 in ascending order based on the attribute specified by the forward attribute of the operation information input unit 110.

  The numbering unit 123 assigns line numbers to the object IDs arranged by the sorting unit 122. That is, when three object IDs are acquired, “1, 2, 3,...” Is assigned in the order of the object IDs arranged in ascending order.

  The processing of the extraction unit 121, the rearrangement unit 122, and the numbering unit 123 described above is repeated for the number of attribute value sets extracted by the extraction unit 121.

  The table control unit 130 sets the [version number] item of the object information storage table for renumbering the version number to “blank”, and after the version number is numbered by the numbering unit 123, the object information storage table Update.

  The table storage unit 140 stores an object information storage table in which object information such as a version number is managed.

  The object storage unit 150 stores objects such as documents and image files.

  The table storage unit 140 and the object storage unit 150 may be managed together.

  The temporary storage area 160 is an area where the extraction unit 121, the rearrangement unit 122, and the numbering unit 123 are processed. The table or the like stored in the temporary storage area 160 is deleted after a series of version numbers are renumbered.

  According to such a configuration, the version number can be renumbered according to the value of the attribute specified as the key attribute, and management can be performed based on a new version number management system.

  FIG. 2 is a diagram showing a table structure in a state before version number renumbering is performed by the version control apparatus according to the present invention.

  FIG. 2 is an object information storage table showing a version number management state, and shows a state where version numbers are managed under a management system in which “attribute 1” is designated as a key attribute.

  The object information storage table is sorted in ascending order using [object ID] as a primary key. At this time, the record with [object ID] “111111” has “AAA” as the value of [Attribute 1], “BBB” as the value of [Attribute 2], and “20031225130522” as the value of [Created Date / Time]. , “1” is stored as the value of [version number]. Such a configuration is held for each [object ID]. Here, the field having “blank” as the attribute value indicates that the object to which [object ID] is assigned does not have the attribute or that the attribute value is “blank”.

  For example, the value of [Attribute 3] of the record whose [Object ID] is “222222” is “blank”. This is because the object whose [Object ID] is “222222” has the attribute [Attribute 3]. This indicates that the attribute is [None] or [Attribute 3] is held but the value is "blank".

  Here, “blank” indicates that the value “NULL” is stored in the actual database structure.

  In the object information storage table having the above configuration, [Attribute 1] is set as a key attribute for managing the version number, grouping is performed by the [Attribute 1], and [Created date] is old Version numbers are assigned in order.

  In the example shown in FIG. 2, two values of “AAA” and “CCCC” are shown as the values of [Attribute 1]. First, object IDs “111111” and “222222” having “AAA” in [Attribute 1]. “333333” is assigned to the same group, and a version number is assigned based on [creation date]. Next, version numbers are similarly assigned to object IDs “444444” to “999999” having “CCCC” in [Attribute 1].

  FIG. 3 is a diagram showing a version management setting change screen for changing the management setting when the version number is renumbered by the version control apparatus according to the present invention.

  FIG. 3 includes a key attribute setting item 301 for setting an attribute as a key for version management, an order specifying item 302 for specifying the order of version numbers, an execution button 303, and a cancel button 304.

  The key attribute setting item 301 can designate a key attribute for managing a version number in the new management system, and includes a designated attribute name 305, an add button 306, and a delete button 307. For example, as shown in FIG. 3, when “attribute 1” and “attribute 2” are designated as the designated attribute name 305, a new version number is renumbered based on these attributes.

  At this time, to add an attribute to be a key attribute, an add button 306 is pressed to select an attribute to be added from a list of attributes that can be added. In order to change or delete the added attribute, the delete button 307 is pressed to select the attribute to be deleted from the currently displayed attributes.

  By these operations, attributes in a new management system can be specified.

  The order designation item 302 is an item for specifying the order of the version numbers according to the key attributes designated in the key attribute setting item 301. The order designation item 302 includes an order attribute designation item 308, a designation button 309, and an arrangement order 310.

  An order attribute designation item 308 designates an attribute of an object that specifies the order of version numbers by pressing a designation button 309.

  The sort order 310 selects either “ascending order” or “descending order” that is the sort order based on the attribute designated by the order attribute designation item 308.

  By pressing the execution button 303 for each item designated by these, a trigger for executing renumbering of the version number based on these conditions is triggered. It can be canceled by pressing a cancel button 304.

  Therefore, special attributes assigned to documents based on their respective usages can be handled in the same manner as general attributes, and can be designated as version number key attributes.

  FIG. 4 is a diagram showing the processing contents of the object information storage table by the version control apparatus according to the present invention.

  In FIG. 4, FIG. 4A is a table 401 showing a state in which all items of [version number] in the object information storage table shown in FIG. FIG. 4B shows a table 402 extracted from the table structure shown in FIG. 4A without duplication of attribute value sets of values of the key attributes set on the version management setting change screen 300 shown in FIG. It is. FIG. 4C is a table 403 in which one attribute value set is further extracted from the attribute value set extracted in FIG.

  As shown in FIG. 4 (a), only the [version number] item in the object information storage table of FIG. 2 is set to “blank” and preparations are made for assigning a new version number. A new version number is assigned for each attribute value set shown in FIG. In FIG. 4C, an attribute value set for numbering is designated.

  At this time, the table shown in FIG. 4 (b) and the table extracted from one attribute value set shown in FIG. 4 (c) are tables created in a temporary area when renumbering is performed. It is deleted as soon as the renumbering process is completed. This prevents an increase in disk capacity and prevents inconsistency because the database table is not manipulated.

  FIG. 5 is a diagram showing a version number numbering table for assigning version numbers.

  In FIG. 5, the object ID is extracted from the object information storage table in which the item “version number” shown in FIG. 4A is “blank” for the attribute value set shown in FIG. A table with the item added is shown.

  FIG. 5A shows an object ID “444444”, “666666”, “999999” having an attribute value set in which the value of attribute 1 is “CCCC” and the value of attribute 2 is “DDDD” in FIG. This is a table in which the item of [Line number] is extracted and assigned to the right side of the item of [Version number].

  FIG. 5B is a table in which the row number is sequentially assigned to the “row number” item in FIG. 5A with the “row number” item whose object ID is “444444” as “1”. .

  In this way, the value assigned to the item [line number] is updated to the item [version number] shown in FIG. 4A, and these processes are performed for each attribute value set shown in FIG. 4B. By sequentially repeating, renumbering can be performed with a new key attribute.

  At this time, it is created in the temporary area in the same manner as in FIG. 4B and FIG. 4C, and the version number is renumbered, and the [Version number] item in the object information storage table shown in FIG. It is erased when reflected.

  Through the above processing, the version number can be renumbered for the object having the specified attribute value set.

  In addition to the [object ID], items extracted from the object information table shown in FIG. 5A may be extracted in the same manner for items specified in the order attribute specification item 308 of FIG.

  For example, when the order attribute designation item 308 is “creation date / time”, both the [object ID] and [creation date / time] items are extracted simultaneously from the object information storage table shown in FIG. The arrangement may be such that the images are arranged in the arrangement order designated at 310.

  This makes it possible to renumber the version numbers based on the order specified in the order attribute specification item 308 shown in FIG. 3 even when the order of the created objects is different from the order in which the database is updated. An example of this case is shown in FIG.

  The processes shown in FIGS. 4C to 5B are repeated as many times as the number of attribute value sets extracted in FIG. 4B.

  As a result, the version number can be assigned to [version number] which is “blank” in the object information storage table 401 shown in FIG.

  FIG. 6 is a diagram showing an object information storage table in a state where the version number is renumbered by the version control apparatus according to the present invention.

  In FIG. 6, the processing of the tables shown in FIGS. 4C, 5A, and 5B is repeated in this order for the number of attribute value sets extracted in FIG. The table of the state which performed renumbering of is shown.

  That is, the version number renumbering function can be realized by updating the number of attribute value sets extracted.

  Next, a control flow until the version number is renumbered will be described.

  FIG. 7 is a flowchart showing version number renumbering processing.

  In FIG. 7, processing is started by an instruction to renumber the version number of the “object information storage table” which is a database table in which object information is stored in advance, and the key in the management system at the time of renumbering the version number The key attribute which is the attribute to be specified is designated using the version management setting change screen 300 shown in FIG. 3 (S701). At this time, the key attributes in the current management system are displayed by default. Further, the order attribute which is the attribute of the object specifying the order of the version number and the sort order which is the order sorted by the order attribute are designated (S702).

  When specified and executed, the item of the version number of the object information storage table is set to “blank” (NULL) (S703), and the attribute value set for the specified key attribute is extracted from the object information management table without duplication (S704). . An attribute value set table based on the extracted attribute value set is generated (S705).

  Further, the processes of S706 to S710 shown below are repeated. First, one attribute value set is extracted from the generated attribute value set table (S706), and an object ID corresponding to the attribute value set is obtained from the object information storage table (S707).

  A line number item is provided for each acquired object ID (S708), a line number is assigned to the line number item (S709), and the version number of the object information storage table with the version number item set to "blank" is set. The line number based on the object ID is updated in each item (S710).

  Then, the key attribute for renumbering the version number is updated (S711).

  FIG. 8 is a diagram showing a table of a modification of the table for assigning the version numbers shown in FIG.

  8 extracts [object ID] and the order attribute specification item 308 shown in FIG. 3 as items for renumbering the version number from the object information storage table shown in FIG. 4A, and adds line numbers. Shows the table.

  In the example shown here, “created date / time” is designated in the order attribute designation item 308, and further, sorting is performed in ascending order of “created date / time”.

  As a result, even when the order of the created objects is different from the order in which the database is updated, it is possible to assign line numbers to the line number items based on the order designated by the order attribute designation item 308 shown in FIG. Become.

  With the processing and configuration shown above, it is possible to renumber version numbers according to the desired attributes without changing specific information such as the creation date and time and the last modification date and time of objects with existing version numbers. become.

  Therefore, by applying the present invention, it is possible to manage the version number assigned to an object to be newly registered and the version number assigned to an existing object based on a new version number management system. Can be expected.

  The processing shown in the flowchart can also be realized by a version control program that can be executed by a computer.

  The present invention is not limited to the embodiments described above and shown in the drawings, and can be implemented with appropriate modifications within the scope not changing the gist thereof.

  The present invention can be applied to a version control apparatus and method that can manage an existing version number assigned to an object such as a document or an image file under a new version number management system. By specifying the attribute that is the key when renumbering the version number among the assigned attributes, all objects having the key attribute are managed based on the new version number management system. Useful for.

The block diagram of the version control apparatus concerning this invention. The figure which shows the table structure in the state before renumbering of a version number is performed. The figure which shows the change screen of the version management setting which changes the management setting at the time of renumbering of a version number with the version control apparatus concerning this invention. The figure which shows the processing content of the object information storage table by the version control apparatus concerning this invention. The figure which shows the version number numbering table which performs numbering of a version number. The figure which shows the object information storage table of the state in which the renumbering of the version number was performed. The flowchart which shows the renumbering process of a version number. The figure which shows the table of the modification of the table which numbers the version number shown in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 110 Operation information input part 120 Control part 121 Extraction part 122 Rearrangement part 123 Numbering part 130 Table control part 140 Table preservation | save part 150 Object preservation | save part 160 Temporary storage area

Claims (3)

In a file management apparatus for managing at least one attribute of an object such as a document or an image file by assigning a version number to an object stored as a key attribute serving as a reference of a version number management system,
Key attribute changing means for changing the key attribute which is a standard of the version number management system;
Order attribute specifying means for specifying the attribute of an object that specifies the order of version numbers by the key attribute changed by the key attribute changing means;
A version number renumbering unit that extracts an object having the key attribute changed by the key attribute changing unit and renumbers the version number of the object in the order specified by the order attribute specifying unit. A file management device characterized by the above. Version number renumbering method for a file management apparatus for managing at least one attribute of an object such as a document or an image file by assigning a version number to an object stored as a key attribute which is a standard of a version number management system In
Change the key attribute that is the basis of the version number management system by the key attribute changing means,
The attribute of the object that specifies the order of the version number by the key attribute changed by the key attribute changing means is specified by the order attribute specifying means,
Extracting the object having the key attribute changed by the key attribute changing means, and renumbering the version number of the object by the version number renumbering means in the order specified by the order attribute specifying means, Version number renumbering method. Version number renumbering processing of a file management apparatus that manages at least one attribute of an object such as a document or an image file by assigning a version number to the object stored as a key attribute serving as a reference for the version number management system A version number renumbering program that causes a computer to execute
A first step of changing the key attribute serving as a basis of the version number management system;
A second step of designating an attribute of an object that specifies the order of version numbers according to the key attribute changed in the first step;
A third step of extracting an object having the key attribute changed in the first step and renumbering the version number of the object in the order specified in the second step. Version number renumbering program.

Images