Method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium
A method of automatically re-organizing structured data in a reporting system based on screen size calculated an initial layout for data containers in a report, checks to see if any of the data containers are obscured by the right display edge, and re-arranges the data containers so that no containers are obscured. A similar process is performed on any data grids with obscured columns. Columns are removed according to importance to maintain context. Elements in a removed column are added below respective associated rows.
Latest Microsoft Patents:
The current application claims a priority to the U.S. Provisional Patent application Ser. No. 62/017,686 filed on Jun. 26, 2014.
FIELD OF THE INVENTIONThe present invention relates generally to arrangement of data. More particularly, the present invention relates to automatic re-layout of structured data.
BACKGROUND OF THE INVENTIONA report is the runtime result of merging a report definition with data producing a visual output. Reports are generally designed with a specific screen size in mind, much like paper size in the past. Using a screen size larger or smaller is less efficient or in many cases completely unusable. To address this inherit problem, report writers must produce several different layouts based on screen size. State of the art responsive layout solutions do not work because it is critical that the data stay in context with the original design. Improper re-layout can lead to misinterpretation of the data and negate the purpose of the report.
There are many of different strategies for implementing a responsive solution using code or templates for static websites. The present invention is a system that focuses on automatic re-layout in a reporting solution where there is an abstract definition of the report that is merged with data at runtime. Therefore the actual amount of data and final layout is not known until runtime.
All illustrations of the drawings are for the purpose of describing selected versions of the present invention and are not intended to limit the scope of the present invention. The present invention is to be described in detail and is provided in a manner that establishes a thorough understanding of the present invention. There may be aspects of the present invention that may be practiced without the implementation of some features as they are described. It should be understood that some details have not been described in detail in order to not unnecessarily obscure focus of the invention.
The present invention is a method for automatic re-layout of structured data in a reporting system based on screen size. The present invention implements a responsive layout on dynamic data maintaining the context and structure of the original, or intended layout. In the present invention, two principal steps are executed to provide automatic and optimal viewing of the data without losing context leading to misinterpretation. The first principal step is to re-layout all elements of the data report to be visible within the boundaries of a display without having to scroll to the right. The second step is to re-layout cells within any data grids so that the most important information in the data grid is displayed.
The present invention is intended to be used with a data reporting system. In a data reporting system, a report is provided comprising a plurality of data containers and data elements. Typically, the report is provided in the form of a spreadsheet or some other format which contextualizes different types of information, such as, but not limited to, vendor information, customer information, item type, item number, cost per item, number of items ordered, and so on. Each individual piece of data is regarded as a data element. Each of the data containers represents a portion of the various types and delineations of data in the report. A data container may comprise a single data element, additional nested containers, or a data container may be empty and not comprise any further data containers or data elements. Data elements are the basic building blocks of a report. Examples of data elements include, but are not limited to, text areas, charts, lines, images, containers, gauges, maps, and so on. Generally, data elements specify content to be delivered and any style information.
With the report, a report definition is also provided (A). The report definition defines the data containers and is a set of instructions for spatially arranging the data containers on a visual medium, more particularly on a digital display device. While the data elements are the content of the report, the report definition provides the intended structure and layout of the content of the report. The report definition defines the spatial arrangement of the data in the report for readability and context. The report definition is an abstract set of instructions for the layout of the data to produce a report. The report definition may contain data grouping, sorting, aggregation and other concepts. Reports are made of data elements that are laid out on a “canvas” or display. Data elements may also be grouped into data containers which may be used for context and to keep like elements together. Data containers may be nested in other data containers. It should be understood that data containers may be treated as individual data elements when nesting is used, and data elements may be understood to be analogous to a data container with a single data element.
In a non-limiting example where the report is a sales order, a report definition may instruct the computer system processing the report to display a “Bill to” data container at the top left corner of the report, with a “Ship to” data container horizontally even with the “Bill to” data container and a certain distance right of the “Bill to” data container, while data containers containing contact information for various parties and order information further down on the report, followed by a list of items purchased.
Referring to
Initial container coordinates for each of the data containers are calculated using the report definition and the data containers as is typical with reporting systems (C). The initial container coordinates for each of the data containers comprise an initial left container edge value, an initial right container edge value, an initial top container edge value and an initial bottom container edge value. The initial container coordinates represent the general layout of the report if the method of the present invention is not executed on the report. In common practice coordinates are specified as Top, Left, Width and Height. From these definitions, Bottom and Right values can be calculated. However, the specific convention of implementation for defining coordinates does not significantly change the present invention so long as the desired effect is achieved.
The initial container coordinates for each of the data containers are compared to the layout coordinates in order to find an obscured container (D). In order for a specific data container to be considered an obscured container, the initial right container edge value of the specific data container must exceed the right display edge value. In one embodiment of the present invention, the initial right container edge value must exceed the right display edge value by any margin to be considered an obscured container. In another embodiment, the initial left container edge value must exceed the right display edge value by a specified percentage of the data container to be considered an obscured container. In another embodiment, the initial left container edge value must exceed the right display edge value by some other calculated margin to be considered an obscured container.
An adjacent container is then checked for from the plurality of data containers (E). In the preferred embodiment, the criteria for finding an adjacent container are as follows: the initial top container edge values for the obscured container and the adjacent container are identical, and the initial right container edge value of the adjacent container is less than (or equal to in some embodiments) the initial left container edge value of the obscured container. In some embodiments the initial top container edge values of the obscured container and the adjacent container need not be identical, but close within a specified margin, or the adjacent container may be recognized by other similar criteria or means. Alternatively stated, the criteria for an adjacent container may simply comprise being left of the obscured container with some vertical overlap.
If the adjacent container is found, the obscured container is moved below the adjacent container (F). Steps (D) through (F) are repeated, starting with the rightmost data containers from the plurality of data containers until an obscured container is found, or until an adjacent container is not found left of an obscured container (G). The rightmost data containers are data containers with larger horizontal coordinate values than other data containers with identical or similar vertical coordinate values (in other words, in the same row of the report or with some vertical overlap).
Referring to
Since data containers may contain other data containers, this re-layout process is repeated as many times as necessary to ensure that no elements are obscured. Data containers and data elements are treated similarly in that they both may be regarded as a single unit and moved to a new layout position. When a data container containing other data containers is moved, the other data containers maintain their position within the containing data container. After the data container is moved, the other data containers within the data containers are also checked to make sure none of the other data containers are obscured. In general, the process of the present invention is to re-layout the data containers from the outermost, or rightmost, containers first, and subsequently check inner data containers.
Referring to
Referring to
For data grids, there is a need to hide and move the cells in the grid if they are not visible. Because the data in a grid is generally very specific to the row and column it is in, there is a need to maintain its context. Since columns are moving or hiding, it must identify the column headers if any. There may be multiple levels of column headers and column headers may change multiples times based on previous rows in the grid. Cells may contain containers, if so the cell is treated as a cell and moves according to data grid rules. The container is treated as a container and is re-laid out in the cell based on element rules. A column header is a special cell within a data grid that is used to identify the rest of the data in that row or column. A data grid may have multiple levels of row and column headers. Column headers may also be dynamic and repeat throughout the data grid.
Once the data grid is identified, a re-layout operation is performed on the data grid similar to the first principal step of performing the re-layout of the data containers. The columns of the data grid are analyzed to determine if any of the columns are obscured, using similar means as in the first principal step. If an obscured column is found, a specified column is removed from the data grid (I). A column is obscured if the column is positioned right of the right display edge value similar to an obscured data container.
A specific data element from the plurality of data elements of the obscured column is then added into a relocated element container below a respective row from the plurality of rows of the data grid, wherein the specific element is associated with the respective row (J). Additionally, a column header of the specific column is added adjacently with the specific data element into the relocated element container below the respective row to maintain context. All data elements of removed columns are moved into the relocated element container for each respective row. The column headers are repeated in every new row with an added data element from the removed specific column.
Rows of the re-laid out data grid may be expanded to show information from the removed columns, as shown in
Similarly, upon receiving input through the user interface to collapse the respective row (if the respective row is currently expanded and the relocated element container is currently shown on the user interface) the relocated element container is removed from the user interface, and the plurality of lower rows is relocated from the relocated position back to the original position, and step (G) is again executed.
Determining the specified column depends on the context and content of the columns. The columns are analyzed to determine an importance ranking for the columns, and less important columns are removed until there are no obscured columns. If an importance ranking is not determined, the columns are removed starting from the rightmost column until no columns are obscured.
By default, columns are removed when they are not visible usually starting from the far right. In some cases it is preferable to prioritize which columns should be removed first so that the most important information is visible to the user. The system should allow the report designer to provide metadata to prioritize the order in which columns are removed.
When performing the re-layout operation of the data grid, the column headers of the data grid are analyzed in order to identify at least one important column and at least one less important column from the plurality of columns. If one of the at least one important column is obscured, a less important column is removed if the less important column is left of the obscured important column, and the obscured important column is moved left until the obscured important column is no longer obscured.
Preferably, column metadata is provided for each of the columns of the data grid. The column metadata of each of the columns is compared to each other in order to identify the at least one important column and the at least one unimportant column.
If the column metadata is not provided, a column header importance guessing algorithm is used to identify the at least one important column and the at least one less important column.
Identifying column headers is critical to maintain context. In most cases the column headers will be in the first row of data. If there is a column span in the first row, then the second row likely also contains column header data. Some reporting systems identify column headers, and use this information when available. The system may also allow the report designer to provide column header metadata to identify the column header rows. For cases where the column headers are repeated or change based on the rows in the grid the system can either rely on hits from the report designer or best guess the column headers based on heuristics repeating values in rows. If no header can be identified then the cell groups either must be ordered or include a column number in the cell group.
If a column is not visible, the column is removed from the grid and a new column data row is added for every row in the grid with the cells from the removed columns. The cells that are removed are added to the column data row with their respective column header forming a column cell group. If there are multiple levels of column headers, they may either all be repeated with each cell group or if they span multiple columns with the first cell group. The cell groups in the column data row may be arranged to make optimal use of the available width. The simplest arrangement is place each cell group below the previous cell group.
In some cases, cells in a data grid may be dynamically expandable. For example, the “Accessories,” “Bikes,” “Clothing,” “Components,” “2002,” and “2003” cells in
Referring to
In addition to cells in a data grid, a report may also allow dynamically expandable data containers. A dynamically expandable data container may be expanded to show further data containers or data elements, which take up additional space on the report and for which other elements must be moved to accommodate. Similar to the above description for cells in a data grid, every time a dynamically expandable data container is either expanded or collapsed, the re-layout process of step (G) is re-applied to maintain proper layout.
In the preferred embodiment of the present invention, cell formatting is maintained when re-layout of data elements within a data grid is performed. This is important to preserving context in the report, since different elements of the report may be formatted in different ways (such as, but not limited to, font type, weight, size, color, and alignment)
The data grid may also have 0 or more levels of row groups, or row spans. If the row has a row group the column data row is added to the row group at the lowest visible level. If a row group column is removed, the entire row group (all rows) is moved to the column data row. By default, column data rows should be not visible and there should be an icon or indicator to allow the user to expand ad collapse each data row.
Although the invention has been explained in relation to its preferred embodiment, it is to be understood that many other possible modifications and variations can be made without departing from the spirit and scope of the invention as hereinafter claimed.
Claims
1. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium comprises the steps of:
- (A) providing a report definition, wherein the report definition defines a plurality of data containers, and wherein the report definition provides instructions for spatially arranging the data containers on a visual medium;
- (B) retrieving layout coordinates for a display device, wherein the layout coordinates delineate display boundaries on the display device, and wherein the layout coordinates comprise a right display edge value;
- (C) calculating initial container coordinates for each of the data containers from the report definition, wherein the initial container coordinates for each of the data containers comprise an initial left container edge value, an initial right container edge value, an initial top container edge value and an initial bottom container edge value;
- (D) comparing the initial container coordinates for each of the data containers to the layout coordinates in order to find an obscured container, wherein the initial right container edge value of the obscured container exceeds the right display edge value;
- (E) checking for an adjacent container from the plurality of data containers, wherein the initial right container edge value of the adjacent container is less than the initial left container edge value of the obscured container, and wherein there is vertical overlap between the obscured container and the adjacent container;
- (F) moving the obscured container below the adjacent container, if the adjacent container is found;
- (G) repeating steps (D) through (F) starting with the rightmost data containers until an obscured container is not found, or until an adjacent container is not found left of an obscured container;
- (H) identifying one of the data containers as a data grid, wherein the data grid comprises a plurality of data elements arranged in a plurality of rows and a plurality of columns, wherein each of the columns may be associated with a column header, and wherein each data element is associated with one of the rows from the plurality of rows and one of the columns from the plurality of columns;
- (I) removing a specified column from the data grid if an obscured column is found from the plurality of columns, wherein a column is obscured if the column is positioned right of the right display edge value; and
- (J) adding a specific data element from the plurality of data elements of the obscured column into a relocated element container below a respective row from the plurality of rows, wherein the specific data element is associated with the respective row.
2. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the steps of:
- checking for a lower container below the adjacent container, wherein the initial top container edge value of the lower container is greater than the initial lower container edge value of the adjacent container; and
- moving the lower container down in order to accommodate the obscured container being moved beneath the adjacent container, if the lower container is found.
3. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the steps of:
- providing that an arbitrary data container comprises a plurality of data elements;
- checking if any of the data elements of the arbitrary data container are obscured, wherein part of an obscured element is past the right display edge boundary;
- checking for an adjacent element, wherein the adjacent element is left of the obscured element;
- moving the obscured element below the adjacent element, if an initial top element edge value of the obscured element is greater than an initial top edge element value of the adjacent element; and
- moving the obscured element above the adjacent element, if the initial top element edge value of the obscured element is less than the initial top edge element value of the adjacent element.
4. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the step of:
- adding a column header of the specific column adjacent to the specific data element below the respective row.
5. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the steps of:
- analyzing the column headers of the data grid in order to identify at least one important column and at least one less important column from the plurality of columns; and
- removing a less important column left of an obscured important column from the at least one important column as the specified column, if the obscured important column is found.
6. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 5 comprises the steps of:
- providing column metadata for each of the columns; and
- comparing the column metadata of each of the columns in order to identify the at least one important column and the at least one less important column.
7. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 5 comprises the steps of:
- providing a column header importance guessing algorithm; and
- identifying the at least one important column and the at least one less important column using the column header importance guessing algorithm.
8. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the steps of:
- receiving input through a user interface to expand the respective row;
- showing the relocated element container below the respective row on the user interface;
- moving a plurality of lower rows from the plurality of rows from an original position to a relocated position in order to accommodate the relocated element container, wherein the lower rows are rows below the respective row, and wherein the relocated position is lower than the original position;
- executing step (G).
9. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the steps of:
- receiving input through a user interface to collapse the respective row;
- removing the relocated element container from the user interface;
- moving a plurality of lower rows from the plurality of rows from a relocated position to an original position, wherein the lower rows are rows below the respective row, and wherein the relocated position is lower than the original position; and
- executing step (G).
10. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the step of:
- executing step (G), if the quantity of rows of the data grid changes, or if the quantity of columns of the data grid changes.
11. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the steps of:
- providing that a specific cell of the data grid is a dynamically expandable cell, and that the dynamically expandable cell is currently collapsed;
- receiving input through a user interface to expand the dynamically expandable cell, wherein expanding the dynamically expandable cell either adds rows, columns, or both to the data grid; and
- executing step (G).
12. A method of automatically re-organizing structured data in a reporting system based on screen size by executing computer-executable instructions stored on a non-transitory computer-readable medium as claimed in claim 1 comprises the steps of:
- providing that a specific cell of the data grid is a dynamically expandable cell, and that the dynamically expandable cell is currently expanded;
- receiving input through a user interface to collapse the dynamically expandable cell, wherein collapsing the dynamically expandable cell removes either rows, columns, or both from the data grid; and
- executing step (G).
| 6976226 | December 13, 2005 | Strong |
| 6981209 | December 27, 2005 | Parikh |
| 7216291 | May 8, 2007 | Kim |
| 7260777 | August 21, 2007 | Fitzsimons |
| 8214733 | July 3, 2012 | Bastos dos Santos |
| 8219927 | July 10, 2012 | Gatlin |
| 9013513 | April 21, 2015 | Paolini |
| 9087337 | July 21, 2015 | Ho |
| 9760271 | September 12, 2017 | Persaud |
| 20090164919 | June 25, 2009 | Bates |
| 20090313537 | December 17, 2009 | Fu |
| 20100153858 | June 17, 2010 | Gausman |
| 20110169927 | July 14, 2011 | Mages |
| 20120159297 | June 21, 2012 | Peters |
| 20130124996 | May 16, 2013 | Margulis |
| 20130151974 | June 13, 2013 | Cho |
| 20140215308 | July 31, 2014 | Cantrell |
| 20170214611 | July 27, 2017 | Cordell |
| 20180247612 | August 30, 2018 | Kikuchi |
Type: Grant
Filed: Jun 26, 2015
Date of Patent: Sep 3, 2019
Patent Publication Number: 20150379470
Assignee: MICROSOFT TECHNOLOGY LICENSING, LLC (Redmond, WA)
Inventor: Jason David Carlson (Plano, TX)
Primary Examiner: Scott T Baderman
Assistant Examiner: Mario M Velez-Lopez
Application Number: 14/752,640
International Classification: G06F 3/048 (20130101); G06F 17/24 (20060101); G06F 17/21 (20060101); G06Q 10/10 (20120101);
