JPH1115709A - Method and device for managing version - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a version managing method which easily arranges versions of a file. SOLUTION: A rack 110 is shown on a display 100. Plural file cases 112A to 112D are arranged in the rack 110. The cases 112A to 112D respectively contain a series of files of different versions that have the same file name. The newest files 116A to 116D are placed on the cases 112A to 112D and the files of the other back numbers are contained in the file case.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file management method and apparatus, and more particularly to a version management method and apparatus suitable for an individual using a personal computer at home or the like to manage file versions.
The present invention also relates to a program for causing a computer to execute a file management method.

[0002]

2. Description of the Related Art In recent years, personal computers have become widespread not only in offices but also in homes. At home, a CD like a magazine
-Possible uses include viewing ROM titles and CD-ROM catalogs for mail-order sales, accessing the Internet to obtain interesting information, and organizing photos taken with a digital camera. CD-RO as well as magazines and mail-order catalogs using paper as media
In the case of electronic media such as M and publications obtained through a network, the publication cycle is often determined. Electronic publications that are published periodically include Vol. And No. And so on.
Further, when organizing photos taken by a digital camera, a serial number is assigned to each of the photos so that the photos can be identified. Further, in software such as a game, the version is different each time the function is improved.

[0003] In the following description, electronic publications (including those published by a scanner after being published on paper) and programs such as photographs and game software are collectively referred to as files. Then, Vol. Used to identify each file. And No. And the serial number and version (ver.) Are collectively referred to as a version. In addition, the version may include the number of electronic publications (xx / yy) and the date of publication.

Conventionally, as a method of managing file versions on a personal computer, for example, US Pat. No. 5,065,
As described in JP-A-347-347, a method of classifying and managing files hierarchically using directories is known. The directory configuration is displayed on the display as a list, and the user can change the configuration by operating files and directories with the mouse. This method is the same for desktop metaphors, which are the mainstream of personal computer screens in recent years. The desktop metaphor mimics the desk in an office, and can therefore be said to be a metaphor suitable for using a personal computer in an office.

[0005]

However, when managing the version of a file such as an electronic publication at home, when managing the version using the file management method using directories or the desktop metaphor as described above, However, the user has no choice but to devise the way of naming the files / directories and the directory structure, which imposes a burden on the user, and there is a problem that the file versions cannot be easily arranged.

An object of the present invention is to provide a version management method and apparatus which can easily organize file versions. Furthermore, a program for implementing the file management method may be provided.

[0007]

In order to achieve the above object, the present invention has the following arrangement.

[0008] A plurality of electronic files (hereinafter, files) stored in the storage device are displayed on the display means in the following procedure. The files are divided into groups, and at least display areas for the number of groups are provided in the display means, and the representative images of each group are displayed in the display areas. The representative image is related to the files included in the group, and when specified by the user, a predetermined file in the group is executed. The execution includes displaying the contents of an electronic file, and executing the program if the electronic file is a program. The present invention is also a program for causing a computer to execute the display. Furthermore, a version control device provided with a processing device (CPU) performs the following processing by the processing device. The display device is provided with display areas corresponding to the number of groups into which the electronic files stored in the storage device are divided, and each display area displays a representative image of each group.

At this time, the grouping may be the same file group having different versions. The version includes multiple electronic publications with different issues. The representative image includes (1) an image indicating a predetermined file in a group, and (2) an image indicating an entire group. The predetermined file of (1) includes a file created latest, a file recently accessed by a user, a file recently stored in a storage device, and the like. Here, there may be two or more predetermined files. The displayed contents of (1) include a part of a file extracted (for example, a cover of an electronic publication and a part thereof), and a part created from a predetermined file. Also, as (2), what is common to files is extracted (for example,
Electronic publication title logo). In the case of (2), when a representative image is designated, a predetermined file in the group is executed. In order to execute such a process, the representative image is associated with a predetermined file. Note that this predetermined file may be the same as in the case of the above (1). Note that both (1) and (2) may be displayed. As described above, there may be two or more representative images of each group.

[0010] When the display area is specified by the user, an image corresponding to a file other than a predetermined file among the files of the group corresponding to the display area may be displayed in the display area. The number of images corresponding to files other than the predetermined file displayed in the display area may be limited to a predetermined number, and an image exceeding the predetermined number may be displayed when another display area is designated. .

(1) The present invention can be expressed as follows. The present invention includes storage means for storing data of a file group having different versions, display means, and arithmetic processing means for performing processing for displaying on the display means using the data stored in the storage means. In a version management method for managing a group of files having different versions by using a system, a rack including a plurality of file cases is displayed on the display unit, and the plurality of file cases have the same file name as if they were respectively. It processes as if a series of files having different versions are stored. For example, if a certain file case is specified, a series of files is displayed. Note that, here, expressions such as a rack and a file case are used, but any name such as a bookshelf may be used as long as the function described in the section of the embodiment can be exhibited.

According to such a method, the versions of the file can be easily arranged.

[0013] Preferably, an image representing a series of files may be displayed on the file case.

(2) In the above (1), preferably,
In the file case, it is displayed as if the file with the latest creation date was stored. In the file case, whether the file group of the back number (other than the file with the latest creation date) was stored is displayed. Is processed as follows.

According to this method, the version of the file can be handled intuitively, and the burden of version management can be reduced. (3) In the above (1), preferably, the file The file is displayed as if it contains the newest file of the day, and the file case is processed as if it contained a file group with a back number.

[0016] With this configuration, the file with the latest usage date is placed at the top, so that access to the file with the latest usage date can be facilitated.

(4) In the above (2) or (3), preferably, a reduced image of the file stored in the file case is displayed on the file case as a file icon. . Note that the display area may be displayed in association with the file case, not necessarily on the file case. This is the same in the above (1) to (3). In the following, the word “storage” is used to indicate that the file is displayed as if it were stored.

According to this method, the contents of the file can be easily understood at a glance by the icon of the image, so that the file listing can be improved.

(5) In the above (2) to (4), preferably, the files stored in the file case are arranged and displayed in chronological order of use date and time.

According to this method, the order of access can be determined from the order in which the files are arranged, so that the visibility of recently accessed files can be improved.

(6) In the above (1), preferably,
If the number of files stored in the file case exceeds a predetermined number, the file case may be processed so as to store the file exceeding the predetermined number in a warehouse distinguished from the file case.

The warehouse may be any display area other than the above-mentioned file case.

According to this method, files exceeding a predetermined number are automatically stored in the warehouse, so that the burden on the user for organizing the files can be reduced.

(7) In the above (6), preferably,
The files stored in the warehouse are sequentially selected from the files stored in the file case in descending order of use date and time.

According to this method, a file that is likely to be used is left in the file case, and a file that is unlikely to be used is stored in the warehouse, so that the file can be easily accessed.

(8) In the above items (1) to (7), preferably, when the file is searched, a representative file representing the file group is searched as a search range. The representative file may be a file displayed on the file case.

According to this method, the search time can be reduced as compared with the case where all files are searched,
Since similar file names can be prevented from being scattered in the search result, it is easy to find the target file, and the usability can be improved.

(9) In the above (1) to (8), preferably, the file to be opened may be realized by moving the file to be opened to a predetermined area of the display means. For example, a browsing icon is displayed on the display means, and a file to be opened is dragged and dropped onto the browsing room icon to open the file.

According to this method, even a user who is not supposed to open a file by double-clicking can easily open the file.

[0030]

DESCRIPTION OF THE PREFERRED EMBODIMENTS A version management method according to an embodiment of the present invention will be described below with reference to FIGS.

First, a configuration of a version management system for realizing a version management method according to an embodiment of the present invention will be described with reference to FIG.

FIG. 1 is a system configuration diagram of a version management system for realizing a version management method according to one embodiment of the present invention.

The version management system according to the present embodiment includes a CPU 10, an input device 20, a rack database 30, a CD-ROM 40, a main storage device 50, and a display 100. The main storage device 50 stores a rack management program 500. For details of the rack management program 500,
This will be described later with reference to FIG. Rack management program 500
Are a case display program 600, a new file case creation program 800, a latest version file addition program 1000, a file open program 1200, and a case file transfer program 1.
400 and the latest access file display program 150
0, a file update management program 1700, and a file search program 2000. For details of each program, see FIGS. 6, 8, 10, and 1.
2, FIG. 14, FIG. 15, FIG. 17, and FIG.

An example of the display screen is displayed on the display 100. The rack 110 is displayed on the display 100 from the center to the left. The rack 110 is used to organize and manage a plurality of files. On the right side of the rack 110, a tool group including a reading room 120, a warehouse 130, a rack storage room 140, and a case storage room 150 is displayed.
Each tool is used for file management, and details thereof will be described later.

Next, the configuration inside the rack 110 will be described. The rack 110 simulates a catalog rack in the real world. In the upper part of the rack 110, a rack name 111 indicating the name of the rack is displayed. In the illustrated example, "catalogs" is displayed as the rack name 111, indicating that the rack 110 is used for organizing the files of the catalogs. As will be described later with reference to FIG. 2 or FIG. 3, a plurality of racks 110 are prepared for organizing files other than catalogs.

Further, in the rack 110, file cases 112A, 112B, 112C, 112D are displayed. Each file case 112A, 112B, 1
12C and 112D are the case doors 113A and 113A, respectively.
13B, 113C, 113D and case knob 114A,
114B, 114C and 114D are provided. Each file case 112A, 112B, 112C, 112D stores a series of files.

Each case knob 114A, 114B, 11
4C and 114D have file case names 115A, 115B and 11 indicating the names of the files to be stored, respectively.
5C and 115D are pasted. In the illustrated example, "Hitachi catalog" is displayed as the file case name 115A, indicating that the name of the file stored in the file case 112A is "Hitachi catalog".
Note that this file case name may be used as the representative image.
In this case, as shown in FIG.
The display of 6A to 6D may be omitted. At this time, 115A
When ~ D is specified, the files 115A-D are executed. To execute a back number or the like other than 115A to 115D, the following may be performed. When 115A to 115D are instructed in a manner different from the instruction to execute themselves, an image (icon) corresponding to the back number is displayed, and the back number corresponding to the displayed image is executed. It may be.

The case doors 113A, 113B, 113C,
113D, each file case 112A, 1
Of the files stored in 12B, 112C, 112D, the latest files 116A, 116B, 116C, 11
6D is stored. In the illustrated example, the case door 113 is used.
A indicates that “Hitachi Catalog Vol. 5” which is the latest file in “Hitachi Catalog” is stored. Latest files 116A, 116B, 116
C and 116D are displayed as reduced figures on the cover of the file. As a result, the contents of the file can be understood at a glance. In this embodiment, the latest files 116A to 116D are used as representative images. Thus 11
When 6A to 6D are the representative images, the display of 115A to 115D may be omitted as shown in FIG. Further, in order to execute a back number or the like, the following may be performed. When an instruction is given to 116A to 116D in a manner different from the instruction to execute the latest file itself, an image (icon) corresponding to the back number is displayed, and the back number corresponding to the displayed image is executed. You may do so.

The representative images are represented by 115A-D and 116D.
A to D may be both.

Files with back numbers other than the latest file are file cases 112A, 112B, 112
C, 112D. That is, the latest files are stored in the case doors 113A, 113B, 113C and 113D on the file cases 112A, 112B, 112C and 112D.
A, 112B, 112C, and 112D contain back number files.

Case knobs 114A, 114B, 114
C and 114D are file cases 112A and 112D, respectively.
It is used to open 112B, 112C, 112D and view the back number file stored therein. Case knobs 114A, 114B, 114C,
By dragging 114D with the mouse and scrolling upward, the file cases 112A, 112B,
112C and 112D open. The file case 112D of “Gift K” shows the opened state, and the case knob 114D is scrolled upward, and the back numbers “1995” and “1994” other than the latest file “1996” are displayed. "Is stored.

In the state shown in FIG. 1, four file cases 112A, 1 are contained in one rack 110.
Although 12B, 112C, and 112D are illustrated, in practice, as described in FIG.
0 has six file cases. Rack 110
A reading room 120, a warehouse 130, a rack storage room 140, and a case storage room 15
0 can normally display six file cases by displaying as a small icon in the lower right corner on the display screen.

Although the CD-ROM 40 is often used as a medium for a catalog file, it is connected to the present system, but is not always necessary for realizing the present invention.

Many electronic publications, such as catalogs and magazines, access only the latest issue, and back numbers increase without knowing them, and in many cases, necessary items are not apparent at a glance. In addition, the organization is cumbersome. On the other hand, in the present embodiment, a series of files are stored in the file case in the rack, which facilitates organization.

Since the latest file in the series of files is placed on the case door above the file case as a representative of the file group, it is easy to confirm the contents of the files. File case names 115A, 115B, 115C, 115D indicating file names
In this case, although the type of the file stored in each file case is clear, it is not possible to intuitively check the contents of the file because of its lack of specificity. On the other hand, displaying the latest file on the file case improves the visibility of the file.

Since a plurality of file cases are displayed in the rack, the list of files arranged in the rack is improved.

The back numbers in a series of files are:
Although the file is stored in the file case, the contents of the stored file can be easily checked by scrolling the case knob.

For storing in a file case, the file name 32 and the version name 33 of the file may be recognized and stored in a file case having the same file name. This processing may be recognized on the device side when the data is stored in the rack database 30, or a human may input a file name and a version name. When the file is an electronic publication, the apparatus may recognize the publication name described on the cover or the like as the file name.

If a file having the same file name is not stored in the rack database 30, a new file case may be created according to the flowchart shown in FIG. If the same file name and the same version name exist in the rack database 30,
Processing not stored in the rack database 30 may be performed. The processing not to be stored includes, for example, giving a warning to the user that the same file already exists.

Next, a display example of a plurality of racks on the display 100 will be described with reference to FIGS.

FIG. 2 is an explanatory diagram of a first display example of a rack on a display in a version control system for realizing a version control method according to an embodiment of the present invention, and FIG. 3 is a view of the second display example. FIG.

At home, various types of personal computers can be used, such as subscribing to catalogs and magazines, organizing documents, organizing and appreciating electronic photographs taken by games, digital cameras, and creating new year's cards. For this reason, it is convenient if files can be grouped and classified according to use. Therefore, a plurality of racks can be used, files grouped in the racks are put together, and a group name can be given to the racks.

In FIG. 1, the CPU 10, the input device 20, the rack database 30, the CD-ROM device 40, the main storage device 50, and the display 100 are described as one body, but the following structure may be adopted. As described above, the components may be arranged at physically separated positions and connected through a network. For example, as shown in FIG. 24, the rack database 30 may have a different configuration (managed by a different person than the user of the version control system) and a computer 101 having another configuration may be connected via a network. At this time, it may be possible to connect to a plurality of rack databases. Further, in this case, as shown in FIG. 25, a plurality of computers 101 may be connected to the rack database 30. Also in this case, it may be possible to connect to a plurality of rack databases.

In FIG. 1, the rack management program is stored in the main storage device 50.
It may be stored in a storage medium such as a ROM, a hard disk, and a DVD. Further, the rack management program 50 may be distributed through a network.

In the example shown in FIG. 2, a plurality of racks are displayed in an overlapping manner. That is, a plurality of racks 110, 110A, 110B, 110
C is superimposed and displayed. Racks 110, 110A, 11
In the upper part of 0B and 110C, rack names 111, 111A, 111B and 111C indicating the names of the racks are displayed. In the illustrated example, the rack names 111, 111A,
“Catalogs”, “documents”, “games”, and “album” are displayed as 111B and 111C, respectively, and the rack 110 organizes the catalogs, documents, games, and album files. It is used for the purpose. In the illustrated example, the racks 110 of catalogs are displayed on the front, but an arbitrary rack can be displayed on the front by clicking the rack names 111, 111A, 111B, and 111C.

Further, in the rack 110, six file cases 112A, 112B, 112C, 112
D, 112E and 112F are displayed. The file case 112F is an empty file case in which nothing is currently stored.

In the example shown in FIG. 3, a plurality of racks are displayed side by side. That is, a plurality of racks 110, 110A, 110B, 110
C is superimposed and displayed. Racks 110, 110A, 11
In the upper part of 0B and 110C, rack names 111, 111A, 111B and 111C indicating the names of the racks are displayed.

When one file case is to be displayed in a large size, the display format shown in FIG. 2 is used, and when it is desired to increase the number of file cases that can be displayed, the display format shown in FIG. 3 is used.

Next, the data structure of the rack database 30 will be described with reference to FIG.

FIG. 4 is an explanatory diagram of the data structure of the rack database in the version management system for implementing the version management method according to one embodiment of the present invention.

The rack database 30 corresponds to the rack display example shown in FIG. 1 or FIG. 2, and includes a rack name 31, a file name 32, a version name 33, and a description column 3.
4, link destination file name 35.

The rack name 31 has a plurality of file names 32. For example, the rack name 31 of “catalogs” has a plurality of file names 32 such as “Hitachi catalog” and “BB clothing”. The file name 32 is displayed on the display 100 as the file case name 112 shown in FIG.

The file name 32 includes a plurality of version names 3
Three. For example, the file name 32 of “Hitachi catalog” includes “Vol.5”, “Vol.3”, “Vol.
l. 4 "," Vol. 2 ", and" Vol. 1 ". Of a plurality of version names 33 in the same file name 32, the first file is the version name of the latest file, and the next file has the latest usage date among files having the same file name other than the latest file. These are new files, and the next file is similarly repeated in order, like the second newest file. In the illustrated example, “Vol. 5” is the latest file, “Vol. 3” is the most recently used file, and “Vol. 4” is the next used file. ing.

The explanation column 34 is explanation data of the contents of the file. The description field 34 is used to specify the difference between the contents of files having different versions, or to be used as a title of a magazine. “Add dishwasher” in the explanation column 34 is an example of a magazine heading, and “specification change” is an example of a difference in file contents.

The link destination file name 35 indicates an association between files when a series of files is derived from a series of files. For example, a plurality of files can be created based on a certain document file, but the association between these files cannot be managed by version alone. In the illustrated example, the file name is “Hitachi catalog”, and the link destination file name of the file whose version name is “Vol. 3” is “Hitachi catalog 2”. This indicates that a series of files having the file name “Hitachi Catalog 2” has been derived from the Hitachi Catalog “Vol. 3”.

Next, the processing contents of the rack management program 500 shown in FIG. 1 will be described with reference to FIG.

FIG. 5 is a flowchart showing the processing contents of the rack management program used in the version management method according to one embodiment of the present invention.

At step 510, the rack management program 111 is started.

Then, in step 520, the CPU
10 displays the rack 110 on the display 100 with reference to the rack database 30.

Thereafter, in step 530, the process waits for an event to occur according to a user operation from the input device 20.

Next, at step 540, it is determined whether or not the event that has occurred is an end event.
In the case of an end event, in step 560,
Terminate the program.

If the event is other than end, step 5
At 50, programs 600, 800, 1000, 1200, 1400, and 15 corresponding to each event
Branch to 00, 1700, 2000. The processing of each program will be described later.

Next, the processing content of the in-case display program 600 shown in FIG. 1 will be described with reference to FIGS.

FIG. 6 is a flowchart showing the processing contents of the in-case display program used in the version management method according to one embodiment of the present invention. FIG. 7 is a flowchart showing the processing contents in the case used in the version management method according to one embodiment of the present invention. FIG. 11 is an explanatory diagram of a display of a file case for explaining processing contents of a display program.

As shown in FIG. 7A, when the user clicks the case knob 114 of the file case 112 with the mouse, in step 610, the CPU 10
The in-case display program 600 is started.

After starting the in-case display program 600,
When the mouse is moved up, at step 620,
As shown in FIG. 7B, an animation is displayed in which the case knob 114 is pulled up. Thereby,
The case door 113 opens.

Next, at step 630, the CPU 1
0 reads out the names of the files recorded in the case and the order of stacking with reference to the rack database 30, and displays the order in the file case 112 as shown in FIG. 7B. . File case 112
, A file group 117 of back numbers is displayed. When the file case 112 shown in FIG. 7A is closed, the latest file 116 is displayed as a reduced figure on the cover, but when the file case 112 shown in FIG. The version name is displayed. Here, when the file case is open, only the version name may be displayed.

When the number of files in the file group 117 of the back number increases, not all the files can be displayed in the file case 112 at one time.
As shown in (C), the scroll bar 118 is displayed, and by moving the scroll bar, the files of the file group 117 of the back number can be sequentially displayed.

Finally, when the file display in step 630 is completed, in step 640, the process returns to the rack management program 500 shown in FIG.

Next, the processing contents of the new file case creation program 800 shown in FIG. 1 will be described using FIG. 8 and FIG.

FIG. 8 is a flowchart showing the processing contents of the new file case creation program used in the version management method according to one embodiment of the present invention.
FIG. 7 is an explanatory diagram of a window display for explaining processing contents of a new file case creation program used in the version management method according to the embodiment of the present invention.

Although the rack can be used as a file management system dedicated to a specific computer, it is used in combination with a window system which is currently mainstream in personal computers. For example, if you install a new catalog on your computer as an application,
As shown in FIG. 9A, a new window W20 is created on the display 100, and the window W2 is created.
0, an icon 160 of a new file is displayed.
In the illustrated example, an icon 160 of a new file of “H & H catalog” is displayed. The user can view the “H & H catalog” by clicking this icon 160.

On the other hand, in order to create an unused file case 112F on the rack window W10, the mouse is clicked on the case accommodating room 150 shown in FIG. The file case created in the case housing room 150 is dragged with the mouse, and the rack 110 of the rack window W10 is dragged.
Can be placed on top.

After completing the above preparation processing, the icon 160 of the new file is moved to the rack window W10 with the mouse.
At step 810, and place it on the unused file case 112F.
Starts the new file case display program 800.

Next, at step 820, the CPU 1
0 automatically creates a cover icon for the file and displays it on an unused file case on the rack. That is, CP
If the file to be registered has a cover, U10 creates a cover icon using a graphic obtained by reducing the cover of the latest file. If the file to be registered does not have a cover, a figure representing the file and characters or figures at the beginning of the file are cut out and reduced to create a cover icon. As shown in FIG. 9C, the created cover icon 116F is displayed on the unused file case 112F.

Next, in step 830, the case knob 114 sets the file name “H & H” as the file case name (label) 115F of the file case 112F.
Display on F.

Next, in step 840, a new file rack is added to the database 30.

Lastly, when the display of the file name in step 840 is completed, in step 850, FIG.
Return to the rack management program 500 shown in FIG.

The unused file case 112F was created by clicking on the case accommodating room 150 shown in FIG. 1 with a mouse. Similarly, the creation of a new rack is shown in FIG. This is performed by clicking the rack storage room 140.

When the racks and cases are no longer needed, the unnecessary racks and cases can be returned by dragging them with the mouse and dropping them into the respective storage rooms 140 and 150.

Furthermore, in the above description, an unused file case is created on the rack, and the icon of the new file is dragged to the rack window with a mouse and placed on the unused file case. When a new file is dropped on the rack, the system may automatically prepare an unused case and register it.

Next, referring to FIGS. 10 and 11, the latest version file adding program 1000 shown in FIG.
The details of the processing will be described.

FIG. 10 is a flowchart showing the processing contents of the latest version file adding program used in the version management method according to one embodiment of the present invention, and FIG. 11 is the flowchart showing the latest contents used in the version management method according to one embodiment of the present invention. FIG. 10 is an explanatory diagram of a file case and a window display for explaining processing contents of a version file addition program.

When the user adds a new version of the file, the CPU 10 activates the latest version file adding program 1000 in step 810.
The addition of a new version file is performed by installing a new file in the case of a commercial catalog or magazine. Further, this is also performed when the file update management program 1700 described later is used to update the file by the user.

At step 1015, the CPU 10
Determines whether the number of files contained in the file case 112 exceeds a predetermined number. In the present embodiment, an upper limit is set for the number of files stored in the file case 112. Then, the file overflowing from the file case is moved to the warehouse. Therefore, in step 1015, the number of files in the file case 112 is checked.

Here, first, a case where the number of files contained in the file case 112 exceeds a predetermined number will be described. As shown in FIG. 11A, it is assumed that the number of files in the file group 117 of the back number has increased in the file case 112, so that the files cannot be accommodated. FIG.
In (A), the maximum number of files is stored in the file case 112, and Vol. 5, V
ol. 3, Vol. 4, Vol. 2, Vol. It is arranged in one.

If it has, at step 1020, a dialog box is displayed to inform the user that the file with the latest access date will be moved to the warehouse. FIG. 11B shows an example of a dialog box displayed on the warehouse movement confirmation window W20. As shown in FIG. 11 (B), the warehouse movement confirmation window W20 displays “Hitachi Catalog Vol.
Are you sure you want to move 1 to the warehouse? Along with three buttons of "move", "cancel", and "move another file".

At step 1025, it is determined whether or not the input from the user is "to move". When the user gives a response to the effect that the file presented by the system is to be moved to the warehouse, a process of adding the new version file after moving the file to the warehouse in step 1045 and thereafter is performed.

At step 1030, it is determined whether or not the input from the user is “moving another file”. If the user replies to move another file,
Proceeding to step 1035, after executing step 1040, a process of adding a new version file after moving the file from step 1045 to the warehouse.

Next, the processing in the case where a reply to move another file is indicated will be described. In step 1035, a dialog box for the user to select another file is displayed. FIG. 11C illustrates an example of the dialog box displayed in the window W30. As shown in FIG. 11C, the window W30 includes “Hitachi Catalog Vol. 5” to “Hitachi Catalog Vo.
l. The creation / update date and use date of each file of "1" are displayed. Therefore, the user selects a file to be moved to the warehouse based on these data.

In step 1040, the process waits for the user to select a file, moves the user-specified file to the warehouse, and performs processing for adding a new version file in step 1045 and thereafter.

Next, the processing after step 1045 will be described. Step 1045 is equivalent to step 10
When the determination in 15 is NO (when the number of files stored in the case does not exceed the specified number)
Is also done.

In step 1045, it is determined whether the file case is displayed in an open state or a closed state. If the file case is closed, the process proceeds to step 1055. However, if the file case is open, the display of the file group of the back number in the file case needs to be changed. Do.

In step 1050, if there is a file to be moved to the warehouse, the file to be moved to the warehouse is deleted from the case, the empty portion is packed, and the file on the case is moved to the top of the file in the case. To display.

Next, in step 1055, the file displayed on the case door above the file case is deleted, and the added new version file is displayed above the file case.

Further, in step 1060, the data inside the rack database 30 is updated.

Lastly, when the update of the rack database in step 1060 is completed, in step 1070, the process returns to the rack management program 500 shown in FIG. Also, if the input from the user is “cancel” in step 1065, the process of adding the new version of the file is stopped, and the process returns to the rack management program 500.

As the number of files in the back number increases, the number of files that are not frequently used also increases, and if all the files are stored in the file case, access to necessary files may be hindered. Therefore, in the present embodiment, when the number of files contained in the file case 112 is limited and a new file is added, the files in the file case 112 are stored in the warehouse 7.
Move to 2. The used file is moved to the top of the file case at any time.

Next, the processing contents of the file open program 1200 shown in FIG. 1 will be described using FIG. 12 and FIG.

FIG. 12 is a flowchart showing the processing contents of the file open program used in the version management method according to one embodiment of the present invention.
FIG. 8 is an explanatory diagram of a file case and a display of a reading room for explaining processing contents of a file open program used in a version management method according to an embodiment of the present invention.

Normally, the operation of opening a file is performed by double-clicking a file icon, but double-clicking is one of the difficult operations for a person who is not used to mouse operation. Therefore, as shown in FIG. 1, a reading room 120 is provided beside the rack 110, and an operation of opening the file by moving the file to the reading room 120 is performed.

As shown in FIG. 13, file 1 to be opened
When the user performs an operation of moving 16 to the reading room 120,
In step 1210, the CPU 10 activates the file open program 1200.

At step 1210, the CPU 10
Sends an "open file" command to the operating system.

Finally, when the command transmission in step 1210 is completed, in step 1220, FIG.
Return to the rack management program 500 shown in FIG.

Next, the processing contents of the in-case file transfer program 1400 and the recently accessed file display program 1500 shown in FIG. 1 will be described with reference to FIGS.

FIG. 14 is a flowchart showing the processing contents of the in-case file transfer program used in the version management method according to one embodiment of the present invention.
FIG. 15 is a flowchart showing the processing contents of a recently accessed file display program used in the version management method according to one embodiment of the present invention. FIG. 10 is an explanatory diagram of a file case and a confirmation window display for explaining processing contents of a recently accessed file display program.

As shown in FIG. 16A, the file case 112 contains the latest file 116 and a file group 117 having a plurality of back numbers. In the back number file group 117, the date and time when the file was used is arranged in chronological order, as described in the description of the rack database 30 in FIG. That is, “Hitachi Catalog” is Vol. 4, Vol.
3, Vol. 2, Vol. The date and time of use is closer to the present.

Here, it is necessary to change the display process of the file between the case where the file stacked at the top is taken out and the case where the file is stacked at the middle of the file, and the file stacking program is executed.

In FIG. 14, when a file in the file case is taken out, in step 1410, C
The PU 10 is a file transfer program 14 within the case.
Start 00.

Next, in step 1420, it is determined whether another file is stacked on the extracted file.

If the files are stacked, in step 1430, the display is changed to a screen display in which the extracted file portions are packed.

Further, in step 1440, the order of the description field 34 and the link destination file name 35 is exchanged with the version name 33 of the rack database 30.

Finally, when the change of the rack database in step 1440 is completed, in step 1450, the process returns to the rack management program 500 shown in FIG.

Next, the processing when the extracted file is closed will be described with reference to FIG.

As shown in FIG. 16A, Vol. File 11 of 3
When the file 117A is closed and put in a rack after the 7A is taken out and used, as in the case where one book is taken out of the books stacked in the case in the real world and loaded on the top. Vol. After using Vol. 3, Vol. 3 is displayed at the top of the file case 112, and Vol.
3, Vol. 4, Vol. 2, Vol. The order is 1.
Further, in the above description, it is assumed that the latest file is always displayed on the case door 113.
It is also conceivable to display the information on the top. Therefore, in this program, a dialog box as shown in FIG. 16B is displayed, and the user is asked which one to display on the case door 113. In this way, by moving the used file to the uppermost position in the file case every time the file is used, the order in which the files are arranged is a measure of the frequency of use.

Next, the processing of the recently accessed file display program 1500 will be described with reference to the flowchart shown in FIG.

When the used file is closed, in step 1510, the CPU 10 activates the recently accessed file display program 1500.

First, in step 1515, it is determined whether or not the used file is the latest version. Step 1 for the latest version of the file
At 520, the latest file used is displayed on the case door. That is, when the latest file 116 is used in the state shown in FIG. 16A, the latest file 116 may be returned to the file case 112 at the original position. Thereafter, in step 1565, the process returns to the rack management program 500 shown in FIG.

If the used file is not the latest file, a dialog box for confirming whether to put the used file in the file case or to put it on the file case is displayed in step 1525. FIG.
6 (B) shows a confirmation window W50 in which a dialog box is displayed in step 1525.
In the dialog box, a message "Have Hitachi Catalog Vol. 3 in the case?"
Display the buttons for "Place in case" and "Place on case".

Next, in step 1530, it is determined whether or not the input from the user is “put on the case”. When “Place on the case” is input, the process proceeds to Step 1535.

If the user selects to put the file on the case, it is determined in step 1535 whether or not the file case is closed. If it is closed, the process proceeds to step 1545. If the case is open, in step 1540, the latest file currently placed on the case door is displayed at the top of the case.

Next, in step 1545, the used file is displayed on the case door. Thereafter, in step 1565, the process returns to the rack management program 500 shown in FIG.

In step 1550, if the user selects “get in case”, step 1555
In, it is determined whether the case is open or closed. If it is closed, proceed to step 1565; if it is open, in step 1560,
Displays the file used at the top of the file case. Thereafter, in step 1565, the process returns to the rack management program 500 shown in FIG.

Next, the processing contents of the file update management program 1700 shown in FIG. 1 will be described using FIG. 17 and FIG.

FIG. 17 is a flowchart showing the processing contents of the file update management program used in the version management method according to one embodiment of the present invention.
FIG. 8 is an explanatory diagram of a file case and a window display for explaining processing contents of a file update management program used in a version management method according to an embodiment of the present invention.

For example, first, “Hitachi Catalog Vol.
3 is modified to create a new file, the newly created file is referred to as Vol. It is difficult to manage version 3 and other files as version differences. Therefore, in the present embodiment, as a file update process, it is recommended to the user to create a new file case for the modified file, the user is confirmed, and the new file case is, for example, “Hitachi Catalog 2”. Is to be created.

When the user performs a file update operation, in step 1710, the CPU 10 activates the file update management program 1700.

At step 1715, a confirmation dialog box for creating a new case is displayed. FIG.
FIG. 8A shows an example of a confirmation dialog box displayed in the case creation confirmation window W60. In the confirmation dialog box, "Hitachi Catalog Vol.
3 (Revision) was created. Are you sure you want to create a new case "Hitachi Catalog 2"? Along with buttons for "create", "cancel" and "rename".

In step 1720, it is determined whether the input from the user is "cancel". If the user inputs a cancel, step 1 is left as it is.
At 755, the rack management program 5 shown in FIG.
Return to 00.

At step 1725, it is determined whether the input from the user is "create". "create"
In step 1730, (revise) is added to the file name and the file is stored in the rack database 30 as a new file. As a result, as shown in FIG. 18B, a file case 112G to which "Hitachi catalog 2" is added is created as the file case name 115G, and the latest file 116G is provided on the case door as Hitachi catalog Vol. 3 (Revision) is displayed.

Further, in step 1735, a link to a new file is created. When the link is created, as shown in FIG. 18C, the file of “Vol. 3” in the file group 117 of the back number stored in the file case 112A of the original file, A link icon 119 is displayed. When this link icon 119 is clicked, "Hitachi catalog 2" which is a file case of the derived file is displayed as shown in FIG. Then, step 1755
Returns to the rack management program 500 shown in FIG.

In step 1740, if the input from the user is a name change, in step 1745,
Displays a dialog box for entering the file location and file name. Although illustration of this dialog box is omitted, a message prompting the user to input a file storage location and a file name is displayed.

Then, in step 1750, the process waits for an input from the user, and returns to step 1715 to proceed with the subsequent processing.

When a new file is created, one file can be created from a plurality of files. In that case, similarly, by linking a plurality of files to one file, the relationship between the files can be maintained.

Although only one link is displayed in the illustrated example, a plurality of links can be established by writing a plurality of link destinations in the link destination file name 35 of the rack database 30. .

Next, detailed information will be described with reference to FIG.

FIG. 19 is an explanatory view of a file case and a window display for explaining detailed information used in the version management method according to one embodiment of the present invention.

When the data structure in the data rack base 30 is as described with reference to FIG. 4, a file whose file name 32 is “Hitachi catalog” and whose version name 33 is “Vol. On the other hand, a description of the content is stored in the description column 34, and a file name of the link destination is stored in the link destination file name 35.

Therefore, in this embodiment, FIG.
As shown in (A), for example, “V” in the file group 117 of the back number in the file case 112A.
ol. Click “3” to display the explanation display window W7
0 is displayed. In the description display window W70, a description of the content of the file stored in the description column 34 is displayed, for example, "add dishwasher". In many cases, files having different versions cannot be distinguished from each other only by the file name and the version name. However, opening each file and checking its contents is a tedious task. By allowing a description of the file contents to be described and allowing the description to be viewed when the file is selected, the identification of the required file is simplified.

[0150] In the explanation display window W70, a detailed information display button B10 is displayed. By clicking the detailed information display button B10, a detailed display window is displayed.

As shown in FIG. 18D, the link icon 119 is clicked to display "Hitachi catalog 2" which is a file case of the derived file, and further click "Hitachi catalog 2". Then, FIG.
As in (A), an explanation display window and a detailed information display button are displayed.

FIG. 19B shows a detailed display window W displayed by clicking a detailed information display button in the description display window for “Hitachi Catalog 2”.
80 shows an example. In the detail display window W80, “Rack name”, “Case name”, “File name”, “Description”, “Creation source file name” is displayed together with “Title display of detailed information of Hitachi Catalog Vol. Is displayed.

To check the file of the creation source from the derived file, it is sufficient to look at the "source file name" in the detailed display window W80. Further, by using the detailed display window W80, editing such as correction of the content of the "description" can be performed. The contents of the edited “description” are stored in the description field 34 of the rack database 30.

Next, the processing contents of the file search program 2000 shown in FIG. 1 will be described using FIG. 20 and FIG.

FIG. 20 is a flowchart showing the processing contents of a file search program used in the version management method according to one embodiment of the present invention. FIG. 21 is a flowchart showing the contents of the file search program used in the version management method according to one embodiment of the present invention. FIG. 10 is an explanatory diagram of a display of a window for explaining the processing contents of FIG.

In the present embodiment, in addition to the general file search function for searching all files, a representative file search function for narrowing down the file search range to representative files is provided. Here, the representative file is a file group composed of files arranged on a plurality of file cases of the rack. In general file search, a series of files with different versions are treated as separate files, so many files with similar names are lined up in the search results, and it takes time and effort to find the target file This is inconvenient because a series of files having different versions cannot be searched collectively. Therefore, by limiting the search range to the representative files, the search time of the system is shortened and the usability of the user is improved as compared with the method of searching all the files.

When the input of the file search is called from the user, in step 2010, the CPU 10 starts the file search program 2000.

In step 2015, a file search window is displayed. FIG. 21 shows a file search window W90 displayed by the process of step 2015.
An example is shown. In the file search window W90, an input column for “file name to be searched” and a setting column for “search range” are provided. In the search range specification field, “all file search” or “representative file search” can be selected, and a rack name, a creation date, and a use date can be set. Further, buttons of “execute” and “close” are displayed at the upper right of the file search window W90.

In step 2020, the user inputs the conditions of the file to be searched, and waits for the user to press the "execute" button or the "close" button. When the “close” button is pressed, the file search window W90 is closed in step 2030, and in step 2035,
The process returns to the rack management program 500 shown in FIG.

If the execution button is pressed in step 2040, it is determined in step 2045 whether the search range is “all files” or “representative file”.

When the representative file is selected, step 2
At 050, the first version of each file name of the rack database 30 shown in FIG. For example, in the example shown in FIG. 4, “Vol.5” in the “Hitachi catalog” and “′” in the “BB clothing”
Files having a version name such as "96 summer" are searched.

When all files are selected, all files are set as search target files. For example, in the example shown in FIG. 4, “Vol.
"Vol.1", "96 summer" in "BB clothing",
All files having version names such as "plan 6" and "plan 5" in "product plan" are to be searched.

Next, in step 2060, a file search is performed on the search target file, and in step 2065, the search result is displayed in the file search window W90. An example of the search result is shown in the file search window W90 shown in FIG. In the illustrated example, a search is made for a representative file having a file name of “catalog”. As a result, "Hitachi Catalog Vol.5" and "H & H Catalog" are hit and displayed.

Thereafter, the flow returns to step 2020 to wait for an input from the next user. When the "close" button is pressed, the file search window W90 is closed in step 2030, and the process returns to the rack management program 500 shown in FIG. 5 in step 2035.

Next, a warehouse according to this embodiment will be described with reference to FIGS.

FIG. 22 is an explanatory view showing a window for explaining a warehouse used in the version management method according to one embodiment of the present invention. FIG. 23 is used in the version management method according to one embodiment of the present invention. It is explanatory drawing of the usage method of a warehouse.

When the warehouse 130 shown in FIG. 1 is clicked, the warehouse 130A is displayed as shown in FIG. Here, the warehouses are provided corresponding to the racks 110, 110A, 110B, 110C shown in FIG. 2, respectively. That is, the warehouse 1 is a warehouse for the “catalog” of the rack 110, and the warehouse 2 is a warehouse for the “document” of the rack 110A. Other than this, "game"
There is also a warehouse for "Album", but illustration is omitted. Here, for example, when "warehouse 1 (catalog)" is clicked, a warehouse 130A of "warehouse 1 (catalog)" is displayed as shown in FIG.

In the warehouse 130A, cardboard boxes are prepared for each file name. A series of files having the same file name are each packed in the same cardboard box. Click on the cardboard box to see a list of the files it contains.

FIG. 22B shows a warehouse detail window W100 displayed when, for example, “Hitachi Catalog” in the warehouse 1 shown in FIG. 22A is clicked. The data in the warehouse 130 is stored and managed in the rack database 30 for each same file name, similarly to the file data. In the illustrated example, “warehouse 1
In the (catalog) warehouse, the “Hitachi Catalog” cardboard boxes contain “Hitachi Catalog Vol. 6, 1995”
"Hitachi Catalog Vol. 1, 1995" is stored.

Next, a method of storing unnecessary files in a warehouse will be described with reference to FIG.

The user drags and drops a file to be stored from the file case 112, for example, the latest file 116 to the warehouse 130. When storing files in a group of files with back numbers in a warehouse, as described with reference to FIG. This is done by: In this manner, it is only necessary to throw the file into the warehouse 130, and the CPU 10 automatically packs the boxes based on the file name and the state in the original rack database.

Further, for a box that is large in size or has not been accessed for a certain period of time, the file can be semi-automatically compressed by asking the user whether the system can compress the file.

As described above, the number of files to be displayed in the file case is determined, and the accessed file is placed at the top of the file case 112.
By moving the old files semi-automatically to the warehouse as new files are added in the file case, it becomes easier to access frequently used files, and the operation is performed semi-automatically, Users spend less time managing files.

As described above, in the present embodiment, a rack for collecting catalogs and the like is used as a metaphor for managing file versions. Since the rack is configured by arranging a plurality of file cases and assigning a series of files having different versions to one file case, file version management becomes easy.

Further, since the latest file is placed at the door of the file case and the old file is placed in the file case, the file version can be handled intuitively, and the burden on the user for version management is increased. Is reduced.

Further, since the reduced image of the cover of the latest file is displayed on the file case, the file listing is improved.

Further, since the files in the file case are stacked in the order of date and time of access, the latest access status can be grasped at a glance.

When the number of files exceeds a certain number, the file with the oldest date and time of use is moved to the warehouse. Access is also easy.

As described above, the user can easily manage the version of the file, and can spend more time for the original purpose of using the personal computer.

[0180]

According to the present invention, file versions can be easily arranged.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram of a version management system that realizes a version management method according to an embodiment of the present invention.

FIG. 2 is an explanatory diagram of a first display example of a rack on a display in a version management system for implementing a version management method according to an embodiment of the present invention;

FIG. 3 is an explanatory diagram of a second display example of a rack on a display in a version management system for implementing a version management method according to an embodiment of the present invention.

FIG. 4 is an explanatory diagram of a data configuration of a rack database in a version management system that implements a version management method according to an embodiment of the present invention.

FIG. 5 is a flowchart showing processing contents of a rack management program used in a version management method according to an embodiment of the present invention.

FIG. 6 is a flowchart showing the processing contents of an in-case display program used in the version management method according to one embodiment of the present invention.

FIG. 7 is an explanatory diagram of a display of a file case for explaining the processing content of the in-case display program used in the version management method according to the embodiment of the present invention;

FIG. 8 is a flowchart showing processing contents of a new file case creation program used in a version management method according to an embodiment of the present invention.

FIG. 9 is an explanatory diagram of a display of a window for explaining processing contents of a new file case creation program used in the version management method according to the embodiment of the present invention;

FIG. 10 is a flowchart showing the processing contents of a latest version file addition program used in the version management method according to one embodiment of the present invention.

FIG. 11 is an explanatory diagram of a file case and a window display for explaining processing contents of a latest version file adding program used in the version management method according to the embodiment of the present invention.

FIG. 12 is a flowchart showing processing contents of a file open program used in a version management method according to an embodiment of the present invention.

FIG. 13 is an explanatory diagram of a file case and a display of a reading room for explaining processing contents of a file open program used in a version management method according to an embodiment of the present invention.

FIG. 14 is a flowchart showing processing contents of a file transfer program in a case used in a version management method according to an embodiment of the present invention.

FIG. 15 is a flowchart showing the processing contents of a recently accessed file display program used in the version management method according to one embodiment of the present invention.

FIG. 16 is an explanatory diagram of a file case and a confirmation window for explaining processing contents of a file open program and a recently accessed file display program used in a version management method according to an embodiment of the present invention.

FIG. 17 is a flowchart showing processing contents of a file update management program used in a version management method according to an embodiment of the present invention.

FIG. 18 is an explanatory diagram of a display of a file case and a window for explaining processing contents of a file update management program used in a version management method according to an embodiment of the present invention.

FIG. 19 is an explanatory diagram of a file case and a window display for describing detailed information used in the version management method according to an embodiment of the present invention.

FIG. 20 is a flowchart showing processing contents of a file search program used in a version management method according to an embodiment of the present invention.

FIG. 21 is an explanatory diagram of a display of a window for explaining processing contents of a file search program used in the version management method according to one embodiment of the present invention;

FIG. 22 is an explanatory diagram of a window display for explaining a warehouse used in the version management method according to the embodiment of the present invention;

FIG. 23 is an explanatory diagram of a method of using a warehouse used in a version management method according to an embodiment of the present invention.

FIG. 24 is a system configuration diagram of a version control system in which a computer and a rack database are connected via a network.

FIG. 25 is a system configuration diagram of a version management system in which a plurality of computers and a rack database are connected via a network.

FIG. 26 is a diagram showing first and second modified examples of display contents of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 ... CPU 20 ... Input device 30 ... Rack database 40 ... CD-ROM device 50 ... Main storage device 100 ... Display 110 ... Rack 111 ... Rack name 112 ... File case 113 ... Case door 114 ... Case knob 115 ... File case name 116 ... latest file 120 ... reading room 130 ... warehouse 140 ... rack storage room 150 ... case storage room

Claims (16)

[Claims] 1. A storage means for storing data of a file group having different versions, a display means, and an arithmetic processing means for performing a process of displaying on the display means using the data stored in the storage means. In a version management method for managing a group of files having different versions using a system, a rack including a plurality of file cases is displayed on the display unit, and each of the plurality of file cases has the same file name. A file having a different version is displayed as being stored. On the file case, a representative image related to the file of the file case and executing a predetermined file when specified by a user is displayed. Version control method characterized by performing. 2. The version management method according to claim 1, wherein the representative image corresponds to one of the files in the file case. 3. The version management method according to claim 1, wherein the representative image corresponds to a different file having the same file name as the file in the file case. Management method. 4. The version management method according to claim 1, wherein the version includes any one of a number, a number of an electronic publication, and a creation date. . 5. A version control device comprising a display device and a processing device, wherein the processing device stores a display area for a number of groups for a plurality of files stored in a storage device and divided into groups. A version management device, provided on a display device, for displaying a representative image related to a group corresponding to the display area and executing a predetermined file in the group when specified by a user. 6. The version management apparatus according to claim 5, wherein the file has a file name and a version name, and the group is a set of the same file names having different versions. Version control device. 7. The version management apparatus according to claim 5, wherein the representative image corresponds to a predetermined file in a corresponding group. 8. The version control apparatus according to claim 7, wherein the file corresponding to the representative image has at least one of the latest file creation, use, and storage in the storage device in each group. Version control device characterized by being data. 9. The version management apparatus according to claim 7, wherein the representative image is a reduced image of the content of a corresponding file. 10. The version control device according to claim 7, wherein when the display area is designated, an image corresponding to a file other than the predetermined file among files of a group corresponding to the display area is displayed. A version control device for displaying in a display area. 11. The version control device according to claim 10, wherein the image corresponding to a file other than the predetermined file displayed in the display area includes at least a date and time of use, a date and time of creation, and a date and time of storage in the storage device. A version control device, wherein the display is arranged and displayed in one new order. 12. The version management apparatus according to claim 10, wherein the number of images corresponding to files other than the predetermined file displayed in the display area is limited to a predetermined number, and the number of images exceeding the predetermined number is limited. A version management device for displaying when another display area is designated. 13. The version control device according to claim 12, wherein the files exceeding the predetermined number are at least one older among the use date and time, the creation date and time, and the storage date and time in the storage device in each group. A version control device which is sequentially selected from a file. 14. The version management apparatus according to claim 7, wherein when searching for the file, a file corresponding to the representative image is set as a search target. 15. The version management device according to claim 7, wherein the file corresponding to the representative image is executed by moving the representative image to a predetermined area. 16. A program readable by a computer and capable of causing the computer to perform the following processing: a plurality of data stored in a storage device and having a data name and a version name; Data is divided into groups having the same data name but different version names as one group, and the display device is provided with display areas for the number of groups, and the display area is associated with each group, and Displaying a representative image for executing a specified file in a group when specified.