Query templates and labeled search tip system, methods, and techniques

• US 8,954,469 B2
• Filed: 03/14/2008
• Issued: 02/10/2015
• Est. Priority Date: 03/14/2007
• Status: Active Grant

• Current Assignee: Fiver LLC
• Original Assignee: Vcvciii LLC
• Inventors: Dhillon, Navdeep S., Reichhold, Jonathan D., Tusk, Carsten
• Primary Examiner(s): Mofiz, Apu
• Assistant Examiner(s): DAYE, CHELCIE L
• Application Number:
  US12/049,184
• Publication Number:
  US 20090019020A1
• Time in Patent Office: 2,524 Days
• Field of Search: 707/3, 707/4, 707/779
• US Class Current: 707/779
• CPC Class Codes: G06F 16/2428 Query predicate definition using graphical user interfaces, including menus and forms G06F16/2423 takes precedence
• CPC Class Codes: G06F 16/24578 using ranking
• CPC Class Codes: G06F 16/248 Presentation of query results
• CPC Class Codes: G06F 16/30 of unstructured textual data document management systems G06F16/93
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques

Abstract

Methods, systems, and techniques for creating, managing, and using query templates to facilitate the execution of relationship queries are provided. Example embodiments provide a Query Template System “QTS”, which enables users, a system, program code, or other people or code to define search tips (i.e., predefined searches) through the generation of query templates that can be used by other users or code, to perform relationship searches using IQL. In one embodiment, the QTS includes a QT editor, a QT dispatcher, a QT creation and index management system, and one or more QT data repositories and indexes. These components cooperate to create and maintain query templates and to search for and retrieve matching query templates.

Claims

1. A method in a computing system for facilitating providing augmented information, comprising:

receiving one or more previously generated query templates, each previously generated query template including a relationship query specification that specifies a relationship query that includes an input specification and an output presentation specification as part of the relationship query;

storing the received one or more query templates in a data repository;

in response to receiving an indication of an entity, an entity type, or a link that triggers a match of one or more query templates,

retrieving one or more of the matching query templates from the data repository; and

for each of the retrieved one or more matching query templates, causing a user interface to be presented to obtain user input based upon the input specification of the relationship query specified by the relationship query specification and supplying the obtained user input to the matching query template;

for each of the retrieved one or more matching query templates, automatically invoking the retrieved query template to cause the relationship query specified by the relationship query specification of the retrieved query template to be executed using the obtained user input according to the relationship query specification, and presenting search results according to the output presentation specification of the relationship query specified by the relationship query specification of the retrieved query template to provide information that augments the indicated entity in a manner specified by the query template.

2. The method of claim 1 wherein the data repository is an inverted index.

3. The method of claim 1 wherein an indication of an entity or entity type is received, and wherein each generated query template has at least an associated description or one or more associated trigger tags, and wherein the one or more matching query templates are determined at least in part based upon matching the received indication of the entity or entity type as a keyword against the associated description or the associated one or more trigger tags.

4. The method of claim 3 wherein the associated description or the associated one or more trigger tags are stored as keys in an inverted index of query templates.

5. The method of claim 1 wherein the method is invoked from a server that does not execute the method.

6. The method of claim 5 wherein the server provides a website used for social networking.

7. The method of claim 5 wherein the server provides information browsing capabilities.

8. The method of claim 5 wherein the server is used to implement a portal or a client-side code module.

15. The method of claim 1 wherein at least some of the previously generated query templates include trigger tags and further comprising matching the trigger tags against a received indication of an entity or entity type to determine which query templates match.

16. The method of claim 1 wherein the link is a url, pathname, question, or icon.

17. The method of claim 1 wherein at least some of the previously generated query templates include a description attribute that is presented to the user as part of the user interface.

18. The method of claim 1 wherein at least one of the output presentation specifications specified by a relationship query of a query template specifies output in a columnar format.

9. A computing system having one or more physical computing devices and, comprising:

one or more memories;

a relationship search engine stored in the one or more memories and configured, when invoked, to execute an indicated relationship search and to return search results;

a query template engine stored in the one or more memories and configured, when invoked, to

retrieve one or more query templates that match at least one of an indicated entity, entity type, topic, concept, ontology path, action, action type, or link;

cause the relationship search engine to be invoked with one or more relationship searches that are included in the one or more retrieved query templates, at least one of the relationship searches included in the one or more retrieved query templates specifying an output specification that indicates how search results of the associated relationship search are to be presented; and

forward relationship search results received from the relationship search engine for further presentation, wherein the search results of the at least one of the relationship searches are forwarded according to the output specification specified by the at least one of the relationship searches.

10. The computing system of claim 9 wherein the query template engine is configured to be invoked by another computing system that is distinct and separate from the computing system, the computing system used to present supplemental information to information being presented by the another computing system.

11. The computing system of claim 10 wherein the another computing system implements at least one of a portal or a widget that can be integrated in other applications or code modules.

12. The computing system of claim 9 wherein the query templates are stored in an inverted index.

13. The computing system of claim 9 wherein at least some of the query templates are automatically generated by a search tip system.

14. The computing system of claim 9 wherein at least some of the query templates are generated by an interactive interface or by editing existing query templates.

19. The computing system of claim 9 wherein the query template engine is invoked to process at least one query template triggered on a subscription basis.

20. The computing system of claim 9 wherein at least one of the relationship searches included in the one or more retrieved query templates specifies an input specification and wherein the query template engine is further configured, when invoked, to cause user input to be requested according to the input specification and forwarded to the relationship search engine when the relationship search engine is caused to be invoked with the at least one of the relationship searches.