CA2252472A1 - A method of and an apparatus for displaying version information and configuration information and a computer-readable recording medium on which a version and configuration information display program is recorded - Google Patents
A method of and an apparatus for displaying version information and configuration information and a computer-readable recording medium on which a version and configuration information display program is recorded Download PDFInfo
- Publication number
- CA2252472A1 CA2252472A1 CA002252472A CA2252472A CA2252472A1 CA 2252472 A1 CA2252472 A1 CA 2252472A1 CA 002252472 A CA002252472 A CA 002252472A CA 2252472 A CA2252472 A CA 2252472A CA 2252472 A1 CA2252472 A1 CA 2252472A1
- Authority
- CA
- Canada
- Prior art keywords
- version
- information
- documents
- configuration information
- constituent elements
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Abstract
Each time a document or a program source is edited, version information including its version name and creation date is stored in a storage. Configuration information of a plurality of documents and program sources is stored in another storage. The version and configuration information is read from the storages such that information of constituent elements of a project such as documents and program sources is placed in a vertical direction and version information of the elements is placed by use of a creation date as a reference in a horizontal direction for a two-dimensional display thereof. With the configuration, there is provided a display method of clearly presenting to the user a display image in which version information is combined with configuration information.
Description
CA 022~2472 1998-11-02 BACKGROUND AND SUMMARY OF THE INVENTION
The present invention relates to a document management system, and in particular, to a method of and an apparatus for displaying document management information as a set of elements including a plurality of documents and a plurality of programs, for example, version information of each element and configuration information of a set thereof and a computer-readable recording medium on which a program for displaying version and configuration information is recorded.
To manage a large volume of documents of a firm in a concentrated manner for efficient use thereof, there has been an increasing need of a document management system in which documents can be stored in a storage to be retrieved and read therefrom. Additionally, for example, to write documents for a large number of manuals and to develop programs, namely, for collaborative job which cannot be achieved by one person but by a plurality of people through a collaborative job, there has been a tendency of effectively utilizing the system above.
In such a collaborative job, in addition to management of versions of respective documents and programs, the persons concerned are required to collabora-tively proceed the job while collaboratively managing the state and condition of writing documents. Consequently, in .. . , .. , , ~ . . .
CA 022~2472 1998-11-02 the document management system employed in the collabora-tive job, there are essentially required a version manage-ment function and a configuration management function.
In this connection, "version management"
indicates management of information items such as a version number of a document or a program source and a creation date of each version such that when a user edits and updates documents and program sources, it is possible to store and to retrieve any version of documents and program sources.
Consequently, a list of version information can be displayed to restore a version of a document at an arbitrary point in the past or to obtain a process of editing operations in the past. Moreover, for an efficient editing operation, it is possible to extract and display differences between the versions.
In addition, "configuration management" means that files or objects in which documents and/or program sources are stored are gathered into sets of related elements for the management thereof. The elements may be constituent elements of documents and programs.
A set of these elements is called a project in some cases. For example, when editing a manual of a product in a file for each chapter, if relationships between the files are managed in the form of configuration information of a project ~product manual", the related files can be gathered into a document when necessary.
Moreover, in a case of development of an CA 022~2472 1998-11-02 application program, when relationships between the program sources and object files of respective modules are managed in the form of configuration information of a project application program", it is possible, for example, to compile related files at a time.
In a document management system having the version and configuration management functions, when the user conducts operation to refer to version information for restoration of versions at an arbitrary point in the past, to know an editing process in the past, and to extract and display differences between versions, it is necessary for the system to present the version information to the user.
Additionally, when a user carries out operation to refer to configuration information to gather related document files into a document and to collect related program sources for compilation thereof, the system is required to present the configuration information to the user.
Furthermore, when the user desires to know information of the editing operation conducted in the past for documents and program sources of a project and informa-tion of relationships between versions of constituent elements, it is necessary to clearly present information in which version information is combined with configuration information. This is a function particularly required in a collaborative job such as a collaborative writing of documents and a collaborative development of programs.
In this situation, version information and CA 022~2472 1998-11-02 configuration information are displayed by use of a tree structure in the conventional document management system or the like as shown in Fig. 5. For example, PVCS Version Manager (http://www.intersolv.co.jp/PVCS/main/Function/
Vm.htm) of INTERSOLV discloses a technology in which program versions are managed to display source names of each program and versions thereof in a tree structure.
In a display of Fig. 5, there is presented a combination of version information shown in Fig. 6 and configuration information shown in Fig. 7. But, Figs. 6 and 7 are not admitted as prior art.
In Fig. 7, 701 indicates a name of a project as an object of management and 702 denotes constituent elements of the project. Configuration information includes a file name 704 and the like corresponding to a constituent element name 703, and the example of Fig. 7 indicates that Project "Product XX Manual" has constituent elements "Contents", "Chapter 1", "Chapter 2", and "Fig.
1." , In Fig. 6, 601 to 604 indicate version informa-tion items respectively corresponding to constituent elements of "Product XX Manual". Each version information includes a version name 605, a creator or writer of the version 606, a creation date thereof 607, etc., and Fig. 6 expresses, for example, that "Contents" include two versions of V1 and V2 (601).
Fig. 5 includes a root node of tree 501 indicat-ing the displayed project. A sub-node 502 thereof denotes CA 022~2472 1998-11-02 a constituent element of the project. Furthermore, a sub-node 503 of the element indicates a list of versions of respective constituent elements.
As above, information in which version informa-tion is combined with configuration information isdisplayed in a tree structure. Consequently, the user can recognize documents and program source names of the pertinent project as well as versions thereof.
However, the method of displaying version information and configuration information in accordance with the conventional document management system is attended with the following problems.
A first problem will be now described.
In the restoration of a document at a point of time in the past in Fig. 5, assume an example of a case in which "Chapter 1" is restored for a point of time of Dec.
4, 1997.
In the conventional display method using the tree structure, there is provided a graphic user interface (GUI) as shown in Fig. 8 to obtain information of a creation date or the like of each version. That is, by pointing an arbitrary constituent element of a document, there is displayed a list of version information thereof.
In Fig. 8, version information 802 is displayed for ~Chapter 1. Namely, it is only necessary to restore the document of V2 by referring to the information.
However, to restore "Contents" for Dec. 4, 1997 on which "Chapter 1" was of V2, there is required a CA 022~2472 1998-11-02 comparison of the creation date by referring to version information of "Contents" in this case. That is, when only the display method of Fig. 5 is used, it cannot be known that which one of the versions of "Contents" was used for each version of "Chapter 1".
As above, in the conventional display method, it is not possible to recognize a relationship in time between constituent elements, i.e., how these mutually related elements were edited. Therefore, it is difficult for the user to conduct operation for the restoration of the elements of a project into documents at a point of time in the past.
Description will now be given of a second problem.
Assume an example of a case in which as a constituent element of a project, there is specified not only a document or a source file but also a particular version name of the element.
This is effective, for example, in a case of management in which when a project has a version and a product manual includes several documents as its constituent elements, a first version of product manual includes the constituent elements of a version and a second version thereof includes the elements of another version.
Fig. 9 is an example in which there is specified, in addition to the configuration information of Fig. 7, a particular version name of the constituent element.
Fig. 9 shows configuration information 901 of CA 022~2472 1998-11-02 first version" and configuration information 903 of llsecond version" of "Product XX Manual". Each information includes a version name (902, 904) for each element in addition to a constituent element name 703 and a file name 704 associated therewith. In short, 901 indicates that first version" of "Product XX Manual" includes V1 of Contents", V1 of "Chapter 1", V2 of "Chapter 2", and V1 of ~Fig. 1" and 903 indicates that "second version" of ~Product XX Manual" includes V2 of "Contents", V4 of "Chapter 1", V2 of "Chapter 2", and V3 of "Fig. 1".
Configuration information of Fig. 9 is displayed in a tree structure, for example, as shown in Fig. 10.
In Fig. 10, a root node of tree 1001 represents a project. A sub-node 1002 thereof indicates a constituent element of the project and a sub-node 1003 of the element denotes a version name corresponding to each element.
However, in the display method above, although it is possible to know a version corresponding to each constituent element, the user cannot obtain, for example, how the version is edited before and/or after a particular point of time.
For example, ~Contents~ of ~first version" of IlProduct XX Manual" is of V1 in the example of Fig. 10.
However, there cannot be attained information of whether or not the Contents are edited thereafter and hence the position or the like of the version of the project cannot be known. That is, there exists a problem that information about versions of constituent elements of a project and CA 022~2472 1998-11-02 historical information of editing of each version from another version cannot be obtained.
It is therefore an object of the present invention, which copes with the problems above, to provide a method of displaying version information and configura-tion information in which information of combination of version information and configuration information is clearly presented to the user such that the user refers to version information of documents and program sources of a project to easily restore versions of all elements of the project at an arbitrary point of time in the past and to easily obtain an editing process of each version in the past.
To achieve the object above, in accordance with one aspect of the present invention, there is provided a version and configuration information display method for use with a document management system including a processor, a storage, and a terminal unit for managing version information of documents, program sources, etc. and configuration information including a plurality of documents, a plurality of program sources, etc., including the steps of storing, each time a document, a program source, and the like is edited, version information includ-ing a version name thereof, a creation date thereof, and the like in the storage; storing configuration information of a project in a set of a plurality of documents, a plurality of program sources, and the like in the storage;
and reading the version information and the configuration CA 022~2472 1998-11-02 information of the project from the storage, placing and displaying information of constituent elements of a project including documents, program sources, and the like on a screen of the terminal unit in a vertical direction, and placing and displaying version information of each of the constituent elements thereon by using the creation date as a reference in a horizontal direction.
Moreover, the display step uses, in place of the creation date, a version of a project as the reference.
Additionally, the display step includes, in place of the step of placing and displaying information of constituent elements of a project including documents, program sources, etc. in a vertical direction, the step of placing and displaying information of constituent elements of a project including documents, program sources, etc. in a tree structure in a vertical direction in accordance with a hierarchical relationship between the constituent elements.
The display includes the step of storing, in the storage, job management information for inspection of a state of writing an entire project and documents as its elements and a state of developing program sources. The display step reads the job management information from the storage and places and displays the job management informa-tion on the screen of the terminal unit.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a diagram showing constitution of a .~ . . .
CA 022~2472 1998-11-02 first embodiment in accordance with the present invention;
Fig. 2 is a flowchart showing a processing procedure of a version management program in the first embodiment in accordance with the present invention;
Fig. 3 is a flowchart showing a processing procedure of a configuration management program in the first embodiment in accordance with the present invention;
Fig. 4 is a flowchart showing a processing procedure to two-dimensionally display version information and configuration information in the first embodiment in accordance with the present invention;
Fig. 5 is a diagram showing a first display example of version information and configuration informa-tion in a conventional display method;
Fig. 6 is a diagram showing an example of version information to explain an embodiment in accordance with the present invention;
Fig. 7 is a diagram showing an example of configuration information to explain a first embodiment in accordance with the present invention;
Fig. 8 is a diagram showing a state of referring to version information in a conventional display method;
Fig. 9 is a diagram showing an example of configuration'information to explain a second embodiment in accordance with the present invention;
Fig. 10 is a diagram showing a second display example of version information and configuration informa-tion in a conventional display method;
CA 022~2472 1998-11-02 Fig. 11 is a diagram showing a display example of version information and configuration information in the first embodiment in accordance with the present invention;
Fig. 12 is a diagram showing a first display process to explain a display method of version information and configuration information in the first embodiment in accordance with the present invention;
Fig. 13 is a diagram showing a second display process to explain a display method of version information and configuration information in the first embodiment in accordance with the present invention;
Fig. 14 is a flowchart showing a processing procedure to two-dimensionally display version information and configuration information in the second embodiment in accordance with the present invention;
Fig. 15 is a diagram showing a first display example of version information and configuration informa-tion in the second embodiment in accordance with the present invention;
Fig. 16 is a diagram showing a second display example of version information and configuration informa-tion in the second embodiment in accordance with the present invention;
Fig. 17 is a diagram showing a third display example of version information and configuration informa-tion in the second embodiment in accordance with the present invention;
Fig. 18 is a diagram showing a fourth display CA 022~2472 1998-11-02 example of version information and configuration informa-tion in the second embodiment in accordance with the present invention;
Fig. 19 is a diagram showing constitution of a third embodiment in accordance with the present invention;
Fig. 20 is a diagram showing an example of configuration information and job management information to explain the third embodiment in accordance with the present invention;
Fig. 21 is a diagram showing a display example of version information and configuration information in the third embodiment in accordance with the present invention;
Fig. 22 is a diagram showing a display example of version information to explain a fourth embodiment in accordance with the present invention;
Fig. 23 is a diagram showing an example of configuration information to explain the fourth embodiment in accordance with the present invention; and Fig. 24 is a diagram showing a display example of version information and configuration information of the fourth embodiment in accordance with the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
Next, description will be given of an embodiment in accordance with the present invention.
Fig. 1 shows constitution of a first embodiment of the present invention.
As can be seen from the diagram, the embodiment CA 022~2472 1998-11-02 includes a CPU 101, a terminal unit 102, a secondary storage 103, a storage medium 104 for storing programs thereon, and a processing program 1 for conducting version management and configuration management and displaying information about versions and configurations.
Additionally, the processing program 1 includes a version management program 105 to store, each time a document or a program source is edited, version information including a version name and a creation date thereof in the secondary storage 103, a configuration management program 106 to store project configuration information 103b in the secondary storage 103, the information 103b including a set of a plurality of documents and a plurality of program sources, and a version/configuration information two-dimensional (2D) display program 107 to place or toarrange, when the version information 103a and the configuration information 103b are read from the storage 103 for the display thereof, information of constituent elements such as documents and program sources of a project in a vertical direction of a two-dimensional plane and version information of the elements in a horizontal direction in accordance with the creation date to thereby display these items in the two-dimensional manner.
A specific processing procedure of this embodi-ment will be described by referring to the flowcharts ofFigs. 2 to 4. Moreover, the version information of Fig. 6 and the configuration information of Fig. 7 are used in this example of processing.
CA 022~2472 l998-ll-02 However, in the embodiment, it is assumed that the version and configuration information of Figs. 6 and 7 is two-dimensionally displayed as shown in Fig. 11.
Fig. 2 shows a processing procedure of the version management program 105.
In step 201, documents and program sources are edited.
In step 202, when the edited documents and program sources are to be stored with new versions created, the program 105 stores version information including a version name, a creator, and a creation date in the secondary storage 103.
In Fig. 6, 601 indicates version information in which "Table of contents~ is edited to be stored as V1 (table of contents of version 1) and then the table of contents of version V1 is further edited to be stored as V2 (table of contents of version 2).
Fig. 3 shows a processing procedure of the configuration management program 106. This is executed independently of the processing procedure of steps 201 and 202.
In step 301, configuration information is created by the program 106. Namely, there is produced configura-tion information including a name of a project and an element name and a file name of each constituent element.
To create configuration information, the user may specify the project name and its elements via GUI or the like. Alternatively, the information may be automatically CA 022~2472 1998-11-02 created from information of the table of contents described in documents.
In step 302, the created information is stored in the secondary storage 103 by the program 106.
Fig. 7 shows the created configuration informa-tion including a project name of ~Product XX Manual~ and element names and file names for its elements "Contents", ~Chapter 1", "Chapter 2", and Fig. 1.
Fig. 4 shows a processing procedure of the version/configuration 2D display program 107 to display the version and configuration information stored in steps 202 and 302.
In step 401, the information stored in step 302 is read from the storage 103a. There is read the informa-tion of Fig. 7.
In step 402, as a reference for placement orplacement in the vertical direction, the element names are placed and displayed in the vertical direction.
For example, the names of Fig. 7 are displayed on the left side of a display area as shown in Fig. 12.
In step 403, version information corresponding to the elements of information read in step 401 is read from the secondary storage 103b. There is attained version information indicated as 601 to 604.
In step 404, according to the creation date of version information read in step 403, a reference for placement in the horizontal direction to display an item.
This processing is carried out, for example, as CA 022~2472 1998-11-02 follows. When the horizontal placement reference is set to the version creation date, the creation date of each version is acquired from the version information. From the information 601 to 604, the horizontal placement reference is determined as 12/2, 12/3, 12/5, 12/8, and 12/9, which are presented on the upper side of the display area as shown in Fig. 13.
In step 405, version names are placed and displayed at associated positions in the horizontal and vertical directions.
For example, "Contents" of ~V1~ is vertically placed and displayed at a position of ~'Contents" of the element name and is horizontally placed and displayed at a position of ~12/2~ for the creation day. Additionally, ~Contents" of "V2" is placed and displayed at a position of "12/5".
Through the steps above, the version information and the configuration information can be two-dimensionally displayed as shown in Fig. 11.
Thanks to usage of the display method of this kind, the user can easily recognize how the constituent elements such as documents and program sources of a project are edited and how the elements are related to each other with respect to time. Therefore, for any element of the project, the user can easily restore a version thereof at an arbitrary point of time in the past, and the editing process in the past can be easily attained.
A second embodiment of the present invention will CA 022~2472 1998-11-02 be next described.
The second embodiment is an example of a case in which not only documents and source file names but also particular version names of elements are specified as constituent elements of a project. This differs from the first embodiment in the processing of the version/
configuration information 2D display program 107, i.e., the other processing is kept unchanged.
Like the first embodiment, this embodiment includes a CPU 101, a terminal unit 102, a secondary storage 103, a storage medium on which programs are stored, and a processing program 1 to conduct version management and configuration management so as to display information thereof. Moreover, the program 1 includes a version management program 105 to store, each time a document or a program source is edited, version information including a version name and a creation date in the secondary storage 103, a configuration management program 106 to store project configuration information 103b in the secondary storage 103, the information 103b including a set of a plurality of documents and a plurality of program sources, and a version/configuration information 2D display program 107 to place, when the version information 103a and the configuration information 103b are read from the storage for the display thereof, information of constituent elements such as documents and program sources of a project in a vertical direction and version information of the elements in a horizontal direction in accordance with the CA 022~2472 1998-11-02 version of the project to thereby display these items in the two-dimensional manner.
A concrete processing procedure of the program 107 of the embodiment will be described by referring to the flowchart of Fig. 14. Additionally, the version informa-tion of Fig. 6 and the configuration information of Fig. 9 are used in this processing example.
The processing procedure of the programs 105 and 106 including steps 201 and 202 and steps 301 and 302 are kept unchanged.
Fig. 14 shows a processing procedure of the program 107 to display the version and configuration information stored in steps 202 and 302.
In step 1401, from the configuration information stored in the secondary storage 103a in step 302, there is obtained configuration information of each version of the project. Information items 901 and 903 of Fig. 9 are read therefrom.
In step 1402, constituent element names of a plurality of projects are placed and displayed in a vertical direction.
In step 1403, version information corresponding to elements of configuration information read in step 1401 are read from the storage 103b. Information items 601 to 604 of Fig. 6 are read therefrom.
In step 1404, beginning from the version of the oldest creation data, the constituent elements of projects are placed and displayed with project names in the CA 022~2472 1998-11-02 horizontal direction.
In step 1405, version names are placed and displayed at corresponding positions in the horizontal and vertical directions. For a version other than the constituent elements of the projects, the version name is placed and displayed between those of the elements.
Through the steps above, the version information and the configuration information can be two-dimensionally displayed as shown in Fig. 15.
Thanks to usage of the display method of this kind, since the user can easily obtain information such as a relationship between versions of a project and constituent elements thereof, it is possible to easily recognize information, for example, how the editing is conducted through versions of projects. Consequently, the editing of projects can be efficiently achieved.
Furthermore, in place of the display method of Fig. 15, there may be used a method shown in Fig. 16 in which the project version is added to the display of Fig.
11.
In Fig. 16, the creation date of constituent elements is used as a reference for placement in the horizontal direction, and versions specified as elements of projects are connected to each other via a line. In addition to the linkage, the versions specified as elements of projects each may be, for example, enclosed with a line to display the enclosed areas in different colors.
Thanks to the display of Fig. 16, the user can CA 022~2472 l998-ll-02 recognize how the constituent elements such as documents and program sources of projects are edited and how the elements are related to each other with respect to time.
Moreover, the user can attain information such as a relationship between a version of a project and the constituent elements of the version.
Furthermore, Fig. 17 shows an example in which configuration information is placed in a tree structure in accordance with a hierarchical relationship between the constituent elements so as to two-dimensionally display version information of the elements in the horizontal direction.
In this example, "Fig 1" is used in "Chapter 2", namely, there exists a hierarchical relationship that "Fig.
1" is a sub-element of "Chapter 2". In accordance with the usage of this display method, there can be obtained a hierarchical relationship between the constituent elements and a relationship therebetween with respect to time. For example, it can be recognized that "Chapter 2" iS updated at a position indicated as "12/8" and "Fig. 1" used in the update operation is updated at " 12/9".
Additionally, in place of the display method of Fig. 17, there may be used a method in which a certain constituent element is pointed as shown in Fig. 18 to 2 5 obtain the two-dimensional display of configuration information and version information for the sub-elements thereof.
This is effective when there exist a large number CA 022~2472 1998-11-02 of constituent elements and the display of configuration information in the tree structure is vertically elongated and the overall display cannot be viewed in one screen image at a time.
Description will be given of a third embodiment of the present invention.
In relation to the third embodiment, description will be given of a method of displaying version information and configuration information in a case of, for example, collaborative writing of documents and/or collaborative development of programs in which a configuration management function of projects including sets of documents and program sources is collaboratively operated with a job management function to check or to inspect a state of writing of each document and a state of development of each program source.
Fig. 19 shows constitution of the third embodi-ment of the present invention.
As shown in the diagram, the embodiment includes, in addition to the configuration (Fig. 1) of the first embodiment, a job management program 1901 to store job management information 103c in a storage for the checking or inspection of the writing state of documents and the state of development of program sources, the documents and 2 5 program sources being constituent elements of the entire project. When displaying version information and configuration information by the version/configuration information 2D display program 107 in this configuration, CA 022~2472 1998-11-02 the job management information 103c is read from the storage and is then displayed in combination with the version and configuration information.
The job management information includes, for example, information of a deadline by which such an element of project as a document or a program source is to be submitted and information of an event for each element that the editing thereof is completed for the project.
Fig. 20 shows an example of configuration information and job management information for a project.
In Fig. 20, there are shown, in addition to the project name as configuration information, job management information including deadline information 2002 and an editing mode of element 2003. The editing mode of element is information which indicates that the editing of element is being conducted or ~Product XX Manual - Version 2~ has been determined. Items of job management information are specified by the user and is stored in a storage by the job management program 1901.
Fig. 21 shows an example in which the job manage-ment information is displayed by the display program 107.
Deadline information 2102 is displayed along the creation date in the hori~ontal direction and the editing mode 2103 is displayed, for example, by changing the display format of version information with different colors.
As above, since the job management information is displayed in combination with the two-dimensional display of version information and configuration information, the CA 022~2472 l998-ll-02 user can easily recognize the state of writing as well as the state of development.
Description will be given of a fourth embodiment of the present invention.
The fourth embodiment is an example of display in, for example, a program development support system for management of program versions and configurations in which configuration information of programs including several sources and version information of the program sources are displayed.
In contrast with the first to third embodiments in which a project includes several documents and the constituent elements are documents, program sources are assigned as the constituent elements of programs to be developed by the project in the fourth embodiment.
The configuration and the processing procedure of this embodiment are the same as those of the first to fourth embodiments.
Fig. 22 shows an example of version information of program sources and Fig. 23 shows an example of configuration information.
In Fig. 23, 2301 indicates a program name as an object of management and 2302 denotes a program source of the program.
2 5 Configuration information includes a program source name 2303, a file name corresponding thereto 2304, and the like. The example of Fig. 23 means that "ABC
program" includes program sources "main.cpp", ~output.cpp~, CA 022~2472 l998-ll-02 "prog.h", and "output.h".
In Fig. 22, 2201 to 2204 indicate version information respectively corresponding to constituent elements of "ABC program" shown in Fig. 23. Version information includes a version name 2205, a person-in-charge of program of the version 2206, a creation date 2207, etc. Fig. 22 indicates, for example, that "main.cpp"
has four versions Vl to V4 t2201).
Fig. 24 shows an example in which version 10 information of Fig. 22 and configuration information of Fig. 23 are two-dimensionally displayed in accordance with the procedure of steps 201 and 202, steps 301 and 302, and steps 401 to 405.
Utilizing the display method above, the user can 15 easily recognize how the program sources of the program have been edited and how the sources are related to each other.
For example, the user can easily recognize a relationship between a particular version of cpp file and a 20 header file of a particular version. Therefore, the user can easily select and compile associated sources to restore the program at an arbitrary point of time in the past.
Moreover, the process of program development can be easily known.
Similarly, version information of program sources and program configuration information can be two-dimensionally displayed in accordance with a program version by use of the processing procedure of the second .
CA 022~2472 1998-11-02 embodiment. Therefore, the user can recognize the versions of source programs for each version of the program and the modification in the past of sources for the program of a particular version.
Additionally, job management information such as the deadline of program development can also be displayed in accordance with the configuration and the processing procedure of the third embodiment. This makes it possible to easily obtain the program development state.
In accordance with the version information and configuration information display method of the present invention, the version information and the configuration information can be two-dimensionally displayed in which constituent elements of the project are vertically displayed and versions of the elements are displayed by using the creation date thereof as a reference in the horizontal direction.
With this configuration, it can be easily known how the constituent elements of project such as documents and program sources have been edited and how the elements are associated with each other with respect to time.
Accordingly, it is possible to easily restore a version of any element of the project at an arbitrary point of time in the past, and the editing process thereof can be easily known. This increases the efficiency of the collaborative editing job and the like.
When there is employed the two-dimensional display method in which constituent elements of a project CA 022~2472 1998-11-02 is vertically displayed and versions thereof are placed by use of the version of project as a reference in the horizontal direction, the user can easily obtain informa-tion, for example, a relationship between a particular version of project and constituent elements of particular versions. Therefore, information about the editing process in the past of projects can be known and hence the effi-ciency of project editing operation is increased.
Additionally, when there is adopted a two-dimensional display method in which constituent elements of a project are vertically placed in a tree structure in accordance with a hierarchical relationship between the elements and version information of the elements is placed in the horizontal direction, the user can recognize, for example, a relationship between versions of an element and sub-elements thereof. Consequently, it is possible to increase the efficiency when editing documents and the like having a hierarchical relationship.
Furthermore, when there is displayed job manage-ment information to check the writing state of the project and documents as constituent elements thereof and the development state of program sources together with the version information and the configuration information in a two-dimensional fashion, the user can easily obtain information of the editing process in the past of the elements of the project and the writing state and the development state. This consequently increases the efficiency of the job management in, for example, the CA 022~2472 1998-11-02 collaborative editing job.
While the present invention has been described with reference to the particular illustrative embodiments, it is not to be restricted by those embodiments but only by the appended claims. It is to be appreciated that those skilled in the art can change or modify the embodiments without departing from the scope and spirit of the present invention.
The present invention relates to a document management system, and in particular, to a method of and an apparatus for displaying document management information as a set of elements including a plurality of documents and a plurality of programs, for example, version information of each element and configuration information of a set thereof and a computer-readable recording medium on which a program for displaying version and configuration information is recorded.
To manage a large volume of documents of a firm in a concentrated manner for efficient use thereof, there has been an increasing need of a document management system in which documents can be stored in a storage to be retrieved and read therefrom. Additionally, for example, to write documents for a large number of manuals and to develop programs, namely, for collaborative job which cannot be achieved by one person but by a plurality of people through a collaborative job, there has been a tendency of effectively utilizing the system above.
In such a collaborative job, in addition to management of versions of respective documents and programs, the persons concerned are required to collabora-tively proceed the job while collaboratively managing the state and condition of writing documents. Consequently, in .. . , .. , , ~ . . .
CA 022~2472 1998-11-02 the document management system employed in the collabora-tive job, there are essentially required a version manage-ment function and a configuration management function.
In this connection, "version management"
indicates management of information items such as a version number of a document or a program source and a creation date of each version such that when a user edits and updates documents and program sources, it is possible to store and to retrieve any version of documents and program sources.
Consequently, a list of version information can be displayed to restore a version of a document at an arbitrary point in the past or to obtain a process of editing operations in the past. Moreover, for an efficient editing operation, it is possible to extract and display differences between the versions.
In addition, "configuration management" means that files or objects in which documents and/or program sources are stored are gathered into sets of related elements for the management thereof. The elements may be constituent elements of documents and programs.
A set of these elements is called a project in some cases. For example, when editing a manual of a product in a file for each chapter, if relationships between the files are managed in the form of configuration information of a project ~product manual", the related files can be gathered into a document when necessary.
Moreover, in a case of development of an CA 022~2472 1998-11-02 application program, when relationships between the program sources and object files of respective modules are managed in the form of configuration information of a project application program", it is possible, for example, to compile related files at a time.
In a document management system having the version and configuration management functions, when the user conducts operation to refer to version information for restoration of versions at an arbitrary point in the past, to know an editing process in the past, and to extract and display differences between versions, it is necessary for the system to present the version information to the user.
Additionally, when a user carries out operation to refer to configuration information to gather related document files into a document and to collect related program sources for compilation thereof, the system is required to present the configuration information to the user.
Furthermore, when the user desires to know information of the editing operation conducted in the past for documents and program sources of a project and informa-tion of relationships between versions of constituent elements, it is necessary to clearly present information in which version information is combined with configuration information. This is a function particularly required in a collaborative job such as a collaborative writing of documents and a collaborative development of programs.
In this situation, version information and CA 022~2472 1998-11-02 configuration information are displayed by use of a tree structure in the conventional document management system or the like as shown in Fig. 5. For example, PVCS Version Manager (http://www.intersolv.co.jp/PVCS/main/Function/
Vm.htm) of INTERSOLV discloses a technology in which program versions are managed to display source names of each program and versions thereof in a tree structure.
In a display of Fig. 5, there is presented a combination of version information shown in Fig. 6 and configuration information shown in Fig. 7. But, Figs. 6 and 7 are not admitted as prior art.
In Fig. 7, 701 indicates a name of a project as an object of management and 702 denotes constituent elements of the project. Configuration information includes a file name 704 and the like corresponding to a constituent element name 703, and the example of Fig. 7 indicates that Project "Product XX Manual" has constituent elements "Contents", "Chapter 1", "Chapter 2", and "Fig.
1." , In Fig. 6, 601 to 604 indicate version informa-tion items respectively corresponding to constituent elements of "Product XX Manual". Each version information includes a version name 605, a creator or writer of the version 606, a creation date thereof 607, etc., and Fig. 6 expresses, for example, that "Contents" include two versions of V1 and V2 (601).
Fig. 5 includes a root node of tree 501 indicat-ing the displayed project. A sub-node 502 thereof denotes CA 022~2472 1998-11-02 a constituent element of the project. Furthermore, a sub-node 503 of the element indicates a list of versions of respective constituent elements.
As above, information in which version informa-tion is combined with configuration information isdisplayed in a tree structure. Consequently, the user can recognize documents and program source names of the pertinent project as well as versions thereof.
However, the method of displaying version information and configuration information in accordance with the conventional document management system is attended with the following problems.
A first problem will be now described.
In the restoration of a document at a point of time in the past in Fig. 5, assume an example of a case in which "Chapter 1" is restored for a point of time of Dec.
4, 1997.
In the conventional display method using the tree structure, there is provided a graphic user interface (GUI) as shown in Fig. 8 to obtain information of a creation date or the like of each version. That is, by pointing an arbitrary constituent element of a document, there is displayed a list of version information thereof.
In Fig. 8, version information 802 is displayed for ~Chapter 1. Namely, it is only necessary to restore the document of V2 by referring to the information.
However, to restore "Contents" for Dec. 4, 1997 on which "Chapter 1" was of V2, there is required a CA 022~2472 1998-11-02 comparison of the creation date by referring to version information of "Contents" in this case. That is, when only the display method of Fig. 5 is used, it cannot be known that which one of the versions of "Contents" was used for each version of "Chapter 1".
As above, in the conventional display method, it is not possible to recognize a relationship in time between constituent elements, i.e., how these mutually related elements were edited. Therefore, it is difficult for the user to conduct operation for the restoration of the elements of a project into documents at a point of time in the past.
Description will now be given of a second problem.
Assume an example of a case in which as a constituent element of a project, there is specified not only a document or a source file but also a particular version name of the element.
This is effective, for example, in a case of management in which when a project has a version and a product manual includes several documents as its constituent elements, a first version of product manual includes the constituent elements of a version and a second version thereof includes the elements of another version.
Fig. 9 is an example in which there is specified, in addition to the configuration information of Fig. 7, a particular version name of the constituent element.
Fig. 9 shows configuration information 901 of CA 022~2472 1998-11-02 first version" and configuration information 903 of llsecond version" of "Product XX Manual". Each information includes a version name (902, 904) for each element in addition to a constituent element name 703 and a file name 704 associated therewith. In short, 901 indicates that first version" of "Product XX Manual" includes V1 of Contents", V1 of "Chapter 1", V2 of "Chapter 2", and V1 of ~Fig. 1" and 903 indicates that "second version" of ~Product XX Manual" includes V2 of "Contents", V4 of "Chapter 1", V2 of "Chapter 2", and V3 of "Fig. 1".
Configuration information of Fig. 9 is displayed in a tree structure, for example, as shown in Fig. 10.
In Fig. 10, a root node of tree 1001 represents a project. A sub-node 1002 thereof indicates a constituent element of the project and a sub-node 1003 of the element denotes a version name corresponding to each element.
However, in the display method above, although it is possible to know a version corresponding to each constituent element, the user cannot obtain, for example, how the version is edited before and/or after a particular point of time.
For example, ~Contents~ of ~first version" of IlProduct XX Manual" is of V1 in the example of Fig. 10.
However, there cannot be attained information of whether or not the Contents are edited thereafter and hence the position or the like of the version of the project cannot be known. That is, there exists a problem that information about versions of constituent elements of a project and CA 022~2472 1998-11-02 historical information of editing of each version from another version cannot be obtained.
It is therefore an object of the present invention, which copes with the problems above, to provide a method of displaying version information and configura-tion information in which information of combination of version information and configuration information is clearly presented to the user such that the user refers to version information of documents and program sources of a project to easily restore versions of all elements of the project at an arbitrary point of time in the past and to easily obtain an editing process of each version in the past.
To achieve the object above, in accordance with one aspect of the present invention, there is provided a version and configuration information display method for use with a document management system including a processor, a storage, and a terminal unit for managing version information of documents, program sources, etc. and configuration information including a plurality of documents, a plurality of program sources, etc., including the steps of storing, each time a document, a program source, and the like is edited, version information includ-ing a version name thereof, a creation date thereof, and the like in the storage; storing configuration information of a project in a set of a plurality of documents, a plurality of program sources, and the like in the storage;
and reading the version information and the configuration CA 022~2472 1998-11-02 information of the project from the storage, placing and displaying information of constituent elements of a project including documents, program sources, and the like on a screen of the terminal unit in a vertical direction, and placing and displaying version information of each of the constituent elements thereon by using the creation date as a reference in a horizontal direction.
Moreover, the display step uses, in place of the creation date, a version of a project as the reference.
Additionally, the display step includes, in place of the step of placing and displaying information of constituent elements of a project including documents, program sources, etc. in a vertical direction, the step of placing and displaying information of constituent elements of a project including documents, program sources, etc. in a tree structure in a vertical direction in accordance with a hierarchical relationship between the constituent elements.
The display includes the step of storing, in the storage, job management information for inspection of a state of writing an entire project and documents as its elements and a state of developing program sources. The display step reads the job management information from the storage and places and displays the job management informa-tion on the screen of the terminal unit.
BRIEF DESCRIPTION OF THE DRAWINGS
Fig. 1 is a diagram showing constitution of a .~ . . .
CA 022~2472 1998-11-02 first embodiment in accordance with the present invention;
Fig. 2 is a flowchart showing a processing procedure of a version management program in the first embodiment in accordance with the present invention;
Fig. 3 is a flowchart showing a processing procedure of a configuration management program in the first embodiment in accordance with the present invention;
Fig. 4 is a flowchart showing a processing procedure to two-dimensionally display version information and configuration information in the first embodiment in accordance with the present invention;
Fig. 5 is a diagram showing a first display example of version information and configuration informa-tion in a conventional display method;
Fig. 6 is a diagram showing an example of version information to explain an embodiment in accordance with the present invention;
Fig. 7 is a diagram showing an example of configuration information to explain a first embodiment in accordance with the present invention;
Fig. 8 is a diagram showing a state of referring to version information in a conventional display method;
Fig. 9 is a diagram showing an example of configuration'information to explain a second embodiment in accordance with the present invention;
Fig. 10 is a diagram showing a second display example of version information and configuration informa-tion in a conventional display method;
CA 022~2472 1998-11-02 Fig. 11 is a diagram showing a display example of version information and configuration information in the first embodiment in accordance with the present invention;
Fig. 12 is a diagram showing a first display process to explain a display method of version information and configuration information in the first embodiment in accordance with the present invention;
Fig. 13 is a diagram showing a second display process to explain a display method of version information and configuration information in the first embodiment in accordance with the present invention;
Fig. 14 is a flowchart showing a processing procedure to two-dimensionally display version information and configuration information in the second embodiment in accordance with the present invention;
Fig. 15 is a diagram showing a first display example of version information and configuration informa-tion in the second embodiment in accordance with the present invention;
Fig. 16 is a diagram showing a second display example of version information and configuration informa-tion in the second embodiment in accordance with the present invention;
Fig. 17 is a diagram showing a third display example of version information and configuration informa-tion in the second embodiment in accordance with the present invention;
Fig. 18 is a diagram showing a fourth display CA 022~2472 1998-11-02 example of version information and configuration informa-tion in the second embodiment in accordance with the present invention;
Fig. 19 is a diagram showing constitution of a third embodiment in accordance with the present invention;
Fig. 20 is a diagram showing an example of configuration information and job management information to explain the third embodiment in accordance with the present invention;
Fig. 21 is a diagram showing a display example of version information and configuration information in the third embodiment in accordance with the present invention;
Fig. 22 is a diagram showing a display example of version information to explain a fourth embodiment in accordance with the present invention;
Fig. 23 is a diagram showing an example of configuration information to explain the fourth embodiment in accordance with the present invention; and Fig. 24 is a diagram showing a display example of version information and configuration information of the fourth embodiment in accordance with the present invention.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
Next, description will be given of an embodiment in accordance with the present invention.
Fig. 1 shows constitution of a first embodiment of the present invention.
As can be seen from the diagram, the embodiment CA 022~2472 1998-11-02 includes a CPU 101, a terminal unit 102, a secondary storage 103, a storage medium 104 for storing programs thereon, and a processing program 1 for conducting version management and configuration management and displaying information about versions and configurations.
Additionally, the processing program 1 includes a version management program 105 to store, each time a document or a program source is edited, version information including a version name and a creation date thereof in the secondary storage 103, a configuration management program 106 to store project configuration information 103b in the secondary storage 103, the information 103b including a set of a plurality of documents and a plurality of program sources, and a version/configuration information two-dimensional (2D) display program 107 to place or toarrange, when the version information 103a and the configuration information 103b are read from the storage 103 for the display thereof, information of constituent elements such as documents and program sources of a project in a vertical direction of a two-dimensional plane and version information of the elements in a horizontal direction in accordance with the creation date to thereby display these items in the two-dimensional manner.
A specific processing procedure of this embodi-ment will be described by referring to the flowcharts ofFigs. 2 to 4. Moreover, the version information of Fig. 6 and the configuration information of Fig. 7 are used in this example of processing.
CA 022~2472 l998-ll-02 However, in the embodiment, it is assumed that the version and configuration information of Figs. 6 and 7 is two-dimensionally displayed as shown in Fig. 11.
Fig. 2 shows a processing procedure of the version management program 105.
In step 201, documents and program sources are edited.
In step 202, when the edited documents and program sources are to be stored with new versions created, the program 105 stores version information including a version name, a creator, and a creation date in the secondary storage 103.
In Fig. 6, 601 indicates version information in which "Table of contents~ is edited to be stored as V1 (table of contents of version 1) and then the table of contents of version V1 is further edited to be stored as V2 (table of contents of version 2).
Fig. 3 shows a processing procedure of the configuration management program 106. This is executed independently of the processing procedure of steps 201 and 202.
In step 301, configuration information is created by the program 106. Namely, there is produced configura-tion information including a name of a project and an element name and a file name of each constituent element.
To create configuration information, the user may specify the project name and its elements via GUI or the like. Alternatively, the information may be automatically CA 022~2472 1998-11-02 created from information of the table of contents described in documents.
In step 302, the created information is stored in the secondary storage 103 by the program 106.
Fig. 7 shows the created configuration informa-tion including a project name of ~Product XX Manual~ and element names and file names for its elements "Contents", ~Chapter 1", "Chapter 2", and Fig. 1.
Fig. 4 shows a processing procedure of the version/configuration 2D display program 107 to display the version and configuration information stored in steps 202 and 302.
In step 401, the information stored in step 302 is read from the storage 103a. There is read the informa-tion of Fig. 7.
In step 402, as a reference for placement orplacement in the vertical direction, the element names are placed and displayed in the vertical direction.
For example, the names of Fig. 7 are displayed on the left side of a display area as shown in Fig. 12.
In step 403, version information corresponding to the elements of information read in step 401 is read from the secondary storage 103b. There is attained version information indicated as 601 to 604.
In step 404, according to the creation date of version information read in step 403, a reference for placement in the horizontal direction to display an item.
This processing is carried out, for example, as CA 022~2472 1998-11-02 follows. When the horizontal placement reference is set to the version creation date, the creation date of each version is acquired from the version information. From the information 601 to 604, the horizontal placement reference is determined as 12/2, 12/3, 12/5, 12/8, and 12/9, which are presented on the upper side of the display area as shown in Fig. 13.
In step 405, version names are placed and displayed at associated positions in the horizontal and vertical directions.
For example, "Contents" of ~V1~ is vertically placed and displayed at a position of ~'Contents" of the element name and is horizontally placed and displayed at a position of ~12/2~ for the creation day. Additionally, ~Contents" of "V2" is placed and displayed at a position of "12/5".
Through the steps above, the version information and the configuration information can be two-dimensionally displayed as shown in Fig. 11.
Thanks to usage of the display method of this kind, the user can easily recognize how the constituent elements such as documents and program sources of a project are edited and how the elements are related to each other with respect to time. Therefore, for any element of the project, the user can easily restore a version thereof at an arbitrary point of time in the past, and the editing process in the past can be easily attained.
A second embodiment of the present invention will CA 022~2472 1998-11-02 be next described.
The second embodiment is an example of a case in which not only documents and source file names but also particular version names of elements are specified as constituent elements of a project. This differs from the first embodiment in the processing of the version/
configuration information 2D display program 107, i.e., the other processing is kept unchanged.
Like the first embodiment, this embodiment includes a CPU 101, a terminal unit 102, a secondary storage 103, a storage medium on which programs are stored, and a processing program 1 to conduct version management and configuration management so as to display information thereof. Moreover, the program 1 includes a version management program 105 to store, each time a document or a program source is edited, version information including a version name and a creation date in the secondary storage 103, a configuration management program 106 to store project configuration information 103b in the secondary storage 103, the information 103b including a set of a plurality of documents and a plurality of program sources, and a version/configuration information 2D display program 107 to place, when the version information 103a and the configuration information 103b are read from the storage for the display thereof, information of constituent elements such as documents and program sources of a project in a vertical direction and version information of the elements in a horizontal direction in accordance with the CA 022~2472 1998-11-02 version of the project to thereby display these items in the two-dimensional manner.
A concrete processing procedure of the program 107 of the embodiment will be described by referring to the flowchart of Fig. 14. Additionally, the version informa-tion of Fig. 6 and the configuration information of Fig. 9 are used in this processing example.
The processing procedure of the programs 105 and 106 including steps 201 and 202 and steps 301 and 302 are kept unchanged.
Fig. 14 shows a processing procedure of the program 107 to display the version and configuration information stored in steps 202 and 302.
In step 1401, from the configuration information stored in the secondary storage 103a in step 302, there is obtained configuration information of each version of the project. Information items 901 and 903 of Fig. 9 are read therefrom.
In step 1402, constituent element names of a plurality of projects are placed and displayed in a vertical direction.
In step 1403, version information corresponding to elements of configuration information read in step 1401 are read from the storage 103b. Information items 601 to 604 of Fig. 6 are read therefrom.
In step 1404, beginning from the version of the oldest creation data, the constituent elements of projects are placed and displayed with project names in the CA 022~2472 1998-11-02 horizontal direction.
In step 1405, version names are placed and displayed at corresponding positions in the horizontal and vertical directions. For a version other than the constituent elements of the projects, the version name is placed and displayed between those of the elements.
Through the steps above, the version information and the configuration information can be two-dimensionally displayed as shown in Fig. 15.
Thanks to usage of the display method of this kind, since the user can easily obtain information such as a relationship between versions of a project and constituent elements thereof, it is possible to easily recognize information, for example, how the editing is conducted through versions of projects. Consequently, the editing of projects can be efficiently achieved.
Furthermore, in place of the display method of Fig. 15, there may be used a method shown in Fig. 16 in which the project version is added to the display of Fig.
11.
In Fig. 16, the creation date of constituent elements is used as a reference for placement in the horizontal direction, and versions specified as elements of projects are connected to each other via a line. In addition to the linkage, the versions specified as elements of projects each may be, for example, enclosed with a line to display the enclosed areas in different colors.
Thanks to the display of Fig. 16, the user can CA 022~2472 l998-ll-02 recognize how the constituent elements such as documents and program sources of projects are edited and how the elements are related to each other with respect to time.
Moreover, the user can attain information such as a relationship between a version of a project and the constituent elements of the version.
Furthermore, Fig. 17 shows an example in which configuration information is placed in a tree structure in accordance with a hierarchical relationship between the constituent elements so as to two-dimensionally display version information of the elements in the horizontal direction.
In this example, "Fig 1" is used in "Chapter 2", namely, there exists a hierarchical relationship that "Fig.
1" is a sub-element of "Chapter 2". In accordance with the usage of this display method, there can be obtained a hierarchical relationship between the constituent elements and a relationship therebetween with respect to time. For example, it can be recognized that "Chapter 2" iS updated at a position indicated as "12/8" and "Fig. 1" used in the update operation is updated at " 12/9".
Additionally, in place of the display method of Fig. 17, there may be used a method in which a certain constituent element is pointed as shown in Fig. 18 to 2 5 obtain the two-dimensional display of configuration information and version information for the sub-elements thereof.
This is effective when there exist a large number CA 022~2472 1998-11-02 of constituent elements and the display of configuration information in the tree structure is vertically elongated and the overall display cannot be viewed in one screen image at a time.
Description will be given of a third embodiment of the present invention.
In relation to the third embodiment, description will be given of a method of displaying version information and configuration information in a case of, for example, collaborative writing of documents and/or collaborative development of programs in which a configuration management function of projects including sets of documents and program sources is collaboratively operated with a job management function to check or to inspect a state of writing of each document and a state of development of each program source.
Fig. 19 shows constitution of the third embodi-ment of the present invention.
As shown in the diagram, the embodiment includes, in addition to the configuration (Fig. 1) of the first embodiment, a job management program 1901 to store job management information 103c in a storage for the checking or inspection of the writing state of documents and the state of development of program sources, the documents and 2 5 program sources being constituent elements of the entire project. When displaying version information and configuration information by the version/configuration information 2D display program 107 in this configuration, CA 022~2472 1998-11-02 the job management information 103c is read from the storage and is then displayed in combination with the version and configuration information.
The job management information includes, for example, information of a deadline by which such an element of project as a document or a program source is to be submitted and information of an event for each element that the editing thereof is completed for the project.
Fig. 20 shows an example of configuration information and job management information for a project.
In Fig. 20, there are shown, in addition to the project name as configuration information, job management information including deadline information 2002 and an editing mode of element 2003. The editing mode of element is information which indicates that the editing of element is being conducted or ~Product XX Manual - Version 2~ has been determined. Items of job management information are specified by the user and is stored in a storage by the job management program 1901.
Fig. 21 shows an example in which the job manage-ment information is displayed by the display program 107.
Deadline information 2102 is displayed along the creation date in the hori~ontal direction and the editing mode 2103 is displayed, for example, by changing the display format of version information with different colors.
As above, since the job management information is displayed in combination with the two-dimensional display of version information and configuration information, the CA 022~2472 l998-ll-02 user can easily recognize the state of writing as well as the state of development.
Description will be given of a fourth embodiment of the present invention.
The fourth embodiment is an example of display in, for example, a program development support system for management of program versions and configurations in which configuration information of programs including several sources and version information of the program sources are displayed.
In contrast with the first to third embodiments in which a project includes several documents and the constituent elements are documents, program sources are assigned as the constituent elements of programs to be developed by the project in the fourth embodiment.
The configuration and the processing procedure of this embodiment are the same as those of the first to fourth embodiments.
Fig. 22 shows an example of version information of program sources and Fig. 23 shows an example of configuration information.
In Fig. 23, 2301 indicates a program name as an object of management and 2302 denotes a program source of the program.
2 5 Configuration information includes a program source name 2303, a file name corresponding thereto 2304, and the like. The example of Fig. 23 means that "ABC
program" includes program sources "main.cpp", ~output.cpp~, CA 022~2472 l998-ll-02 "prog.h", and "output.h".
In Fig. 22, 2201 to 2204 indicate version information respectively corresponding to constituent elements of "ABC program" shown in Fig. 23. Version information includes a version name 2205, a person-in-charge of program of the version 2206, a creation date 2207, etc. Fig. 22 indicates, for example, that "main.cpp"
has four versions Vl to V4 t2201).
Fig. 24 shows an example in which version 10 information of Fig. 22 and configuration information of Fig. 23 are two-dimensionally displayed in accordance with the procedure of steps 201 and 202, steps 301 and 302, and steps 401 to 405.
Utilizing the display method above, the user can 15 easily recognize how the program sources of the program have been edited and how the sources are related to each other.
For example, the user can easily recognize a relationship between a particular version of cpp file and a 20 header file of a particular version. Therefore, the user can easily select and compile associated sources to restore the program at an arbitrary point of time in the past.
Moreover, the process of program development can be easily known.
Similarly, version information of program sources and program configuration information can be two-dimensionally displayed in accordance with a program version by use of the processing procedure of the second .
CA 022~2472 1998-11-02 embodiment. Therefore, the user can recognize the versions of source programs for each version of the program and the modification in the past of sources for the program of a particular version.
Additionally, job management information such as the deadline of program development can also be displayed in accordance with the configuration and the processing procedure of the third embodiment. This makes it possible to easily obtain the program development state.
In accordance with the version information and configuration information display method of the present invention, the version information and the configuration information can be two-dimensionally displayed in which constituent elements of the project are vertically displayed and versions of the elements are displayed by using the creation date thereof as a reference in the horizontal direction.
With this configuration, it can be easily known how the constituent elements of project such as documents and program sources have been edited and how the elements are associated with each other with respect to time.
Accordingly, it is possible to easily restore a version of any element of the project at an arbitrary point of time in the past, and the editing process thereof can be easily known. This increases the efficiency of the collaborative editing job and the like.
When there is employed the two-dimensional display method in which constituent elements of a project CA 022~2472 1998-11-02 is vertically displayed and versions thereof are placed by use of the version of project as a reference in the horizontal direction, the user can easily obtain informa-tion, for example, a relationship between a particular version of project and constituent elements of particular versions. Therefore, information about the editing process in the past of projects can be known and hence the effi-ciency of project editing operation is increased.
Additionally, when there is adopted a two-dimensional display method in which constituent elements of a project are vertically placed in a tree structure in accordance with a hierarchical relationship between the elements and version information of the elements is placed in the horizontal direction, the user can recognize, for example, a relationship between versions of an element and sub-elements thereof. Consequently, it is possible to increase the efficiency when editing documents and the like having a hierarchical relationship.
Furthermore, when there is displayed job manage-ment information to check the writing state of the project and documents as constituent elements thereof and the development state of program sources together with the version information and the configuration information in a two-dimensional fashion, the user can easily obtain information of the editing process in the past of the elements of the project and the writing state and the development state. This consequently increases the efficiency of the job management in, for example, the CA 022~2472 1998-11-02 collaborative editing job.
While the present invention has been described with reference to the particular illustrative embodiments, it is not to be restricted by those embodiments but only by the appended claims. It is to be appreciated that those skilled in the art can change or modify the embodiments without departing from the scope and spirit of the present invention.
Claims (12)
1. A version and configuration information display method for use with a document management system including a processor, a storage, and a terminal unit for managing version information of documents and program sources and configuration information including a plurality of documents and a plurality of program sources, comprising the steps of:
storing, each time a document or a program source is edited, version information including a version name thereof and a creation date thereof in a storage;
storing configuration information of a plurality of documents and a plurality of program sources in another storage; and reading the version information and the configuration information from storage, placing and displaying information of constituent elements of documents and program sources on a screen of the terminal unit in a vertical direction, and placing and displaying version information of each of the constituent elements thereon by using the creation date as a reference in a horizontal direction.
storing, each time a document or a program source is edited, version information including a version name thereof and a creation date thereof in a storage;
storing configuration information of a plurality of documents and a plurality of program sources in another storage; and reading the version information and the configuration information from storage, placing and displaying information of constituent elements of documents and program sources on a screen of the terminal unit in a vertical direction, and placing and displaying version information of each of the constituent elements thereon by using the creation date as a reference in a horizontal direction.
2. A version and configuration information display method in accordance with claim 1, wherein the display step uses, in place of the creation date, a version as the reference.
3. A version and configuration information display method in accordance with claim 1, wherein the display step includes, in place of the step of placing and displaying information of constituent elements of documents and program sources in a vertical direction, the step of placing and displaying information of constituent elements of documents and program sources in a tree structure in a vertical direction in accordance with a hierarchic relationship between the constituent elements.
4. A version and configuration information display method in accordance with claim 1, further comprising the step of storing, in the storage, job management information for inspection of a state of writing documents and a state of developing program sources, wherein the display step reads the job management information from the storage and places and displays the job management information on the screen of the terminal unit.
5. A version and configuration information display apparatus for use with a document management system including a processor, a storage, and a terminal unit for managing version information of documents and program sources and configuration information including a plurality of documents and a plurality of program sources, comprising:
means for storing, each time a document or a program source is edited, version information including a version name thereof and a creation date thereof in the storage;
means for storing configuration information of a plurality of documents and a plurality of program sources in the storage; and means for reading the version information and the configuration information from the storage, placing and displaying information of constituent elements of documents and program sources on a screen of the terminal unit in a vertical direction, and placing and displaying version information of each of the constituent elements thereon by using the creation date as a reference in a horizontal direction.
means for storing, each time a document or a program source is edited, version information including a version name thereof and a creation date thereof in the storage;
means for storing configuration information of a plurality of documents and a plurality of program sources in the storage; and means for reading the version information and the configuration information from the storage, placing and displaying information of constituent elements of documents and program sources on a screen of the terminal unit in a vertical direction, and placing and displaying version information of each of the constituent elements thereon by using the creation date as a reference in a horizontal direction.
6. A version and configuration information display apparatus in accordance with claim 5, wherein the display means uses, in place of the creation date, a version as the reference.
7. A version and configuration information display apparatus in accordance with claim 5, wherein the display means conducts, in place of the placing and displaying information of constituent elements of documents and program sources in a vertical direction, placing and displaying information of constituent elements of documents and program sources in a tree structure in a vertical direction in accordance with a hierarchic relationship between the constituent elements.
8. A version and configuration information display apparatus in accordance with claim 5, further including means for storing, in the storage, job management information for inspection of a state of writing documents as constituent elements and a state of developing program sources, wherein the display means reads the job management information from the storage and places and displays the job management information on the screen of the terminal unit.
9. A computer-readable recording medium on which a version and configuration information display program of a document management system is recorded, wherein the program executes:
a procedure of storing, each time a document or a program source is edited, version information including a version name thereof and a creation date thereof in a first storage;
a procedure of storing configuration information of a plurality of documents and a plurality of program sources in a second storage; and a procedure of reading the version information and the configuration information from said first storage and said second storage, placing and displaying information of constituent elements of documents and program sources on a screen of the terminal unit in a vertical direction, and placing and displaying version information of each of the constituent elements thereon by using the creation date as a reference in a horizontal direction.
a procedure of storing, each time a document or a program source is edited, version information including a version name thereof and a creation date thereof in a first storage;
a procedure of storing configuration information of a plurality of documents and a plurality of program sources in a second storage; and a procedure of reading the version information and the configuration information from said first storage and said second storage, placing and displaying information of constituent elements of documents and program sources on a screen of the terminal unit in a vertical direction, and placing and displaying version information of each of the constituent elements thereon by using the creation date as a reference in a horizontal direction.
10. A computer-readable recording medium in accordance with claim 9, wherein the display procedure uses, in place of the creation date, a version as the reference.
11. A computer-readable recording medium in accordance with claim 9, wherein the display procedure conducts, in place of the placing and displaying information of constituent elements of documents and program sources in a vertical direction, placing and displaying information of constituent elements of documents and program sources in a tree structure in a vertical direction in accordance with a hierarchic relationship between the constituent elements.
12. A computer-readable recording medium in accordance with claim 9, further including a procedure of storing, in the storage, job management information for inspection of a state of writing documents as constituent elements and a state of developing program sources, wherein the display procedure reads the job management information from the storage and places and displays the job management information on the screen of the terminal unit.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP09-319011 | 1997-11-05 | ||
| JP31901197A JPH11143754A (en) | 1997-11-05 | 1997-11-05 | Version information and constitution information display method and device therefor, and computer readable recording medium for recording version information and constitution information display program |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2252472A1 true CA2252472A1 (en) | 1999-05-05 |
Family
ID=18105511
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002252472A Abandoned CA2252472A1 (en) | 1997-11-05 | 1998-11-02 | A method of and an apparatus for displaying version information and configuration information and a computer-readable recording medium on which a version and configuration information display program is recorded |
Country Status (4)
| Country | Link |
|---|---|
| US (2) | US6301592B1 (en) |
| EP (1) | EP0915427A3 (en) |
| JP (1) | JPH11143754A (en) |
| CA (1) | CA2252472A1 (en) |
Families Citing this family (356)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6418478B1 (en) | 1997-10-30 | 2002-07-09 | Commvault Systems, Inc. | Pipelined high speed data transfer mechanism |
| US7209972B1 (en) | 1997-10-30 | 2007-04-24 | Commvault Systems, Inc. | High speed data transfer mechanism |
| US7581077B2 (en) | 1997-10-30 | 2009-08-25 | Commvault Systems, Inc. | Method and system for transferring data in a storage operation |
| JPH11143754A (en) | 1997-11-05 | 1999-05-28 | Hitachi Ltd | Version information and constitution information display method and device therefor, and computer readable recording medium for recording version information and constitution information display program |
| US7277941B2 (en) | 1998-03-11 | 2007-10-02 | Commvault Systems, Inc. | System and method for providing encryption in a storage network by storing a secured encryption key with encrypted archive data in an archive storage device |
| US7739381B2 (en) * | 1998-03-11 | 2010-06-15 | Commvault Systems, Inc. | System and method for providing encryption in storage operations in a storage network, such as for use by application service providers that provide data storage services |
| US8234477B2 (en) | 1998-07-31 | 2012-07-31 | Kom Networks, Inc. | Method and system for providing restricted access to a storage medium |
| US9361243B2 (en) | 1998-07-31 | 2016-06-07 | Kom Networks Inc. | Method and system for providing restricted access to a storage medium |
| US6918082B1 (en) * | 1998-12-17 | 2005-07-12 | Jeffrey M. Gross | Electronic document proofing system |
| US6549894B1 (en) | 1999-05-07 | 2003-04-15 | Legalstar, Inc. | Computerized docketing system for intellectual property law with automatic due date alert |
| JP2000322303A (en) * | 1999-05-10 | 2000-11-24 | Fujitsu Ltd | Integral document management system and document withdrawing device used for the system and computer readable recording medium for recording document withdraw program |
| US7035880B1 (en) | 1999-07-14 | 2006-04-25 | Commvault Systems, Inc. | Modular backup and retrieval system used in conjunction with a storage area network |
| US7389311B1 (en) | 1999-07-15 | 2008-06-17 | Commvault Systems, Inc. | Modular backup and retrieval system |
| US7395282B1 (en) | 1999-07-15 | 2008-07-01 | Commvault Systems, Inc. | Hierarchical backup and retrieval system |
| US7418435B1 (en) * | 1999-08-05 | 2008-08-26 | Oracle International Corporation | Multi-model access to data |
| JP4232283B2 (en) * | 1999-08-10 | 2009-03-04 | ソニー株式会社 | Access history presentation method, access history presentation device, resource provision method and resource provision device, and computer-readable recording medium recording a program |
| US7155481B2 (en) | 2000-01-31 | 2006-12-26 | Commvault Systems, Inc. | Email attachment management in a computer system |
| US6658436B2 (en) | 2000-01-31 | 2003-12-02 | Commvault Systems, Inc. | Logical view and access to data managed by a modular data and storage management system |
| US7434219B2 (en) * | 2000-01-31 | 2008-10-07 | Commvault Systems, Inc. | Storage of application specific profiles correlating to document versions |
| US7003641B2 (en) | 2000-01-31 | 2006-02-21 | Commvault Systems, Inc. | Logical view with granular access to exchange data managed by a modular data and storage management system |
| TW544671B (en) | 2000-02-25 | 2003-08-01 | Sony Corp | Recording medium, recording apparatus, and reading apparatus |
| JP2002024211A (en) * | 2000-06-30 | 2002-01-25 | Hitachi Ltd | Method and system for document management and storage medium having processing program stored thereon |
| EP1204048A1 (en) * | 2000-11-03 | 2002-05-08 | Sun Microsystems, Inc. | Method and apparatus for handling scenarios in spreadsheet documents |
| JP4401565B2 (en) * | 2000-12-12 | 2010-01-20 | キヤノン株式会社 | Recording apparatus and management method |
| US20020107886A1 (en) * | 2001-02-07 | 2002-08-08 | Gentner Donald R. | Method and apparatus for automatic document electronic versioning system |
| US7679774B2 (en) | 2001-04-06 | 2010-03-16 | Oce Printing Systems Gmbh | Method, system and computer program for the generation of an electronic document from scanned image data |
| US7107298B2 (en) | 2001-09-28 | 2006-09-12 | Commvault Systems, Inc. | System and method for archiving objects in an information store |
| DE60232165D1 (en) | 2001-09-28 | 2009-06-10 | Commvault Systems Inc | SYSTEM AND METHOD FOR PRODUCING AND MANAGING FAST RECOVERY VOLUME |
| JP4369082B2 (en) * | 2001-10-05 | 2009-11-18 | 株式会社日立製作所 | Component selection support system, component selection support method, component selection support program, and component selection support storage medium |
| US20030101155A1 (en) * | 2001-11-23 | 2003-05-29 | Parag Gokhale | Method and system for scheduling media exports |
| US7584227B2 (en) * | 2005-12-19 | 2009-09-01 | Commvault Systems, Inc. | System and method for containerized data storage and tracking |
| WO2003046721A1 (en) * | 2001-11-23 | 2003-06-05 | Commvault Systems, Inc. | Selective data replication system and method |
| US7603518B2 (en) | 2005-12-19 | 2009-10-13 | Commvault Systems, Inc. | System and method for improved media identification in a storage device |
| US20050033913A1 (en) * | 2003-04-03 | 2005-02-10 | Rajiv Kottomtharayil | Method and system for controlling a robotic arm in a storage device |
| US8346733B2 (en) | 2006-12-22 | 2013-01-01 | Commvault Systems, Inc. | Systems and methods of media management, such as management of media to and from a media storage library |
| US6981268B2 (en) * | 2001-12-05 | 2005-12-27 | Microsoft Corporation | System and method for persisting and resolving application assembly binds |
| US7120652B2 (en) * | 2002-04-25 | 2006-10-10 | Sun Microsystems, Inc. | Method, system and program for determining version of storage devices and programs indicated in the resource information installed in the computer system |
| JP3913127B2 (en) * | 2002-06-27 | 2007-05-09 | 富士通株式会社 | Electronic document system, electronic document management apparatus, computer program, and recording medium |
| US7254772B2 (en) * | 2002-07-30 | 2007-08-07 | Xerox Corporation | Systems and methods for visually representing the aging and/or expiration of electronic documents |
| US7130970B2 (en) * | 2002-09-09 | 2006-10-31 | Commvault Systems, Inc. | Dynamic storage device pooling in a computer system |
| JP3861780B2 (en) * | 2002-09-13 | 2006-12-20 | 富士通株式会社 | CAD generation management system and generation management program |
| AU2003272457A1 (en) * | 2002-09-16 | 2004-04-30 | Commvault Systems, Inc. | System and method for blind media support |
| US8370542B2 (en) | 2002-09-16 | 2013-02-05 | Commvault Systems, Inc. | Combined stream auxiliary copy system and method |
| EP1579331A4 (en) | 2002-10-07 | 2007-05-23 | Commvault Systems Inc | System and method for managing stored data |
| JP4185346B2 (en) * | 2002-10-18 | 2008-11-26 | 株式会社日立製作所 | Storage apparatus and configuration setting method thereof |
| US7130844B2 (en) * | 2002-10-31 | 2006-10-31 | International Business Machines Corporation | System and method for examining, calculating the age of an document collection as a measure of time since creation, visualizing, identifying selectively reference those document collections representing current activity |
| US7293286B2 (en) | 2003-02-20 | 2007-11-06 | Bea Systems, Inc. | Federated management of content repositories |
| US7840614B2 (en) | 2003-02-20 | 2010-11-23 | Bea Systems, Inc. | Virtual content repository application program interface |
| US8010491B2 (en) * | 2003-02-28 | 2011-08-30 | Microsoft Corporation | Method for managing multiple file states for replicated files |
| JP4393774B2 (en) * | 2003-02-28 | 2010-01-06 | 株式会社日立製作所 | Job management method, information processing system, program, and recording medium |
| US7389309B2 (en) * | 2003-02-28 | 2008-06-17 | Microsoft Corporation | Method for managing file replication in applications |
| EP1625526B1 (en) | 2003-04-03 | 2012-10-03 | Commvault Systems, Inc. | System and method for dynamically performing storage operations in a computer network |
| US7631351B2 (en) * | 2003-04-03 | 2009-12-08 | Commvault Systems, Inc. | System and method for performing storage operations through a firewall |
| WO2004090789A2 (en) | 2003-04-03 | 2004-10-21 | Commvault Systems, Inc. | System and method for extended media retention |
| US20050039069A1 (en) * | 2003-04-03 | 2005-02-17 | Anand Prahlad | Remote disaster data recovery system and method |
| US20040215601A1 (en) * | 2003-04-23 | 2004-10-28 | Win-Harn Liu | Method of file management using a computer |
| US7454569B2 (en) | 2003-06-25 | 2008-11-18 | Commvault Systems, Inc. | Hierarchical system and method for performing storage operations in a computer network |
| US7418656B1 (en) * | 2003-10-03 | 2008-08-26 | Adobe Systems Incorporated | Dynamic annotations for electronics documents |
| US7546324B2 (en) | 2003-11-13 | 2009-06-09 | Commvault Systems, Inc. | Systems and methods for performing storage operations using network attached storage |
| US7613748B2 (en) | 2003-11-13 | 2009-11-03 | Commvault Systems, Inc. | Stored data reverification management system and method |
| US7734578B2 (en) * | 2003-11-13 | 2010-06-08 | Comm Vault Systems, Inc. | System and method for performing integrated storage operations |
| CA2544063C (en) | 2003-11-13 | 2013-09-10 | Commvault Systems, Inc. | System and method for combining data streams in pilelined storage operations in a storage network |
| US20050174869A1 (en) * | 2003-11-13 | 2005-08-11 | Rajiv Kottomtharayil | System and method for data storage and tracking |
| US7440982B2 (en) | 2003-11-13 | 2008-10-21 | Commvault Systems, Inc. | System and method for stored data archive verification |
| CA2546304A1 (en) | 2003-11-13 | 2005-05-26 | Commvault Systems, Inc. | System and method for performing an image level snapshot and for restoring partial volume data |
| US20050228816A1 (en) * | 2004-04-13 | 2005-10-13 | Bea Systems, Inc. | System and method for content type versions |
| CA2564967C (en) | 2004-04-30 | 2014-09-30 | Commvault Systems, Inc. | Hierarchical systems and methods for providing a unified view of storage information |
| US8266406B2 (en) | 2004-04-30 | 2012-09-11 | Commvault Systems, Inc. | System and method for allocation of organizational resources |
| US7860924B2 (en) * | 2004-05-21 | 2010-12-28 | Computer Associates Think, Inc. | Method and system for supporting multiple versions of web services standards |
| EP1617344A1 (en) | 2004-07-07 | 2006-01-18 | Canon Kabushiki Kaisha | Image management device and method for managing a plurality of images |
| US9047165B1 (en) | 2004-07-08 | 2015-06-02 | The Mathworks, Inc. | Multiversion model versioning system and method |
| US7739655B1 (en) | 2004-07-08 | 2010-06-15 | The Mathworks, Inc. | Version control in modeling environments |
| US9292276B1 (en) | 2004-07-19 | 2016-03-22 | Micro Focus (IP) Development Limited | Method and system for utilizing change packages |
| US7614038B2 (en) * | 2004-07-19 | 2009-11-03 | Accurev, Inc. | Systems and methods for determining the software components included in a view of a software development project at a particular time |
| US8341590B1 (en) | 2007-12-12 | 2012-12-25 | Accurev, Inc. | System for relating workflow status to code component status in a software project |
| US8473893B2 (en) * | 2008-09-30 | 2013-06-25 | Accurev, Inc. | Integration of external software analysis processes with software configuration management applications |
| US8667465B2 (en) * | 2008-03-31 | 2014-03-04 | Accurev, Inc. | System for estimating a software product release time from version information |
| US8548967B1 (en) | 2007-12-12 | 2013-10-01 | Accurev, Inc. | System for visual query and manipulation of configuration management records |
| JP4682563B2 (en) * | 2004-08-31 | 2011-05-11 | 富士通株式会社 | Document management system, document management method, and document management program |
| US20060059423A1 (en) * | 2004-09-13 | 2006-03-16 | Stefan Lehmann | Apparatus, system, and method for creating customized workflow documentation |
| US7500053B1 (en) | 2004-11-05 | 2009-03-03 | Commvvault Systems, Inc. | Method and system for grouping storage system components |
| WO2006053050A2 (en) | 2004-11-08 | 2006-05-18 | Commvault Systems, Inc. | System and method for performing auxiliary storage operations |
| JP4515463B2 (en) * | 2004-11-12 | 2010-07-28 | 株式会社ジャストシステム | Data processing apparatus and data processing method |
| US8775823B2 (en) | 2006-12-29 | 2014-07-08 | Commvault Systems, Inc. | System and method for encrypting secondary copies of data |
| US8959299B2 (en) | 2004-11-15 | 2015-02-17 | Commvault Systems, Inc. | Using a snapshot as a data source |
| US7921076B2 (en) | 2004-12-15 | 2011-04-05 | Oracle International Corporation | Performing an action in response to a file system event |
| US7702661B2 (en) * | 2005-03-02 | 2010-04-20 | Computer Associates Think, Inc. | Managing checked out files in a source control repository |
| US8112605B2 (en) * | 2005-05-02 | 2012-02-07 | Commvault Systems, Inc. | System and method for allocation of organizational resources |
| US7945541B1 (en) * | 2005-05-20 | 2011-05-17 | Adobe Systems Incorporated | Version set of related objects |
| US20070057967A1 (en) * | 2005-07-13 | 2007-03-15 | Armstrong Orin R | System and method for the display of versioned documents and amendments |
| CN1904879B (en) * | 2005-07-27 | 2011-01-12 | 国际商业机器公司 | Electronic table system, method for obtaining snapshot/history information of electronic table file |
| US7602906B2 (en) * | 2005-08-25 | 2009-10-13 | Microsoft Corporation | Cipher for disk encryption |
| US8949455B2 (en) | 2005-11-21 | 2015-02-03 | Oracle International Corporation | Path-caching mechanism to improve performance of path-related operations in a repository |
| US7668884B2 (en) | 2005-11-28 | 2010-02-23 | Commvault Systems, Inc. | Systems and methods for classifying and transferring information in a storage network |
| US7822749B2 (en) | 2005-11-28 | 2010-10-26 | Commvault Systems, Inc. | Systems and methods for classifying and transferring information in a storage network |
| US7636743B2 (en) | 2005-12-19 | 2009-12-22 | Commvault Systems, Inc. | Pathname translation in a data replication system |
| EP1974296B8 (en) | 2005-12-19 | 2016-09-21 | Commvault Systems, Inc. | Systems and methods for performing data replication |
| US8572330B2 (en) | 2005-12-19 | 2013-10-29 | Commvault Systems, Inc. | Systems and methods for granular resource management in a storage network |
| US7543125B2 (en) | 2005-12-19 | 2009-06-02 | Commvault Systems, Inc. | System and method for performing time-flexible calendric storage operations |
| EP1974490A4 (en) * | 2005-12-19 | 2012-01-18 | Commvault Systems Inc | System and method for providing a flexible licensing system for digital content |
| US20070166674A1 (en) * | 2005-12-19 | 2007-07-19 | Kochunni Jaidev O | Systems and methods for generating configuration metrics in a storage network |
| US7651593B2 (en) | 2005-12-19 | 2010-01-26 | Commvault Systems, Inc. | Systems and methods for performing data replication |
| US7606844B2 (en) | 2005-12-19 | 2009-10-20 | Commvault Systems, Inc. | System and method for performing replication copy storage operations |
| US7617262B2 (en) | 2005-12-19 | 2009-11-10 | Commvault Systems, Inc. | Systems and methods for monitoring application data in a data replication system |
| US7457790B2 (en) * | 2005-12-19 | 2008-11-25 | Commvault Systems, Inc. | Extensible configuration engine system and method |
| US20200257596A1 (en) | 2005-12-19 | 2020-08-13 | Commvault Systems, Inc. | Systems and methods of unified reconstruction in storage systems |
| US7620710B2 (en) | 2005-12-19 | 2009-11-17 | Commvault Systems, Inc. | System and method for performing multi-path storage operations |
| US8930496B2 (en) | 2005-12-19 | 2015-01-06 | Commvault Systems, Inc. | Systems and methods of unified reconstruction in storage systems |
| US7962709B2 (en) | 2005-12-19 | 2011-06-14 | Commvault Systems, Inc. | Network redirector systems and methods for performing data replication |
| US7617253B2 (en) * | 2005-12-19 | 2009-11-10 | Commvault Systems, Inc. | Destination systems and methods for performing data replication |
| US8661216B2 (en) * | 2005-12-19 | 2014-02-25 | Commvault Systems, Inc. | Systems and methods for migrating components in a hierarchical storage network |
| US20110010518A1 (en) | 2005-12-19 | 2011-01-13 | Srinivas Kavuri | Systems and Methods for Migrating Components in a Hierarchical Storage Network |
| WO2007109444A2 (en) * | 2006-03-17 | 2007-09-27 | Schmitt William C | Common format learning device |
| EP2013779A4 (en) * | 2006-04-14 | 2012-07-18 | Vertafore Inc | Method, apparatus and computer-readabele medium to provide customized classification of documents in a file management system |
| US20070294612A1 (en) * | 2006-06-20 | 2007-12-20 | Microsoft Corporation | Comparing and Managing Multiple Presentations |
| US8726242B2 (en) | 2006-07-27 | 2014-05-13 | Commvault Systems, Inc. | Systems and methods for continuous data replication |
| US20080201223A1 (en) * | 2006-09-19 | 2008-08-21 | Lutnick Howard W | Products and processes for providing information services |
| US7539783B2 (en) * | 2006-09-22 | 2009-05-26 | Commvault Systems, Inc. | Systems and methods of media management, such as management of media to and from a media storage library, including removable media |
| US7882077B2 (en) | 2006-10-17 | 2011-02-01 | Commvault Systems, Inc. | Method and system for offline indexing of content and classifying stored data |
| US8655914B2 (en) | 2006-10-17 | 2014-02-18 | Commvault Systems, Inc. | System and method for storage operation access security |
| CN101529419B (en) | 2006-10-17 | 2013-05-01 | 慷孚系统公司 | Method and system for offline indexing of content and classifying stored data |
| US8370442B2 (en) | 2008-08-29 | 2013-02-05 | Commvault Systems, Inc. | Method and system for leveraging identified changes to a mail server |
| EP2102750B1 (en) | 2006-12-04 | 2014-11-05 | Commvault Systems, Inc. | System and method for creating copies of data, such as archive copies |
| US8677091B2 (en) | 2006-12-18 | 2014-03-18 | Commvault Systems, Inc. | Writing data and storage system specific metadata to network attached storage device |
| US8312323B2 (en) | 2006-12-22 | 2012-11-13 | Commvault Systems, Inc. | Systems and methods for remote monitoring in a computer network and reporting a failed migration operation without accessing the data being moved |
| US7734669B2 (en) * | 2006-12-22 | 2010-06-08 | Commvault Systems, Inc. | Managing copies of data |
| US20080228771A1 (en) | 2006-12-22 | 2008-09-18 | Commvault Systems, Inc. | Method and system for searching stored data |
| US7831566B2 (en) | 2006-12-22 | 2010-11-09 | Commvault Systems, Inc. | Systems and methods of hierarchical storage management, such as global management of storage operations |
| TWI402693B (en) * | 2006-12-22 | 2013-07-21 | Hon Hai Prec Ind Co Ltd | An interface device and method for controlling documents edition |
| US7840537B2 (en) | 2006-12-22 | 2010-11-23 | Commvault Systems, Inc. | System and method for storing redundant information |
| US20080155205A1 (en) * | 2006-12-22 | 2008-06-26 | Parag Gokhale | Systems and methods of data storage management, such as dynamic data stream allocation |
| US8719809B2 (en) | 2006-12-22 | 2014-05-06 | Commvault Systems, Inc. | Point in time rollback and un-installation of software |
| US7831766B2 (en) * | 2006-12-22 | 2010-11-09 | Comm Vault Systems, Inc. | Systems and methods of data storage management, such as pre-allocation of storage space |
| JP2008217168A (en) * | 2007-02-28 | 2008-09-18 | Toshiba Corp | Version management device |
| US8290808B2 (en) | 2007-03-09 | 2012-10-16 | Commvault Systems, Inc. | System and method for automating customer-validated statement of work for a data storage environment |
| JP2008226005A (en) * | 2007-03-14 | 2008-09-25 | Omron Corp | Distribution management system for control software component |
| US20090064030A1 (en) * | 2007-06-01 | 2009-03-05 | Suman Grandhi | System and Method For Representing Point-In-Time Data On A Common Viewing Plane |
| CN103123702B (en) | 2007-08-28 | 2017-11-28 | Commvault系统公司 | Such as the managing power consumption of the data processing resources of the adaptive managing power consumption of data storage operations |
| US8706976B2 (en) | 2007-08-30 | 2014-04-22 | Commvault Systems, Inc. | Parallel access virtual tape library and drives |
| US8396838B2 (en) | 2007-10-17 | 2013-03-12 | Commvault Systems, Inc. | Legal compliance, electronic discovery and electronic document handling of online and offline copies of data |
| US7836174B2 (en) | 2008-01-30 | 2010-11-16 | Commvault Systems, Inc. | Systems and methods for grid-based data scanning |
| US8296301B2 (en) | 2008-01-30 | 2012-10-23 | Commvault Systems, Inc. | Systems and methods for probabilistic data classification |
| US8769048B2 (en) | 2008-06-18 | 2014-07-01 | Commvault Systems, Inc. | Data protection scheduling, such as providing a flexible backup window in a data protection system |
| US9128883B2 (en) | 2008-06-19 | 2015-09-08 | Commvault Systems, Inc | Data storage resource allocation by performing abbreviated resource checks based on relative chances of failure of the data storage resources to determine whether data storage requests would fail |
| US8352954B2 (en) | 2008-06-19 | 2013-01-08 | Commvault Systems, Inc. | Data storage resource allocation by employing dynamic methods and blacklisting resource request pools |
| US9098495B2 (en) | 2008-06-24 | 2015-08-04 | Commvault Systems, Inc. | Application-aware and remote single instance data management |
| US8219524B2 (en) | 2008-06-24 | 2012-07-10 | Commvault Systems, Inc. | Application-aware and remote single instance data management |
| US8484162B2 (en) | 2008-06-24 | 2013-07-09 | Commvault Systems, Inc. | De-duplication systems and methods for application-specific data |
| US8335776B2 (en) | 2008-07-02 | 2012-12-18 | Commvault Systems, Inc. | Distributed indexing system for data storage |
| US8166263B2 (en) | 2008-07-03 | 2012-04-24 | Commvault Systems, Inc. | Continuous data protection over intermittent connections, such as continuous data backup for laptops or wireless devices |
| US8307177B2 (en) | 2008-09-05 | 2012-11-06 | Commvault Systems, Inc. | Systems and methods for management of virtualization data |
| US8725688B2 (en) | 2008-09-05 | 2014-05-13 | Commvault Systems, Inc. | Image level copy or restore, such as image level restore without knowledge of data object metadata |
| US20100070474A1 (en) | 2008-09-12 | 2010-03-18 | Lad Kamleshkumar K | Transferring or migrating portions of data objects, such as block-level data migration or chunk-based data migration |
| US20100070466A1 (en) | 2008-09-15 | 2010-03-18 | Anand Prahlad | Data transfer techniques within data storage devices, such as network attached storage performing data migration |
| US9015181B2 (en) | 2008-09-26 | 2015-04-21 | Commvault Systems, Inc. | Systems and methods for managing single instancing data |
| WO2010036754A1 (en) | 2008-09-26 | 2010-04-01 | Commvault Systems, Inc. | Systems and methods for managing single instancing data |
| US8341132B2 (en) * | 2008-10-01 | 2012-12-25 | Ca, Inc. | System and method for applying deltas in a version control system |
| US9178842B2 (en) | 2008-11-05 | 2015-11-03 | Commvault Systems, Inc. | Systems and methods for monitoring messaging applications for compliance with a policy |
| US8412677B2 (en) | 2008-11-26 | 2013-04-02 | Commvault Systems, Inc. | Systems and methods for byte-level or quasi byte-level single instancing |
| US9495382B2 (en) | 2008-12-10 | 2016-11-15 | Commvault Systems, Inc. | Systems and methods for performing discrete data replication |
| US8204859B2 (en) | 2008-12-10 | 2012-06-19 | Commvault Systems, Inc. | Systems and methods for managing replicated database data |
| US8434131B2 (en) | 2009-03-20 | 2013-04-30 | Commvault Systems, Inc. | Managing connections in a data storage system |
| US8401996B2 (en) | 2009-03-30 | 2013-03-19 | Commvault Systems, Inc. | Storing a variable number of instances of data objects |
| US8578120B2 (en) | 2009-05-22 | 2013-11-05 | Commvault Systems, Inc. | Block-level single instancing |
| JP2009245448A (en) * | 2009-06-15 | 2009-10-22 | Fujitsu Ltd | Data restoration device |
| US8612439B2 (en) | 2009-06-30 | 2013-12-17 | Commvault Systems, Inc. | Performing data storage operations in a cloud storage environment, including searching, encryption and indexing |
| US8930306B1 (en) | 2009-07-08 | 2015-01-06 | Commvault Systems, Inc. | Synchronized data deduplication |
| US9069751B1 (en) | 2009-07-21 | 2015-06-30 | Exelis, Inc. | Systems and methods for managing document pedigrees |
| US8706867B2 (en) | 2011-03-31 | 2014-04-22 | Commvault Systems, Inc. | Realtime streaming of multimedia content from secondary storage devices |
| US9092500B2 (en) | 2009-09-03 | 2015-07-28 | Commvault Systems, Inc. | Utilizing snapshots for access to databases and other applications |
| US8719767B2 (en) | 2011-03-31 | 2014-05-06 | Commvault Systems, Inc. | Utilizing snapshots to provide builds to developer computing devices |
| US8433682B2 (en) | 2009-12-31 | 2013-04-30 | Commvault Systems, Inc. | Systems and methods for analyzing snapshots |
| US9063932B2 (en) | 2009-12-18 | 2015-06-23 | Vertafore, Inc. | Apparatus, method and article to manage electronic or digital documents in a networked environment |
| US8700682B2 (en) | 2009-12-24 | 2014-04-15 | Vertafore, Inc. | Systems, methods and articles for template based generation of markup documents to access back office systems |
| EP2519872A4 (en) | 2009-12-31 | 2015-08-26 | Commvault Systems Inc | Systems and methods for performing data management operations using snapshots |
| WO2011082113A1 (en) | 2009-12-31 | 2011-07-07 | Commvault Systems, Inc. | Asynchronous methods of data classification using change journals and other data structures |
| US8504517B2 (en) | 2010-03-29 | 2013-08-06 | Commvault Systems, Inc. | Systems and methods for selective data replication |
| US8504515B2 (en) | 2010-03-30 | 2013-08-06 | Commvault Systems, Inc. | Stubbing systems and methods in a data replication environment |
| US8352422B2 (en) | 2010-03-30 | 2013-01-08 | Commvault Systems, Inc. | Data restore systems and methods in a replication environment |
| US8725698B2 (en) | 2010-03-30 | 2014-05-13 | Commvault Systems, Inc. | Stub file prioritization in a data replication system |
| US8572038B2 (en) | 2010-05-28 | 2013-10-29 | Commvault Systems, Inc. | Systems and methods for performing data replication |
| US11449394B2 (en) | 2010-06-04 | 2022-09-20 | Commvault Systems, Inc. | Failover systems and methods for performing backup operations, including heterogeneous indexing and load balancing of backup and indexing resources |
| US8364652B2 (en) | 2010-09-30 | 2013-01-29 | Commvault Systems, Inc. | Content aligned block-based deduplication |
| US8572340B2 (en) | 2010-09-30 | 2013-10-29 | Commvault Systems, Inc. | Systems and methods for retaining and using data block signatures in data protection operations |
| US9244779B2 (en) | 2010-09-30 | 2016-01-26 | Commvault Systems, Inc. | Data recovery operations, such as recovery from modified network data management protocol data |
| EP2622469B1 (en) | 2010-09-30 | 2019-11-13 | Commvault Systems, Inc. | Efficient data management improvements, such as docking limited-feature data management modules to a full-featured data management system |
| US8935492B2 (en) | 2010-09-30 | 2015-01-13 | Commvault Systems, Inc. | Archiving data objects using secondary copies |
| JP5630190B2 (en) * | 2010-10-06 | 2014-11-26 | 富士通株式会社 | Update management apparatus, update management method, and update management program |
| US9384198B2 (en) | 2010-12-10 | 2016-07-05 | Vertafore, Inc. | Agency management system and content management system integration |
| US20120150818A1 (en) | 2010-12-14 | 2012-06-14 | Commvault Systems, Inc. | Client-side repository in a networked deduplicated storage system |
| US9020900B2 (en) | 2010-12-14 | 2015-04-28 | Commvault Systems, Inc. | Distributed deduplicated storage system |
| US9021198B1 (en) | 2011-01-20 | 2015-04-28 | Commvault Systems, Inc. | System and method for sharing SAN storage |
| JP2012173780A (en) * | 2011-02-17 | 2012-09-10 | Hitachi Solutions Ltd | File configuration management system |
| US8719264B2 (en) | 2011-03-31 | 2014-05-06 | Commvault Systems, Inc. | Creating secondary copies of data based on searches for content |
| US8849762B2 (en) | 2011-03-31 | 2014-09-30 | Commvault Systems, Inc. | Restoring computing environments, such as autorecovery of file systems at certain points in time |
| US8731973B2 (en) | 2011-04-19 | 2014-05-20 | Vertafore, Inc. | Overlaying images in automated insurance policy form generation |
| US9461881B2 (en) | 2011-09-30 | 2016-10-04 | Commvault Systems, Inc. | Migration of existing computing systems to cloud computing sites or virtual machines |
| US9116633B2 (en) | 2011-09-30 | 2015-08-25 | Commvault Systems, Inc. | Information management of virtual machines having mapped storage devices |
| US9372827B2 (en) | 2011-09-30 | 2016-06-21 | Commvault Systems, Inc. | Migration of an existing computing system to new hardware |
| US9298715B2 (en) | 2012-03-07 | 2016-03-29 | Commvault Systems, Inc. | Data storage system utilizing proxy device for storage operations |
| US9471578B2 (en) | 2012-03-07 | 2016-10-18 | Commvault Systems, Inc. | Data storage system utilizing proxy device for storage operations |
| US8950009B2 (en) | 2012-03-30 | 2015-02-03 | Commvault Systems, Inc. | Information management of data associated with multiple cloud services |
| US9639297B2 (en) | 2012-03-30 | 2017-05-02 | Commvault Systems, Inc | Shared network-available storage that permits concurrent data access |
| US9020890B2 (en) | 2012-03-30 | 2015-04-28 | Commvault Systems, Inc. | Smart archiving and data previewing for mobile devices |
| US9262496B2 (en) | 2012-03-30 | 2016-02-16 | Commvault Systems, Inc. | Unified access to personal data |
| AU2013202553B2 (en) | 2012-03-30 | 2015-10-01 | Commvault Systems, Inc. | Information management of mobile device data |
| US10157184B2 (en) | 2012-03-30 | 2018-12-18 | Commvault Systems, Inc. | Data previewing before recalling large data files |
| US9063938B2 (en) | 2012-03-30 | 2015-06-23 | Commvault Systems, Inc. | Search filtered file system using secondary storage, including multi-dimensional indexing and searching of archived files |
| US9342537B2 (en) | 2012-04-23 | 2016-05-17 | Commvault Systems, Inc. | Integrated snapshot interface for a data storage system |
| US8892523B2 (en) | 2012-06-08 | 2014-11-18 | Commvault Systems, Inc. | Auto summarization of content |
| US9251186B2 (en) | 2012-06-13 | 2016-02-02 | Commvault Systems, Inc. | Backup using a client-side signature repository in a networked storage system |
| US10268662B2 (en) * | 2012-09-10 | 2019-04-23 | The Boeing Company | Panoptic visualization of a document according to the structure thereof |
| US9311121B2 (en) | 2012-12-21 | 2016-04-12 | Commvault Systems, Inc. | Archiving virtual machines in a data storage system |
| US20140181085A1 (en) | 2012-12-21 | 2014-06-26 | Commvault Systems, Inc. | Data storage system for analysis of data across heterogeneous information management systems |
| US9740702B2 (en) | 2012-12-21 | 2017-08-22 | Commvault Systems, Inc. | Systems and methods to identify unprotected virtual machines |
| US10379988B2 (en) | 2012-12-21 | 2019-08-13 | Commvault Systems, Inc. | Systems and methods for performance monitoring |
| US9069799B2 (en) | 2012-12-27 | 2015-06-30 | Commvault Systems, Inc. | Restoration of centralized data storage manager, such as data storage manager in a hierarchical data storage system |
| US9021452B2 (en) | 2012-12-27 | 2015-04-28 | Commvault Systems, Inc. | Automatic identification of storage requirements, such as for use in selling data storage management solutions |
| US9633216B2 (en) | 2012-12-27 | 2017-04-25 | Commvault Systems, Inc. | Application of information management policies based on operation with a geographic entity |
| US9378035B2 (en) | 2012-12-28 | 2016-06-28 | Commvault Systems, Inc. | Systems and methods for repurposing virtual machines |
| US10346259B2 (en) | 2012-12-28 | 2019-07-09 | Commvault Systems, Inc. | Data recovery using a cloud-based remote data recovery center |
| US9633022B2 (en) | 2012-12-28 | 2017-04-25 | Commvault Systems, Inc. | Backup and restoration for a deduplicated file system |
| US20140196039A1 (en) | 2013-01-08 | 2014-07-10 | Commvault Systems, Inc. | Virtual machine categorization system and method |
| US20140201162A1 (en) | 2013-01-11 | 2014-07-17 | Commvault Systems, Inc. | Systems and methods to restore selected files from block-level backup for virtual machines |
| US9633033B2 (en) | 2013-01-11 | 2017-04-25 | Commvault Systems, Inc. | High availability distributed deduplicated storage system |
| US9886346B2 (en) | 2013-01-11 | 2018-02-06 | Commvault Systems, Inc. | Single snapshot for multiple agents |
| US20140201140A1 (en) | 2013-01-11 | 2014-07-17 | Commvault Systems, Inc. | Data synchronization management |
| US9286110B2 (en) | 2013-01-14 | 2016-03-15 | Commvault Systems, Inc. | Seamless virtual machine recall in a data storage system |
| US9459968B2 (en) | 2013-03-11 | 2016-10-04 | Commvault Systems, Inc. | Single index to query multiple backup formats |
| US20140281518A1 (en) | 2013-03-12 | 2014-09-18 | Commvault Systems, Inc. | Multi-tier file restoration |
| US9939981B2 (en) | 2013-09-12 | 2018-04-10 | Commvault Systems, Inc. | File manager integration with virtualization in an information management system with an enhanced storage manager, including user control and storage management of virtual machines |
| US20150100552A1 (en) * | 2013-10-07 | 2015-04-09 | QQ Solutions Inc. | Managing non-committed computerized workflows |
| US9898451B2 (en) | 2013-11-26 | 2018-02-20 | Adobe Systems Incorporated | Content adaptation based on selected reviewer comment |
| US9507814B2 (en) | 2013-12-10 | 2016-11-29 | Vertafore, Inc. | Bit level comparator systems and methods |
| US9367435B2 (en) | 2013-12-12 | 2016-06-14 | Vertafore, Inc. | Integration testing method and system for web services |
| US10949382B2 (en) | 2014-01-15 | 2021-03-16 | Commvault Systems, Inc. | User-centric interfaces for information management systems |
| US9639426B2 (en) | 2014-01-24 | 2017-05-02 | Commvault Systems, Inc. | Single snapshot for multiple applications |
| US9632874B2 (en) | 2014-01-24 | 2017-04-25 | Commvault Systems, Inc. | Database application backup in single snapshot for multiple applications |
| US9753812B2 (en) | 2014-01-24 | 2017-09-05 | Commvault Systems, Inc. | Generating mapping information for single snapshot for multiple applications |
| US9495251B2 (en) | 2014-01-24 | 2016-11-15 | Commvault Systems, Inc. | Snapshot readiness checking and reporting |
| US10324897B2 (en) | 2014-01-27 | 2019-06-18 | Commvault Systems, Inc. | Techniques for serving archived electronic mail |
| US9798596B2 (en) | 2014-02-27 | 2017-10-24 | Commvault Systems, Inc. | Automatic alert escalation for an information management system |
| US9648100B2 (en) | 2014-03-05 | 2017-05-09 | Commvault Systems, Inc. | Cross-system storage management for transferring data across autonomous information management systems |
| US9633056B2 (en) | 2014-03-17 | 2017-04-25 | Commvault Systems, Inc. | Maintaining a deduplication database |
| JP5835381B2 (en) * | 2014-03-17 | 2015-12-24 | 富士ゼロックス株式会社 | Image processing apparatus and program |
| US10380072B2 (en) | 2014-03-17 | 2019-08-13 | Commvault Systems, Inc. | Managing deletions from a deduplication database |
| EP2921970B1 (en) * | 2014-03-18 | 2017-04-26 | smartwork solutions GmbH | Method and system for editing virtual documents |
| US9563518B2 (en) | 2014-04-02 | 2017-02-07 | Commvault Systems, Inc. | Information management by a media agent in the absence of communications with a storage manager |
| US9823978B2 (en) | 2014-04-16 | 2017-11-21 | Commvault Systems, Inc. | User-level quota management of data objects stored in information management systems |
| US9740574B2 (en) | 2014-05-09 | 2017-08-22 | Commvault Systems, Inc. | Load balancing across multiple data paths |
| US9848045B2 (en) | 2014-05-27 | 2017-12-19 | Commvault Systems, Inc. | Offline messaging between a repository storage operation cell and remote storage operation cells via an intermediary media agent |
| US9760446B2 (en) | 2014-06-11 | 2017-09-12 | Micron Technology, Inc. | Conveying value of implementing an integrated data management and protection system |
| US20160019317A1 (en) | 2014-07-16 | 2016-01-21 | Commvault Systems, Inc. | Volume or virtual machine level backup and generating placeholders for virtual machine files |
| US11249858B2 (en) | 2014-08-06 | 2022-02-15 | Commvault Systems, Inc. | Point-in-time backups of a production application made accessible over fibre channel and/or ISCSI as data sources to a remote application by representing the backups as pseudo-disks operating apart from the production application and its host |
| US9852026B2 (en) | 2014-08-06 | 2017-12-26 | Commvault Systems, Inc. | Efficient application recovery in an information management system based on a pseudo-storage-device driver |
| US9747556B2 (en) | 2014-08-20 | 2017-08-29 | Vertafore, Inc. | Automated customized web portal template generation systems and methods |
| US9774672B2 (en) | 2014-09-03 | 2017-09-26 | Commvault Systems, Inc. | Consolidated processing of storage-array commands by a snapshot-control media agent |
| US10042716B2 (en) | 2014-09-03 | 2018-08-07 | Commvault Systems, Inc. | Consolidated processing of storage-array commands using a forwarder media agent in conjunction with a snapshot-control media agent |
| US9405928B2 (en) | 2014-09-17 | 2016-08-02 | Commvault Systems, Inc. | Deriving encryption rules based on file content |
| US9436555B2 (en) | 2014-09-22 | 2016-09-06 | Commvault Systems, Inc. | Efficient live-mount of a backed up virtual machine in a storage management system |
| US9710465B2 (en) | 2014-09-22 | 2017-07-18 | Commvault Systems, Inc. | Efficiently restoring execution of a backed up virtual machine based on coordination with virtual-machine-file-relocation operations |
| US9417968B2 (en) | 2014-09-22 | 2016-08-16 | Commvault Systems, Inc. | Efficiently restoring execution of a backed up virtual machine based on coordination with virtual-machine-file-relocation operations |
| US9444811B2 (en) | 2014-10-21 | 2016-09-13 | Commvault Systems, Inc. | Using an enhanced data agent to restore backed up data across autonomous storage management systems |
| US9575673B2 (en) | 2014-10-29 | 2017-02-21 | Commvault Systems, Inc. | Accessing a file system using tiered deduplication |
| US10776209B2 (en) | 2014-11-10 | 2020-09-15 | Commvault Systems, Inc. | Cross-platform virtual machine backup and replication |
| US9448731B2 (en) | 2014-11-14 | 2016-09-20 | Commvault Systems, Inc. | Unified snapshot storage management |
| US9648105B2 (en) | 2014-11-14 | 2017-05-09 | Commvault Systems, Inc. | Unified snapshot storage management, using an enhanced storage manager and enhanced media agents |
| US20160142485A1 (en) | 2014-11-19 | 2016-05-19 | Commvault Systems, Inc. | Migration to cloud storage from backup |
| US9983936B2 (en) | 2014-11-20 | 2018-05-29 | Commvault Systems, Inc. | Virtual machine change block tracking |
| US9904481B2 (en) | 2015-01-23 | 2018-02-27 | Commvault Systems, Inc. | Scalable auxiliary copy processing in a storage management system using media agent resources |
| US9898213B2 (en) | 2015-01-23 | 2018-02-20 | Commvault Systems, Inc. | Scalable auxiliary copy processing using media agent resources |
| US10313243B2 (en) | 2015-02-24 | 2019-06-04 | Commvault Systems, Inc. | Intelligent local management of data stream throttling in secondary-copy operations |
| US10956299B2 (en) | 2015-02-27 | 2021-03-23 | Commvault Systems, Inc. | Diagnosing errors in data storage and archiving in a cloud or networking environment |
| US9928144B2 (en) | 2015-03-30 | 2018-03-27 | Commvault Systems, Inc. | Storage management of data using an open-archive architecture, including streamlined access to primary data originally stored on network-attached storage and archived to secondary storage |
| US10339106B2 (en) | 2015-04-09 | 2019-07-02 | Commvault Systems, Inc. | Highly reusable deduplication database after disaster recovery |
| US10311150B2 (en) | 2015-04-10 | 2019-06-04 | Commvault Systems, Inc. | Using a Unix-based file system to manage and serve clones to windows-based computing clients |
| US10324914B2 (en) | 2015-05-20 | 2019-06-18 | Commvalut Systems, Inc. | Handling user queries against production and archive storage systems, such as for enterprise customers having large and/or numerous files |
| US20160350391A1 (en) | 2015-05-26 | 2016-12-01 | Commvault Systems, Inc. | Replication using deduplicated secondary copy data |
| US9563514B2 (en) | 2015-06-19 | 2017-02-07 | Commvault Systems, Inc. | Assignment of proxies for virtual-machine secondary copy operations including streaming backup jobs |
| US10084873B2 (en) | 2015-06-19 | 2018-09-25 | Commvault Systems, Inc. | Assignment of data agent proxies for executing virtual-machine secondary copy operations including streaming backup jobs |
| US10275320B2 (en) | 2015-06-26 | 2019-04-30 | Commvault Systems, Inc. | Incrementally accumulating in-process performance data and hierarchical reporting thereof for a data stream in a secondary copy operation |
| US9766825B2 (en) | 2015-07-22 | 2017-09-19 | Commvault Systems, Inc. | Browse and restore for block-level backups |
| US10101913B2 (en) | 2015-09-02 | 2018-10-16 | Commvault Systems, Inc. | Migrating data to disk without interrupting running backup operations |
| US9600400B1 (en) | 2015-10-29 | 2017-03-21 | Vertafore, Inc. | Performance testing of web application components using image differentiation |
| US10176036B2 (en) | 2015-10-29 | 2019-01-08 | Commvault Systems, Inc. | Monitoring, diagnosing, and repairing a management database in a data storage management system |
| US10310953B2 (en) | 2015-12-30 | 2019-06-04 | Commvault Systems, Inc. | System for redirecting requests after a secondary storage computing device failure |
| US10296368B2 (en) | 2016-03-09 | 2019-05-21 | Commvault Systems, Inc. | Hypervisor-independent block-level live browse for access to backed up virtual machine (VM) data and hypervisor-free file-level recovery (block-level pseudo-mount) |
| US10565067B2 (en) | 2016-03-09 | 2020-02-18 | Commvault Systems, Inc. | Virtual server cloud file system for virtual machine backup from cloud operations |
| US10503753B2 (en) | 2016-03-10 | 2019-12-10 | Commvault Systems, Inc. | Snapshot replication operations based on incremental block change tracking |
| US10417102B2 (en) | 2016-09-30 | 2019-09-17 | Commvault Systems, Inc. | Heartbeat monitoring of virtual machines for initiating failover operations in a data storage management system, including virtual machine distribution logic |
| US10540516B2 (en) | 2016-10-13 | 2020-01-21 | Commvault Systems, Inc. | Data protection within an unsecured storage environment |
| WO2018073865A1 (en) * | 2016-10-17 | 2018-04-26 | 三菱電機株式会社 | Program development assistance device, program development assistance method, program development assistance program, and recording medium |
| US10162528B2 (en) | 2016-10-25 | 2018-12-25 | Commvault Systems, Inc. | Targeted snapshot based on virtual machine location |
| US10152251B2 (en) | 2016-10-25 | 2018-12-11 | Commvault Systems, Inc. | Targeted backup of virtual machine |
| US10389810B2 (en) | 2016-11-02 | 2019-08-20 | Commvault Systems, Inc. | Multi-threaded scanning of distributed file systems |
| US10922189B2 (en) | 2016-11-02 | 2021-02-16 | Commvault Systems, Inc. | Historical network data-based scanning thread generation |
| US10678758B2 (en) | 2016-11-21 | 2020-06-09 | Commvault Systems, Inc. | Cross-platform virtual machine data and memory backup and replication |
| US10838821B2 (en) | 2017-02-08 | 2020-11-17 | Commvault Systems, Inc. | Migrating content and metadata from a backup system |
| US10740193B2 (en) | 2017-02-27 | 2020-08-11 | Commvault Systems, Inc. | Hypervisor-independent reference copies of virtual machine payload data based on block-level pseudo-mount |
| US10459666B2 (en) | 2017-03-03 | 2019-10-29 | Commvault Systems, Inc. | Using storage managers in respective data storage management systems for license distribution, compliance, and updates |
| US10949308B2 (en) | 2017-03-15 | 2021-03-16 | Commvault Systems, Inc. | Application aware backup of virtual machines |
| US11032350B2 (en) | 2017-03-15 | 2021-06-08 | Commvault Systems, Inc. | Remote commands framework to control clients |
| US20180276085A1 (en) | 2017-03-24 | 2018-09-27 | Commvault Systems, Inc. | Virtual machine recovery point generation |
| US10891069B2 (en) | 2017-03-27 | 2021-01-12 | Commvault Systems, Inc. | Creating local copies of data stored in online data repositories |
| US10776329B2 (en) | 2017-03-28 | 2020-09-15 | Commvault Systems, Inc. | Migration of a database management system to cloud storage |
| US11108858B2 (en) | 2017-03-28 | 2021-08-31 | Commvault Systems, Inc. | Archiving mail servers via a simple mail transfer protocol (SMTP) server |
| US11074140B2 (en) | 2017-03-29 | 2021-07-27 | Commvault Systems, Inc. | Live browsing of granular mailbox data |
| US10387073B2 (en) | 2017-03-29 | 2019-08-20 | Commvault Systems, Inc. | External dynamic virtual machine synchronization |
| US11074138B2 (en) | 2017-03-29 | 2021-07-27 | Commvault Systems, Inc. | Multi-streaming backup operations for mailboxes |
| US11010261B2 (en) | 2017-03-31 | 2021-05-18 | Commvault Systems, Inc. | Dynamically allocating streams during restoration of data |
| US10853195B2 (en) | 2017-03-31 | 2020-12-01 | Commvault Systems, Inc. | Granular restoration of virtual machine application data |
| US10552294B2 (en) | 2017-03-31 | 2020-02-04 | Commvault Systems, Inc. | Management of internet of things devices |
| US11221939B2 (en) | 2017-03-31 | 2022-01-11 | Commvault Systems, Inc. | Managing data from internet of things devices in a vehicle |
| US11294786B2 (en) | 2017-03-31 | 2022-04-05 | Commvault Systems, Inc. | Management of internet of things devices |
| US10984041B2 (en) | 2017-05-11 | 2021-04-20 | Commvault Systems, Inc. | Natural language processing integrated with database and data storage management |
| US10664352B2 (en) | 2017-06-14 | 2020-05-26 | Commvault Systems, Inc. | Live browsing of backed up data residing on cloned disks |
| US10742735B2 (en) | 2017-12-12 | 2020-08-11 | Commvault Systems, Inc. | Enhanced network attached storage (NAS) services interfacing to cloud storage |
| US10831591B2 (en) | 2018-01-11 | 2020-11-10 | Commvault Systems, Inc. | Remedial action based on maintaining process awareness in data storage management |
| US10795927B2 (en) | 2018-02-05 | 2020-10-06 | Commvault Systems, Inc. | On-demand metadata extraction of clinical image data |
| US10740022B2 (en) | 2018-02-14 | 2020-08-11 | Commvault Systems, Inc. | Block-level live browsing and private writable backup copies using an ISCSI server |
| US10642886B2 (en) | 2018-02-14 | 2020-05-05 | Commvault Systems, Inc. | Targeted search of backup data using facial recognition |
| US10877928B2 (en) | 2018-03-07 | 2020-12-29 | Commvault Systems, Inc. | Using utilities injected into cloud-based virtual machines for speeding up virtual machine backup operations |
| US10789387B2 (en) | 2018-03-13 | 2020-09-29 | Commvault Systems, Inc. | Graphical representation of an information management system |
| US10891198B2 (en) | 2018-07-30 | 2021-01-12 | Commvault Systems, Inc. | Storing data to cloud libraries in cloud native formats |
| US11159469B2 (en) | 2018-09-12 | 2021-10-26 | Commvault Systems, Inc. | Using machine learning to modify presentation of mailbox objects |
| US11010258B2 (en) | 2018-11-27 | 2021-05-18 | Commvault Systems, Inc. | Generating backup copies through interoperability between components of a data storage management system and appliances for data storage and deduplication |
| US11200124B2 (en) | 2018-12-06 | 2021-12-14 | Commvault Systems, Inc. | Assigning backup resources based on failover of partnered data storage servers in a data storage management system |
| US10860443B2 (en) | 2018-12-10 | 2020-12-08 | Commvault Systems, Inc. | Evaluation and reporting of recovery readiness in a data storage management system |
| US20200192572A1 (en) | 2018-12-14 | 2020-06-18 | Commvault Systems, Inc. | Disk usage growth prediction system |
| US11698727B2 (en) | 2018-12-14 | 2023-07-11 | Commvault Systems, Inc. | Performing secondary copy operations based on deduplication performance |
| US10996974B2 (en) | 2019-01-30 | 2021-05-04 | Commvault Systems, Inc. | Cross-hypervisor live mount of backed up virtual machine data, including management of cache storage for virtual machine data |
| US10768971B2 (en) | 2019-01-30 | 2020-09-08 | Commvault Systems, Inc. | Cross-hypervisor live mount of backed up virtual machine data |
| JP7183092B2 (en) * | 2019-03-25 | 2022-12-05 | アズビル株式会社 | SOURCE INFORMATION MANAGEMENT DEVICE AND SOURCE INFORMATION MANAGEMENT METHOD |
| US20200327017A1 (en) | 2019-04-10 | 2020-10-15 | Commvault Systems, Inc. | Restore using deduplicated secondary copy data |
| US11494273B2 (en) | 2019-04-30 | 2022-11-08 | Commvault Systems, Inc. | Holistically protecting serverless applications across one or more cloud computing environments |
| US11463264B2 (en) | 2019-05-08 | 2022-10-04 | Commvault Systems, Inc. | Use of data block signatures for monitoring in an information management system |
| US11461184B2 (en) | 2019-06-17 | 2022-10-04 | Commvault Systems, Inc. | Data storage management system for protecting cloud-based data including on-demand protection, recovery, and migration of databases-as-a-service and/or serverless database management systems |
| US11308034B2 (en) | 2019-06-27 | 2022-04-19 | Commvault Systems, Inc. | Continuously run log backup with minimal configuration and resource usage from the source machine |
| US20210011816A1 (en) | 2019-07-10 | 2021-01-14 | Commvault Systems, Inc. | Preparing containerized applications for backup using a backup services container in a container-orchestration pod |
| US11042318B2 (en) | 2019-07-29 | 2021-06-22 | Commvault Systems, Inc. | Block-level data replication |
| US20210173811A1 (en) | 2019-12-04 | 2021-06-10 | Commvault Systems, Inc. | Optimizing the restoration of deduplicated data stored in multi-node replicated file systems |
| US11467753B2 (en) | 2020-02-14 | 2022-10-11 | Commvault Systems, Inc. | On-demand restore of virtual machine data |
| US11321188B2 (en) | 2020-03-02 | 2022-05-03 | Commvault Systems, Inc. | Platform-agnostic containerized application data protection |
| US11422900B2 (en) | 2020-03-02 | 2022-08-23 | Commvault Systems, Inc. | Platform-agnostic containerized application data protection |
| US11442768B2 (en) | 2020-03-12 | 2022-09-13 | Commvault Systems, Inc. | Cross-hypervisor live recovery of virtual machines |
| US11099956B1 (en) | 2020-03-26 | 2021-08-24 | Commvault Systems, Inc. | Snapshot-based disaster recovery orchestration of virtual machine failover and failback operations |
| US11500669B2 (en) | 2020-05-15 | 2022-11-15 | Commvault Systems, Inc. | Live recovery of virtual machines in a public cloud computing environment |
| US11687424B2 (en) | 2020-05-28 | 2023-06-27 | Commvault Systems, Inc. | Automated media agent state management |
| US11494417B2 (en) | 2020-08-07 | 2022-11-08 | Commvault Systems, Inc. | Automated email classification in an information management system |
| US11314687B2 (en) | 2020-09-24 | 2022-04-26 | Commvault Systems, Inc. | Container data mover for migrating data between distributed data storage systems integrated with application orchestrators |
| US11656951B2 (en) | 2020-10-28 | 2023-05-23 | Commvault Systems, Inc. | Data loss vulnerability detection |
| US11803528B2 (en) * | 2021-02-02 | 2023-10-31 | Jpmorgan Chase Bank, N.A. | Method and apparatus for generating data structure describing how taxonomies evolve and usage algorithm thereof |
| US11604706B2 (en) | 2021-02-02 | 2023-03-14 | Commvault Systems, Inc. | Back up and restore related data on different cloud storage tiers |
| US11593223B1 (en) | 2021-09-02 | 2023-02-28 | Commvault Systems, Inc. | Using resource pool administrative entities in a data storage management system to provide shared infrastructure to tenants |
| CN115220679B (en) * | 2021-09-08 | 2023-09-22 | 广州汽车集团股份有限公司 | Vehicle-mounted multimedia system and screen initialization method thereof |
| US11809285B2 (en) | 2022-02-09 | 2023-11-07 | Commvault Systems, Inc. | Protecting a management database of a data storage management system to meet a recovery point objective (RPO) |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5671428A (en) * | 1991-08-28 | 1997-09-23 | Kabushiki Kaisha Toshiba | Collaborative document processing system with version and comment management |
| JPH06250895A (en) * | 1993-02-26 | 1994-09-09 | Fujitsu Ltd | Structured data base system |
| JPH0954735A (en) * | 1995-06-07 | 1997-02-25 | Fuji Xerox Co Ltd | Method and device for information processing |
| JPH09128380A (en) * | 1995-10-30 | 1997-05-16 | Matsushita Electric Ind Co Ltd | Document storing and managing system |
| US5890176A (en) * | 1996-04-24 | 1999-03-30 | International Business Machines Corp. | Object-oriented document version tracking method and apparatus |
| US6112024A (en) * | 1996-10-02 | 2000-08-29 | Sybase, Inc. | Development system providing methods for managing different versions of objects with a meta model |
| US5983242A (en) * | 1997-07-01 | 1999-11-09 | Microsoft Corporation | Method and system for preserving document integrity |
| JPH11143754A (en) | 1997-11-05 | 1999-05-28 | Hitachi Ltd | Version information and constitution information display method and device therefor, and computer readable recording medium for recording version information and constitution information display program |
-
1997
- 1997-11-05 JP JP31901197A patent/JPH11143754A/en active Pending
-
1998
- 1998-11-02 CA CA002252472A patent/CA2252472A1/en not_active Abandoned
- 1998-11-02 EP EP98120740A patent/EP0915427A3/en not_active Ceased
- 1998-11-04 US US09/185,646 patent/US6301592B1/en not_active Expired - Fee Related
-
2001
- 2001-09-06 US US09/946,345 patent/US6493732B2/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| JPH11143754A (en) | 1999-05-28 |
| US20020007365A1 (en) | 2002-01-17 |
| EP0915427A3 (en) | 2004-01-28 |
| EP0915427A2 (en) | 1999-05-12 |
| US6493732B2 (en) | 2002-12-10 |
| US6301592B1 (en) | 2001-10-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6301592B1 (en) | Method of and an apparatus for displaying version information and configuration information and a computer-readable recording medium on which a version and configuration information display program is recorded | |
| US20090031227A1 (en) | Intelligent screen capture and interactive display tool | |
| JPH1124901A (en) | Method and system for analyzing and displaying program information | |
| JP2016218967A (en) | Information processing device, and information processing program | |
| JP2005301453A (en) | Medical report preparing device, medical report reference device, medical report preparing method, and program therefor | |
| US20080240683A1 (en) | Method and system to reproduce contents, and recording medium including program to reproduce contents | |
| JP2009508227A (en) | Browse mode designer | |
| JP2001337994A (en) | Thumbnail display system and method and recording medium with processing program therefor recorded therein | |
| TW200406692A (en) | Semiconductor test data analysis system | |
| JP2001306310A (en) | Method and device for assisting creation of gui part and application developing method | |
| Lease et al. | Using an issue-based hypertext system to capture the software life-cycle process | |
| JP2008140190A (en) | Program, apparatus and method for automatically generating screen configurations | |
| CN100438600C (en) | Video check system and method | |
| US7730105B2 (en) | Time sharing managing apparatus, document creating apparatus, document reading apparatus, time sharing managing method, document creating method, and document reading method | |
| JP2001256043A (en) | Correction history managing method and correction history management system of program source | |
| JPH08190569A (en) | Information presenter | |
| JP3175239B2 (en) | Multimedia information editing device | |
| JP2005108107A (en) | Method and apparatus for document processing | |
| JPH08153104A (en) | Hypermedia system and hypermedia document preparing and editing method | |
| WO2021084769A1 (en) | Attachment of sticky-note to and recovery of sticky-note from visualization data | |
| JP2006268314A (en) | Document processor, method, and program | |
| JP2007094453A (en) | Program development support system, program development support method and program | |
| JP2002287964A (en) | Screen input/output specification designing system, method and program | |
| JPH10333857A (en) | Information editing device | |
| JPH08221265A (en) | Supporting device for developing software |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |