System and method for managing objects between projects

• US 7,559,048 B1
• Filed: 06/19/2001
• Issued: 07/07/2009
• Est. Priority Date: 06/19/2001
• Status: Active Grant

• Current Assignee: Microstrategy Incorporated
• Original Assignee: Microstrategy Incorporated
• Inventors: Codini, Michael, Trundle, Steven S., Gay, Arturo, Yost, Kyle N., Hurwood, William, Warikoo, Abhimanyu, Bedell, Jeffrey A., Li, Benjamin Z., Martin, Fabrice, Ramachandran, Ramkumar
• Primary Examiner(s): Zhen; Li B
• Application Number:
  US09/883,508
• Time in Patent Office: 2,940 Days
• Field of Search: 717/100, 717/101, 717/120, 717/122, 719/310
• US Class Current: 717/101
• CPC Class Codes: G06F 16/289 Object oriented databases

Abstract

A system and method for manipulating objects between related projects. Dependencies between object are checked as objects are moved between projects. The dependency review enables all dependent object to be copied simultaneously. The system and method facilitates the management of multiple stages of a project by permitting as object and all of its modified dependents to be easily copied from one stage to another.

Claims

1. A computer implemented method for managing groups of objects for use in a reporting system project comprising the steps of:

receiving a command to perform a selected function on a selected object;

automatically identifying dependent objects referred to by the selected object;

determining using a computer processor an appropriate manner of executing the selected function on the selected object;

determining using a computer processor appropriate functions to be performed on the dependent objects;

automatically causing the appropriate functions to be performed on the dependent objects;

automatically causing the execution of the selected function on the selected object in the appropriate manner;

wherein objects are grouped in projects and the selected function relates to manipulating objects within and between projects and wherein within each project each object has a unique identifier and a version identifier; and

wherein the step of receiving is a step of receiving a command to copy a selected object from a source project to a destination project.

2. The method of claim 1 wherein the unique identifier and version identifier of objects in the source project are similar to the unique identifier and version identifier of objects in the destination project.

3. The method of claim 1 wherein the step of determining an appropriate manner of executing the function includes the steps of:

determining, by comparing unique identifiers and version identifiers, whether the selected object exists in the destination project in an identical form and whether the selected object exists in the destination project in a modified form; and

selecting whether to copy the selected object from the source project to the destination project, to replace an object in the destination project with the selected object, and to keep an object in the destination project as is.

4. The method of claim 3 wherein the step of selecting includes prompting the user for a selection.

5. A system application stored on a computer-readable storage medium for managing objects within and between projects of a reporting system, the objects including unique identifiers and version identifiers that are similar between projects, the system application comprising:

a user interface for receiving a user command to manipulate a selected object;

an operational module interfacing with the projects for identifying dependent objects referred to by the selected object, determining an appropriate manner of executing the user command, determining appropriate functions to be performed on the dependent objects, performing the appropriate functions on dependent objects, and executing the user command in the appropriate manner;

wherein the operational module, upon receiving a user command to copy the selected object from a source project to a destination project, determines, by comparing the unique identifiers and the version identifiers, whether the selected object exists in the destination project in an identical form and whether the selected object exists in the destination project in a modified form; and

wherein the operational module communicates with the user interface to select whether to copy the selected object from the source project to the destination project, to replace an object in the destination object with the selected object, and to keep an object in the destination project as is.