Patent Application
20230334237
The field of the invention is data processing, or, more specifically, methods, apparatus, and products for workbook template sharing.
Modern businesses may store large amounts of data in remote databases within cloud-based data warehouses. This data may be accessed using database statement languages, such as structured query language (SQL). Manipulating the data stored in the database may require constructing complex queries beyond the abilities of most users. Further, composing and issuing database queries efficiently may also be beyond the abilities of most users.
Methods, systems, and apparatus for workbook template sharing including receiving, by a table manager, a request to create a workbook from a workbook template using data in a cloud-based data warehouse, wherein the workbook template comprises a fingerprint describing an input schema hierarchy; determining, by the table manager, data pathways for the workbook by matching the fingerprint of the workbook template to a schema hierarchy of the data in the cloud-based data warehouse; and generating, by the table manager, the workbook according to the workbook template using the data pathways.
The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.
Exemplary methods, apparatus, and products for workbook template sharing in accordance with the present invention are described with reference to the accompanying drawings, beginning with
Stored in RAM 168 is an operating system 154. Operating systems useful in computers configured for workbook template sharing according to embodiments of the present invention include UNIX™, Linux™, Microsoft Windows™, AIX™, and others as will occur to those of skill in the art. The operating system 154 in the example of
The intermediary computing system 152 of
The example intermediary computing system 152 of
The exemplary intermediary computing system 152 of
The communications adapter 167 is communicatively coupled to a wide area network 190 that also includes a cloud-based data warehouse 192 and a client computing system 194. The cloud-based data warehouse 192 is a computing system or group of computing systems that hosts a database or databases for access over the wide area network 190. The client computing system 194 is a computing system that accesses the database using the table manager 126.
The GUI 202 is a visual presentation configured to present data sets in the form of workbooks to a user. The GUI 202 also receives requests from a user for data sets from the database 204. The GUI 202 may also present to the user the ability to add a new row into a data set or table and enter values for each column of the new row. The GUI 202 may be presented, in part, by the table manager 126 and displayed on a client computing system 194 (e.g., on a system display or mobile touchscreen). The GUI 202 may be part of an Internet application that includes the table manager 126 and is hosted on the intermediary computing system 152.
The database 204 is a collection of data and a management system for the data. A data set is a collection of data (such as a table) from the database 204. Data sets may be organized into columns and rows (also referred to as records). The particular columns, rows, and organization of the columns and rows that make up a data set may be specified in the database statement requesting the data set. Data sets may be sent from the cloud-based data warehouse 192 in response to a database statement (also referred to as a query). Accordingly, data sets retrieved in response to a database statement may be referred to as query results.
The table manager 126 is hardware, software, or an aggregation of hardware and software configured to receive instructions in the form of state specifications from the client computing system 194, via the GUI 202. The table manager 126 is also configured to present workbooks in the GUI 202 response to the instructions, which may include generating database statements in response to manipulations of the GUI 202 described in the state specification.
The state specification is a collection of data describing inputs into the GUI 202. The state specification may include manipulations of GUI elements within the GUI 202 along with data entered into the GUI 202 by a user of the client computing system 194. Such manipulations and data may indicate requests for and manipulations of data sets. Such manipulations and data may also indicate requests to edit an existing row or create a new row and values for that row. The state specification may be a standard file format used to exchange data in asynchronous browser-server communication. For example, the state specification may be a JavaScript Object Notation specification. The state specification may also include descriptions of elements that are used to apply changes to the data set. Such elements may include filters applied to the workbook, the hierarchical level of the workbook, joins performed within the workbook, exposable parameters in the workbook, and security for the workbook.
The table manager 126 may use the state specification as input to generate a database statement. This database statement generation process may begin with state specification being converted into an abstract syntax tree. The abstract syntax tree may then be canonicalized into a canonicalized hierarchy. The canonicalized hierarchy may then be linearized into the workbook algebra. The workbook algebra may then be lowered into a relational algebra, which may then be lowered into the database statement.
The table manager 126 may use the database statement to fetch query results (i.e., a data set) from the database 204. The table manager 126 may then present the query results to a user via the GUI 202. The table manager 126 may further manage tables on the database 202 to which a user has made edits, such as adding new rows or editing existing rows. Further, the table manager 126 may add columns to new rows and create new tables on the database 202.
The table manager 126 may service requests in the state specification using workbooks local to the table manager 126. A workbook is a presentation of a data set in the GUI 202. Specifically, a workbook is metadata describing a particular organization and configuration of a data set for presentation via the GUI 202. A workbook may include multiple elements including a visualization and a spreadsheet structure. For example, a workbook may include a spreadsheet structure presenting data points from a data set and an accompanying visualization may present a graph of the data points. Such workbooks may be stored in the workbook repository 206.
The workbook 302 is a collection of graphical elements and organizing mechanism for a data set. The workbook may present a data set retrieved by the table manager from a cloud-based data warehouse. Specifically, the table manager may generate a database statement in response to the request from a client. The database statement may then be issued to the cloud-based data warehouse and the data set may be received as the query results of the database statement. The data set may then be organized based on the workbook retrieved from the workbook repository. The table manager itself may reside on an intermediary computing system between the client computing system and the cloud-based data warehouse.
As shown in
The list structure 310 is a graphical element used to define and organize the hierarchical relationships between the columns (column A 308A, column B 308B, column C 308C, column D 308D, column E 308E, column F 308F) of the data set. The term “hierarchical relationship” refers to subordinate and superior groupings of columns. For example, a database may include rows for an address book, and columns for state, county, city, and street. A data set from the database may be grouped first by state, then by county, and then by city. Accordingly, the state column would be at the highest level in the hierarchical relationship, the county column would be in the second level in the hierarchical relationship, and the city column would be at the lowest level in the hierarchical relationship.
The list structure 310 presents a dimensional hierarchy to the user. Specifically, the list structure 310 presents levels arranged hierarchically across at least one dimension. Each level within the list structure 310 is a position within a hierarchical relationship between columns (column A 308A, column B 308B, column C 308C, column D 308D, column E 308E, column F 308F). The keys within the list structure 310 identify the one or more columns that are the participants in the hierarchical relationship. Each level may have more than one key.
One of the levels in the list structure 310 may be a base level. Columns selected for the base level provide data at the finest granularity. One of the levels in the list structure 310 may be a totals or root level. Columns selected for the totals level provide data at the highest granular level. For example, the totals level may include a field that calculates the sum of each row within a single column of the entire data set (i.e., not partitioned by any other column).
The GUI 202 may enable a user to drag and drop columns (column A 308A, column B 308B, column C 308C, column D 308D, column E 308E, column F 308F) into the list structure 310. The order of the list structure 310 may specify the hierarchy of the columns relative to one another. A user may be able to drag and drop the columns in the list structure 310 at any time to redefine the hierarchical relationship between columns. The hierarchical relationship defined using the columns selected as keys in the list structure 310 may be utilized in charts such that drilling down (e.g., double click on a bar), enables a new chart to be generated based on a level lower in the hierarchy.
The GUI 202 may also include a mechanism for a user to request a table from a database to be presented as a workbook in the GUI 202. Such a mechanism may be part of the interactivity of the workbook. Specifically, a user may manipulate a workbook (e.g., by dragging and dropping columns or rows, resorting columns or rows, manipulating a graph etc.) and, in response, the GUI 202 may generate a request (e.g., in the form of a state specification) for a data set and send the request to the table manager 126. Such a mechanism may also include a direct identification of the rows and columns of a database table that a user would like to access (e.g., via a selection of the rows and columns in a dialog box). The GUI 202 may also include a mechanism for a user to create a new table on the database, add rows to a table, and move rows within the table.
For further explanation,
As discussed above, a workbook is a collection of graphical elements and organizing mechanism for a particular (known) data set. A workbook template is a collection of graphical elements and organizing mechanism for a type of data set. The workbook template may be used to create a workbook for any data set from data on a cloud-based data warehouse that conforms to a particular structure (i.e., schema hierarchy). For example, a workbook template may be created for store inventory, and may be used by any organization that structures their inventory data in a way that approximately conforms to the schema hierarchy used by the workbook template.
The workbook template includes a fingerprint describing an input schema hierarchy. Specifically, the fingerprint refers to a description of the expected schema hierarchy for data used by that particular workbook template. The schema hierarchy refers to the structure of data on a cloud-based data warehouse. The schema hierarchy may include databases, folders, tables, and columns and relationships between elements. The fingerprint describes the expected inputs for a workbook created using the workbook template. The fingerprint may describe elements in the schema hierarchy such that exact name matches are not required to determine data pathways between the elements of the input schema hierarchy and the database schema and folders of the data in the cloud-based data warehouse (and thus use the data to create a workbook using the workbook template).
Receiving 402 the request 420 to create the workbook 424 from a workbook template may also be carried out by receiving a selection, by a client, of the workbook template from a repository of workbook templates presented to the client. For example, a client may access a workbook template repository, such as a template store, and select one of the presented workbook templates. The workbook templates may be organized by data type, industry, creator, etc.
The workbook template may be created by receiving an original workbook and converting the schema hierarchy in the original workbook into the fingerprint describing the input schema hierarchy. Converting the schema hierarchy into the fingerprint may include determine broadened descriptions for each data path used by the original workbook. The broadened descriptions may then be collected as the input schema hierarchy for the workbook template.
The method of
Matching the fingerprint of the workbook template to the schema hierarchy of the data in the cloud-based data warehouse 192 may include, for each element in the input schema hierarchy, determining an existence and location for the corresponding element in the data database schema and folders on the cloud-based data warehouse 192. The existence and location for the corresponding elements may be determined using a variety of methods. For example, the similarity between the names (e.g., a table name) of elements in the input schema hierarchy and data on the cloud-based data warehouse may indicate a match or potential match. As another example, the location of one element relative to another element within the data on the cloud-based data warehouse may indicate a match with an element with a similar relative location in the input schema hierarchy. A cumulation of match indicators may be used to make a final determination regarding whether two elements match and therefore may be used to create a data pathway.
The method of
The above limitations improve the operation of the computer system by enabling a client to offload workbook creation to a workbook template creator. The above limitations further improve the operation of the computer system by providing workbook templates to clients who lack the ability to create complex analysis tools on their own. This is performed by using templates to create workbooks by determining a set of data pathways that allow the template to retrieve the appropriate categories of data for presentation in the workbook by the table manager.
For further explanation,
The method of
For further explanation,
The method of
The first table name may be matched to the second table name based on column names in the second table identified by the second table name. Specifically, in addition to the process described above, the table manager may also attempt to match a table in the input schema hierarchy to a table on the cloud-based data warehouse based on the names of columns within that table. A match for a table may be found if the tables include the same or similar column names. For example, a table “sales” in the input schema hierarchy with columns “date”, “item” and “quantity” may be matched to a table name “orders” with columns “date”, “item” and “quantity” in the schema hierarchy of the data in the cloud-based data warehouse 192. These processes may be used in conjunction with one another, as well as other not specifically described.
In view of the explanations set forth above, readers will recognize that the benefits of workbook template sharing according to embodiments of the present invention include:
Exemplary embodiments of the present invention are described largely in the context of a fully functional computer system for workbook template sharing. Readers of skill in the art will recognize, however, that the present invention also may be embodied in a computer program product disposed upon computer readable storage media for use with any suitable data processing system. Such computer readable storage media may be any storage medium for machine-readable information, including magnetic media, optical media, or other suitable media. Examples of such media include magnetic disks in hard drives or diskettes, compact disks for optical drives, magnetic tape, and others as will occur to those of skill in the art. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a computer program product. Persons skilled in the art will recognize also that, although some of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.
The present invention may be a system, a method, and/or a computer program product. 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. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
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, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. 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. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
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 comprises 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 comprises 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.
It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.
