Patent application number | Description | Published |
20080282188 | Shape elasticity in visual layout - Resizing and/or repositioning a target object related by containment to one or more related object laid out on a computer user interface. Original sizes and/or positions of the related objects to the target object resized and/or repositioned are stored. During the resize and/or reposition operation of the target object, an impact on a related object is calculated based upon a change from the stored original sizes and/or positions of the related object. | 11-13-2008 |
20100223264 | REPORTING INCLUDING FILLING DATA GAPS AND HANDLING UNCATEGORIZED DATA - A reporting system is described herein that allows a report author to declare data reporting structures that specify to a reporting application how to dynamically categorize data with changing or potentially unknown characteristics. The reporting system may extend RDL and the data grouping provided by Microsoft SQL Server Reporting Services by adding new elements to the XML-based RDL schema. The reporting system allows the report author to specify for the system to fill gaps in the data, so that the report has a similar layout even as data changes from period to period. The reporting system also allows the report author to specify whether data that does not fit any predefined group bucket is displayed in a report. Thus, the reporting system allows unsophisticated database users to define reports that group data consistently regardless of missing values or other changes in the underlying data. | 09-02-2010 |
20110246447 | INLINE DATA CORRELATION AND HIERARCHICAL DATASETS - Architecture which provides that certain data-bound objects in the report can be configured by the report author to use data from a specific query result rather than take data from the containing data bound object. The report author defines a relationship between the data in the contained object and the data in the container, allowing instances of the descendant object to be correlated with instances of the ancestor object. This relationship can be either explicit with join conditions or implicit due to an intrinsic hierarchical relationship between the query results. | 10-06-2011 |
20120066249 | UTILIZING HIERARCHY METADATA TO IMPROVE PATH SELECTION - Embodiments are directed to implementing hierarchy metadata to improve relational model default path selection heuristics. A computer system receives a database query from a user. The query is configured to return a portion of requested data stored in the database. The database includes multiple different data entities related to each other via different relationship paths. The computer system accesses hierarchy metadata that describes various database hierarchies, each hierarchy including multiple data entities. The computer system determines an optimal path between the related data entities based on the database query and the hierarchy metadata, and accesses the data using the determined optimal data entity relationship path. | 03-15-2012 |
20120066267 | AUTOMATIC LAYOUT DERIVATION AND IMPLEMENTATION - Embodiments are directed to determining a data insertion point in a data layout based on relative cardinalities between data objects and to determining a data insertion point in a data layout based on defined hierarchies between data objects. In an embodiment, a computer system receives a user input indicating that an additional portion of information is to be added to an existing data layout which includes multiple different data objects. The computer system accesses the data objects to determine relative cardinalities between the data objects in the data layout. The computer system determines an optimal data insertion point for inserting the additional portion of information based on the determined relative cardinalities between the data objects. The computer system also inserts the additional portion of information in the existing data layout at the determined optimal data insertion point. | 03-15-2012 |
20120109995 | ANTINULL USAGE AND SIMULATION IN DATA FILTERING - Comparing data items. The method includes accessing a query or command to retrieve data. The query or command includes an identification of a data item, a logical operator and a specialized token. A comparison as defined by the logical operator between the data item and the specialized token is performed. The following illustrates the results of the logical operation on any data item and the specialized token: an equal logical operation results in true, a greater than logical operation results in false; a less than logical operation results in false; a greater than or equal to logical operation results in true; a less than or equal to logical operation results in true; a not equal logical operation results in false; an IN logical operation results in true; and a NOT IN logical operation results in false. As a result of the comparison, the data item may be retrieved. | 05-03-2012 |
20130282769 | AUTOMATIC LAYOUT DERIVATION AND IMPLEMENTATION - Embodiments are directed to determining a data insertion point in a data layout based on relative cardinalities between data objects and to determining a data insertion point in a data layout based on defined hierarchies between data objects. In an embodiment, a computer system receives a user input indicating that an additional portion of information is to be added to an existing data layout which includes multiple different data objects. The computer system accesses the data objects to determine relative cardinalities between the data objects in the data layout. The computer system determines an optimal data insertion point for inserting the additional portion of information based on the determined relative cardinalities between the data objects. The computer system also inserts the additional portion of information in the existing data layout at the determined optimal data insertion point. | 10-24-2013 |
20140019437 | Data Scope Origination Within Aggregation Operations - A computer-implemented method for generating a report from a report definition specifying a plurality of data scopes for a dataset includes interpreting, with a processor, a report definition for the report, the report definition comprising a calculation expression for populating a unit of the report, the calculation expression comprising a data aggregation operation, the data aggregation operation comprising an originating reference to a further data scope, accessing a memory coupled to the processor to obtain data from the dataset for respective subsets of the dataset corresponding with the further data scope, determining, with the processor, an output value for the calculation expression in accordance with the obtained data and the data aggregation operation, and rendering the report based on the output value. | 01-16-2014 |
20140351296 | AUTOMATIC LAYOUT DERIVATION AND IMPLEMENTATION - Embodiments are directed to determining a data insertion point in a data layout based on relative cardinalities between data objects and to determining a data insertion point in a data layout based on defined hierarchies between data objects. In an embodiment, a computer system receives a user input indicating that an additional portion of information is to be added to an existing data layout which includes multiple different data objects. The computer system accesses the data objects to determine relative cardinalities between the data objects in the data layout. The computer system determines an optimal data insertion point for inserting the additional portion of information based on the determined relative cardinalities between the data objects. The computer system also inserts the additional portion of information in the existing data layout at the determined optimal data insertion point. | 11-27-2014 |
20150058350 | REPORTING INCLUDING FILLING DATA GAPS AND HANDLING UNCATEGORIZED DATA - A reporting system is described herein that allows a report author to declare data reporting structures that specify to a reporting application how to dynamically categorize data with changing or potentially unknown characteristics. The reporting system may extend RDL and the data grouping provided by Microsoft SQL Server Reporting Services by adding new elements to the XML-based RDL schema. The reporting system allows the report author to specify for the system to fill gaps in the data, so that the report has a similar layout even as data changes from period to period. The reporting system also allows the report author to specify whether data that does not fit any predefined group bucket is displayed in a report. Thus, the reporting system allows unsophisticated database users to define reports that group data consistently regardless of missing values or other changes in the underlying data. | 02-26-2015 |