This disclosure relates to building functions, and more particularly to dynamically building spreadsheet functions to access and display information.
Today, spreadsheet-based applications and programs, collectively referred herein as ‘spreadsheets’, are increasingly being utilized by people to interact with large amounts of data. Spreadsheets arrange data in rows and columns that define spreadsheet cells. Typically, spreadsheet cells allow a user to build functions which may include references to other cells, formulas, lists, as well as user-defined functions. As such, by providing the ability to specify functions in spreadsheets, spreadsheets have become a powerful tool for analyzing a wide range of data.
Building a spreadsheet function, however, is not an easy task. Typically, a user is required to remember a formula name and arguments, and/or memorize objects that are to be included in the function. Such technical requirements are further complicated when the user desires to access to data external to the spreadsheet. Accordingly, building a function can be slow and tedious work and often prevents a user from successfully completing their task.
Some spreadsheets utilize a “Function Wizard” to assist with building functions. Typically, a Function Wizard assists the user with entry of function parameters but does not allow the user to enter functions directly into spreadsheet cells. Thus, while assisting the user with certain aspects of function construction, Function Wizards only assist the user after proper syntax for a function has been manually entered. Consequently, Function Wizards associated with current spreadsheets neither free the user from the difficult task of remembering and entering proper function syntax and parameters nor assist the user in the construction of a function in its entirety.
Accordingly, there is a need for improved systems and techniques for building functions.
Systems and techniques are disclosed for dynamically generating functions. The systems and techniques may be utilized to access and display information from a data store accessible to a spreadsheet-based application or program over a network. A web service is also provided that interprets data requests received from the spreadsheet-based application or program in one format, such as a natural language format, and translates the requests into syntactically correct functions for automatic execution by the spreadsheet-based application or program.
Various aspects of the invention relate to identifying at least one keyword included in a request and generating an executable instruction based on the request.
For example, according to one aspect, a computer-implemented method for querying information includes obtaining, from a spreadsheet-based program, a data request in a first format, the first format being a natural language format, transmitting, from the spreadsheet-based program to a web service, the data request in the first format, and identifying, from the data request in the first format, at least one keyword. The method also includes comparing the at least one keyword to a data set of pre-defined keyword values, dynamically generating an executable instruction for the spreadsheet-based program in response to the comparison, and transmitting, from the web service and to the spreadsheet program, the generated instruction for execution.
In one embodiment, the generated instruction is automatically executed by the spreadsheet-based program. The generated instruction may invoke a market data platform to access a set of information, such as financial information. The method may also include displaying the set of accessed information in the spreadsheet-based program.
A system, as well as articles that include a machine-readable medium storing machine-readable instructions for implementing the various techniques, are disclosed. Details of various implementations are discussed in greater detail below.
Additional features and advantages will be readily apparent from the following detailed description, the accompanying drawings and the claims.
Like reference symbols in the various drawings indicate like elements.
In one embodiment, as shown in
The market data platform 15 is configured to provide information to the access device 12 relating to equities, commodities and energy, fixed income, foreign exchange and money market data. In one embodiment, the market data platform 15 also provides effective compliance and risk management, investment management, wealth management solutions, and financial models. The type of data may be historical data, real-time data (e.g., information that is delivered immediately after collection, and fundamentals data. One example of the market data platform is the Thomson Reuters Eikon® product.
The network 16 may include various devices such as routers, servers, and switching elements connected in an Intranet, Extranet or Internet configuration. In some embodiments, the network 16 uses wired communications to transfer information between the access device 12 and the server 14. In other embodiments, the network 16 employs wireless communication protocols. In yet other embodiments, the network 16 employs a combination of wired and wireless technologies.
As shown in
The web server 28 is configured to send syntactically correct spreadsheet function instructions to the add-in module 12B of the access device 12 in response to a request. As noted previously, the request may be in the form of a natural language description. The web server 28 may communicate with the add-in module 12B using one or more communication protocols, such as HTTP (Hyper Text Markup Language). In one embodiment, the web server 28 is configured to include the Java 2 Platform, Enterprise Edition (J2EE′).
The web server 28 provides a run-time environment that includes software modules for dynamically generating spreadsheet cell functions. As shown in the
The syntactic-analyzer module 30 analyzes user expressions for keyword names and then correlates the identified keyword names to pre-defined function names that are transmitted to the function-builder module 34 for function generation. The user expression may be received from the add-in module 12B or other functional modules included in the system 10 and may be based in a natural language format, such as a spoken language. In one embodiment, user expressions are passed to the syntactic-analyzer module 30 for analysis as arguments of an HTTP request transmitted from the add-in module 12B.
The instrument-resolver module 32 analyzes user expressions to determine financial instrument codes that may be associated with expressions. Example financial industry codes determined by the instrument-resolver module 32 include, but are not limited to Reuters Industry Codes (RICs). In one embodiment, the instrument-resolver module 32 employs table-lookup and fuzzy logic techniques to correlate at least a portion of a user expression with one or more financial industry codes stored in an instruments data store 44. The one or more financial industry codes are then transmitted to the function-builder module 34 for function generation. For example, the instrument-resolver module 32 may identify the RIC code ‘WMT.N’ based on a user expression including the phrase ‘Wal-Mart on the New York Stock Exchange’.
In one embodiment, the syntactic-analyzer module 30 transmits at least a portion of the user expression to the instrument-resolver module 32 for analysis. Of course, it will be appreciated by one skilled in the art that other means may be used to transmit at least a portion of the user expression. For example, in another embodiment, the function-builder 34 transmits at least a portion of the user expression to the instrument resolver module 32 for analysis. In yet other embodiments, the instrument-resolver module 32 receives the user expression from the add-in module 12B.
The function-builder module 34 dynamically generates functions by combining the results of the syntactic-analyzer module 30 and the instrument resolver module 32. In one embodiment, upon receiving the user expression from the add-in module 12B via an HTTP request, the function-builder module 34 initiates both the syntactic-analyzer module 30 and the instrument-resolver module 32. The function-builder module 34 then combines the results of the modules 30, 32 into an executable spreadsheet instruction which is transmitted to the add-in module 12B using an HTTP response.
As shown in the
The tutorial module 36 provides end-user guidance on use of the system. In one embodiment, the tutorial module 36 is configured to provide a context sensitive reference list of keywords supported by the system with keyword descriptions. The reference list of keywords may be dynamically generated and transmitted to the access device via HTTP responses and/or be HTML formatted.
As shown in
The instruments data store 44 stores financial instrument codes that are used to identify financial instruments and indices. For example, in one embodiment, the instruments data store 44 includes a set of RICs, which may be used for querying information on various Thomson Reuters financial information networks. In one embodiment, the operational data store 40 is a relational database. In another embodiment, the operational data store 40 is a directory server, such as a Lightweight Directory Access Protocol (‘LDAP’) server. In yet another embodiment, the operational data store 40 is a configured area in the non-volatile memory 24 of the device server 14. Although the operational data store 40 shown in
It should be noted that the system 10 shown in
Turning now to
The function-builder module 34, at step 54, parses the user expression included in the request, which in one embodiment is in the form of a string of characters, and identifies portions of the expression that may be analyzed by the syntactic-analyzer module 30 and the instrument-resolver module 32.
Next, at step 56, possible keywords included in the user expression are determined. In one embodiment, the function-builder module 34 transmits those portions of the user expression that may comprise keywords to the syntactic-analyzer module 30 for analysis. The syntactic-analyzer module 30 in turn compares the possible keywords to the pre-defined keywords stored in the keyword data store 42. If there is a match between a possible keyword and a pre-defined keyword, additional parameters associated with the pre-defined keywords, as shown in connection with
For those portions of the user expression that may relate to a financial asset, such as a bond, stock, currency, futures contract, company name, etc., the function-builder module 34 transmits those portions of the user expression to the instrument-resolver module 32. Similar to the syntactic-analyzer module 30, the instrument-resolver module 32 compares potential financial asset names included in the user expression to pre-defined financial asset identifiers stored in the instruments data store 44. The match may be based on table-lookup and/or fuzzy logic techniques. In one embodiment, if the instrument-resolver module 32 determines a match exists between the potential financial asset and a pre-defined financial asset identifier, the instrument-resolver module 32 transmits a corresponding RIC code associated with the pre-defined financial asset identifier to the function-builder module 34.
Once results from the syntactic-analyzer module 30 and the instrument-resolver module 32 are transmitted to the function-builder module 34, at step 58, the function-builder module 34 dynamically generates a response to the request. In one embodiment, the response is an HTTP response that includes a combination of results from the syntactic-analyzer module 30 and the instrument-resolver module 32 in the form of a native spreadsheet function. Once the native spreadsheet function is generated, the function-builder module 34 transmits the response to the add-in module 12B. At step 60, upon receiving the response, the add-in module 12B copies the generated instruction to at least one spreadsheet cell. Lastly, at step 62, upon the generated instruction being copied to the at least one spreadsheet cell, the spreadsheet 12A executes the generated native language function.
Referring now to
In operation, an end-user first selects one or more cell 90 in the spreadsheet 12A. Next, in the text box 92, which in one embodiment is provided as a command bar, the end-user types a request i.e., natural language, and presses an enter key to validate. The add-in module 12B then generates an HTTP request which is then transmitted to the web server 28. A response to the request is then generated by the system as disclosed in connection with
Referring to
Various features of the system may be implemented in hardware, software, or a combination of hardware and software. For example, some features of the system may be implemented in one or more computer programs executing on programmable computers. Each program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system or other machine. Furthermore, each such computer program may be stored on a storage medium such as read-only-memory (ROM) readable by a general or special purpose programmable computer or processor, for configuring and operating the computer to perform the functions described above.
This application claims priority to U.S. Provisional Application No. 61/737,430 filed Dec. 14, 2012, entitled ‘DYNAMIC FUNCTION BUILDER’, the content of which is incorporated herein in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
6138130 | Adler et al. | Oct 2000 | A |
6779151 | Cahill et al. | Aug 2004 | B2 |
6988241 | Guttman et al. | Jan 2006 | B1 |
7392238 | Zhou et al. | Jun 2008 | B1 |
8239751 | Rochelle et al. | Aug 2012 | B1 |
8589869 | Wolfram | Nov 2013 | B2 |
20050289124 | Kaiser et al. | Dec 2005 | A1 |
20060069696 | Becker et al. | Mar 2006 | A1 |
20060129932 | Weber et al. | Jun 2006 | A1 |
20060131383 | Battagin et al. | Jun 2006 | A1 |
20060282818 | DeSpain | Dec 2006 | A1 |
20080066052 | Wolfram | Mar 2008 | A1 |
20080126465 | Delaney | May 2008 | A1 |
20090055733 | Graeber | Feb 2009 | A1 |
20090112787 | Ginzberg | Apr 2009 | A1 |
20090125796 | Day et al. | May 2009 | A1 |
20090235154 | Khen | Sep 2009 | A1 |
20120151315 | Campbell et al. | Jun 2012 | A1 |
20130125094 | Wolfram | May 2013 | A1 |
20140136936 | Patel et al. | May 2014 | A1 |
Number | Date | Country |
---|---|---|
2014093831 | Jun 2014 | WO |
2014093831 | Aug 2014 | WO |
Entry |
---|
International Search Report and Written Opinion received for International Patent Application Serial No. PCT/US2013/075028 dated May 27, 2014, 8 pages. |
International Preliminary Report on Patentability received for International Patent Application Serial No. PCT/US2013/075028 dated Jun. 25, 2015, 8 pages. |
Number | Date | Country | |
---|---|---|---|
20140173400 A1 | Jun 2014 | US |
Number | Date | Country | |
---|---|---|---|
61738084 | Dec 2012 | US |