Abstract: Mechanisms are provided for auto-generating reports based on metadata. Entities in databases may have some associated metadata, and this metadata may serve as the basis of the reports. Such reports may be generated not only automatically but also dynamically. The generation of reports may also be a function of the role traversal between entities, such that if a role indicates at most one instance of the target entity is related to an instance of the source entity, a single-type report can be created, whereas if the role indicates many instances of the target entity may be related, a different kind or report can be generated, namely, a multi-type report. Lastly, even though reports are auto-generated, such reports can be overridden or customized via user interfaces or application programming interfaces.

Abstract: A method of creating and defining complex functions and/or expressions that may be run against an entity relationship model. An anchor entity serves as a beginning point of the expression and determines what data that will be returned by the user-created expression within the context of a query. When a relationship from any entity is traversed, including the anchor entity, the role name for the target entity is displayed hierarchically beneath the entity it was navigated from. When an entity is selected, the relationships from this entity are shown as possible navigation paths. The user may select one of these paths to navigate and add to the query tree or chose a field from the field list. Entities can be dragged and dropped into a formula area to create the expression. Functions, and mathematical and logical operations can be performed on the entities and fields in creating the expression. The fields and entities can be filtered to refine the results retrieved by the expression.

Abstract: A graphical user interface and method of use thereof that allows users to interact with an entity relationship model. The user interface includes zones that allow users to navigate among the entities, roles and fields to create queries that are run against the model. Clicking on an entity in the shows the available fields for the entity. Users can drag and drop entities and fields onto a design surface to quickly and easily build queries. Rules are applied when either an entity or a field is dropped onto the design surface based upon the item being dropped (either an entity or a field), the position of the drop and also the properties that are associated with the item. Entities may be grouped and filtered to sort and limit the results of the query. After query is run, the results may be displayed in a separate area to the user.

Abstract: A dimension member of a report is slid to produce a new view of the report that corresponds to the slid dimension. The dimension member sliding allows navigation of a dimension of the data by members in a pattern that is not hierarchical. The view of the report corresponds to a hierarchy tree that is decomposed into a matrix. The next dimension members are determined using the matrix and the dimensionally slid view of the report is generated.

Abstract: Method and system for generating summary scores from heterogeneous measures retrieved from multi-dimensional data structures for monitoring organizational performance. Scorecards are created for each group of tree-structured measures branching from Parent nodes to child nodes based on Key Performance Indicators (KPI). Scores for each parent node may be obtained by rolling up scores for child nodes reporting to the parent node. KPI's at the lowest level are mapped on first scale, then mapped to a normalized scale, and score values determined. KPI scores are weight-averaged for roll-up to a parent node determining the score for that node. Multiple parent nodes may be rolled-up to a higher level node in a similar way. Multiple dimensions of the measure such as geographic and temporal may be scored simultaneously.

Abstract: A system, including a planning module, a control module and a receiver module, configured to schedule display of one or more advertising impressions of available advertising inventory. The planning module enables scheduling a requested quantity of advertising impressions in accordance with target criteria. Further, the planning module enables selecting an advertising impression goal for advertisement, assigning an advertising type and defining a weight for the advertisements. The control module receives the schedule, the advertising type and the defined weights and generates one or more metadata files that contain target criteria, advertising type and weights for the advertisements. The one or more metadata files, with the advertisements, are delivered to the receiver module that is configured to define a display frequency for the advertisements based upon one or more of the metadata files.