Patent Grant
11797579
The present invention relates to the field of presentation layer management and more particularly to presentation layer composition based upon an underlying data model.
The term database refers to an organized collection of data, stored and accessed electronically by way of a computing system. A database management system (DBMS) in turn is a computer program that provides an interface between the database and one or more end users so as to facilitate the interaction by each end user with the database. A DBMS generally also provides an interface to other computer programs to access the data in the underlying database. Generally, speaking, end users and other computer programs interact with the database through the DBMS using query directives formed in conformance with a corresponding query language such as the venerable structured query language (SQL).
While the very basic use of SQL to query and manage data in a database is of no great difficulty for many end users, formulating more complex SQL queries is not for the faint of heart. More importantly, specifying a query irrespective of the mechanics of the actual query requires a strong understanding of the data in the database and the underlying relationships between the data. To the extent that “reading” the content of a database is not practical, it is known to model a database so that the created database model can then be introspected so as to afford a deeper understanding of the data in the database. Indeed, modern data analytics tools permit not only the modeling of an existing database, but also the formulation of SQL queries to be executed against the database based upon knowledge only supplied by the model.
In this regard, a data model is an abstract model that describes how a data set of a database is organized, and guides the construction of queries with respect to the data of the data set. The data model generally contains a join graph whose vertices each reference a table and whose edges reflect join conditions between references to the tables. As well, the join graph may also describe the columns in those tables, columns that are derived from other columns via expressions, collections of columns by which queries are typically sorted, collections of columns by which queries are typically grouped into sub-totals and totals, expressions that are derived by combining column values during the construction of a sub-total or total, and other suggestions for how queries might be formed on the data.
Despite the robust nature of a data model, the introspection of a data model for a database, however, is not alone sufficient to enjoy a complete understanding of the data in a database. To that end, a presentation layer applied to data elements of the data model permit a fuller understanding of the nature of the underlying values in a database modeled by the data model. Of course, the presentation layer once generated and rendered, remains fully dependent upon the state of the data model. In particular, some aspects of the data model, once visualization in the presentation layer, depend upon data elements present in the data model, and more importantly, upon values derived from one or more data elements when combined as an aggregation, or derived from a dependency of one data element upon the other. Hence, the validity of the presentation layer can change responsive to a change in the underlying data model rendering the visualization in the presentation layer invalid and forcing the end user to re-specify the presentation layer.
Embodiments of the present invention address deficiencies of the art in respect to presentation layer management, including a visualization or dashboard for an underlying data model, and provide a novel and non-obvious method, system and computer program product for data content governance for presentation layer synchronization for a version controlled underlying data model. In an embodiment of the invention, a data content governance for presentation layer synchronization method includes defining a data model for underlying data in a database, specifying a presentation layer for the defined data model and identifying selected elements of the data model necessary to meet data requirements of the specified presentation layer. The method additionally includes serializing the identified selected elements of the data model and versioning both the specified presentation layer and the serialized elements of the data model in respect to the specified presentation layer. Thereafter, the method includes modifying the data model and also modifying the specified presentation layer to accommodate the modified data model and in response to the modification, re-identifying a different selection of elements of the data model necessary to meet data requirements of the modified presentation layer, serializing the re-identified different selection of elements of the data model and versioning the modified presentation layer and the serialized re-identified different selection of elements.
In one aspect of the embodiment, the method further includes selecting a data model for visualization in a new presentation layer and validating the new presentation layer against the selected data model by comparing a serialization of elements of the selected data model, identified as being necessary to meet data requirements of the new presentation layer, to a versioned form of the new presentation layer. In another aspect of the embodiment, the method further includes responding to a failed validation by selecting a prior version of the data model for visualization in the new presentation layer.
In yet another aspect of the embodiment, the data requirements of the specified presentation layer are user interface controls each referencing a particular element of the data model such that the particular element must be accessible to the specified presentation layer in order to include data of the particular element in a corresponding one of the user interface controls of the specified presentation layer. In even yet another aspect of the embodiment, the data requirements of the specified presentation layer are user interface controls each referencing content that is dependent upon particular element of the data model such that the particular element must be accessible to the specified presentation layer in order to compute data for the referenced content properly for inclusion in a corresponding one of the user interface controls of the specified presentation layer.
In another embodiment of the invention, a data visualization data processing system configured for data content governance for presentation layer synchronization is provided. The system includes a host computing system of one or more computers, each with memory and at least one processor. The system also includes a data visualization module. The module includes comprising computer program instructions executing in the memory of the host computing system and accessing a data model in a database. The program instructions during execution define a data model for underlying data in the database, specify a presentation layer for the defined data model and identify selected elements of the data model necessary to meet data requirements of the specified presentation layer. The program instructions during execution further serialize the identified selected elements of the data model and version both the specified presentation layer and the serialized elements of the data model in respect to the specified presentation layer.
Subsequently the program instructions modify the data model and also the specified presentation layer to accommodate the modified data model respond to the modification by re-identifying a different selection of elements of the data model necessary to meet data requirements of the modified presentation layer, serializing the re-identified different selection of elements of the data model and versioning the modified presentation layer and the serialized re-identified different selection of elements.
Additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The aspects of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
The accompanying drawings, which are incorporated in and constitute part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. The embodiments illustrated herein are presently preferred, it being understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown, wherein:
Embodiments of the invention provide for data content governance for presentation layer synchronization. In accordance with an embodiment of the invention, a data model is selected for a database including a multiplicity of different model elements. A presentation layer is then defined for visualizing values associated with the different model elements, such as a graphical visualization of underlying values in the database corresponding to the different model elements, or values reflecting an aggregation of different underlying values in the database corresponding to the different model elements, or values derived from underlying values of dependent ones of the model elements. An association is then established as between the visualization and the different model elements necessary for rendering the visualization as a serialization of the required model elements and a versioning of both the serialization and the visualization. Consequently, as the database model changes, when a visualization is selected in connection with the changed model in respect to a set of data elements in the model, the set of data elements can be serialized and compared to the versioned serialization corresponding to the selected visualization so as to detect a match. Without a match, it can be presumed that the set of data elements is lacking in respect to the association and, in consequence, a prior version of the data model can be selected from which the presentation can be rendered.
In further illustration,
Importantly, the model elements in the set 150A are transformed into a serialization 160A and both the presentation layer 170A and the serialization are assigned a version and inserted as an entry into a version table 190. Thereafter, as the data model 140A is modified into a modified data model 140B, a different presentation layer 170B is defined according to the data requirements 180B of the presentation layer 170B in respect to the data elements in a set of data elements 150B for the modified data model 140B. Again, the data elements in the set of data elements 150B may be serialized into a serialization 160B and assigned a version as can be the different presentation layer 170B, with both being included as part of an entry 100N in the version table 190.
Thus, as the data model 140A changes into modified data model 140B, if the prior presentation layer 170A is selected to visualize the modified data model 140B, the serialization 160B of the model elements in the set 150B is compared to the serialization 160A stored in the version table 190. If the serializations 160A, 160B match, it is determined that the presentation layer 170A is valid for visualizing the modified data model 140B. But, if the serializations 160A, 160B do not match, the presentation layer 170A is determined to be invalid and the prior data model 140 is the selected for providing the underlying data elements in the set of data elements 150A for the presentation layer in lieu of the modified data model 140B. In this way, it is assured that the selected presentation layer 170A can be validly presented despite underlying changes in the data model 140A present in the modified data model 140A that result in an invalid presentation layer 170A.
The process described in connection with
The program instructions of the data content governance module 300 upon execution in the memory 260 of the host computing system are operable to select an instance of a multiplicity of versioned data models 200A for the database 220 managed by version control system 290A, and also a presentation layer 200B adapted to visualize values in the database 220 associated with a set of data elements of the selected data model 200A. The program instructions further are enabled to serialize the data elements in the set and to assign a version to each of the serialization and the selected presentation layer 200B. The program instructions even further are enabled to add an entry to version table 290B of a version control system 290A including the versioned serialization and presentation layer.
The program instructions also are enabled upon execution in the memory 260 to respond to a selection of the presentation layer 200B associated with a specific version by locating in the version table 290B an entry including a correspondingly versioned serialization of data elements requisite for the validation of the selected presentation layer 200B. The program instructions then serialize the data elements of the selected instance of the data models 200A of a particular version presently loaded for visualization in the selected presentation layer 200B and compare the serialized data elements to the versioned serialization of data elements in the entry of the version table 290B. To the extent the serializations match, the selected presentation layer 200B may be rendered. But, to the extent that the serializations do not match, a prior instance of the data models 200A of the same version as the selected presentation layer 200B is retrieved for use in rendering the selected presentation layer 200B.
In even further illustration of the operation of the data content governance module 300,
In block 340, those data elements in the versioned instance of the data model that are requisite to the visualization are serialized and in block 350, a version is retrieved for the selected presentation layer. Thereafter, in block 360 an entry is retrieved from a version table corresponding to the version and a serialization in the entry identified. In block 370, the identified serialization is compared to the serialization of the data elements in the versioned instance of the data model. In decision block 380, it is determined if the serializations match and are thus valid. If so, in block 400 the presentation layer may be rendered including the visualization. But otherwise, in block 390, a prior instance of the data model associated with the version of the presentation layer is retrieved and then, in block 400, the presentation layer may be rendered.
The present invention may be embodied within a system, a method, a computer program product or any combination thereof. The computer program product may include a computer readable storage medium or media having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention. The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein includes an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which includes one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
Finally, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “includes” and/or “including,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
Having thus described the invention of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the invention defined in the appended claims as follows:
| Number | Name | Date | Kind |
|---|---|---|---|
| 5619631 | Schott | Apr 1997 | A |
| 9489119 | Smith, Jr. | Nov 2016 | B1 |
| 20050246690 | Horton | Nov 2005 | A1 |
| 20070011653 | Fischer et al. | Jan 2007 | A1 |
| 20150074044 | Metreveli | Mar 2015 | A1 |
| 20160019244 | Liu et al. | Jan 2016 | A1 |
| 20160378733 | Mullins | Dec 2016 | A1 |
| 20170039253 | Bond | Feb 2017 | A1 |
| 20170109003 | Angermayer et al. | Apr 2017 | A1 |
| 20200004847 | Bagga | Jan 2020 | A1 |
| 20200341903 | Dobiesz | Oct 2020 | A1 |
| 20210056104 | Tong | Feb 2021 | A1 |
| Entry |
|---|
| International Search Report, Application No. PCT/US2020/067386, dated Apr. 22, 2021, 13 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20210200791 A1 | Jul 2021 | US |
