The subject technology generally relates to information retrieval, and in particular to generating search results.
A search engine results page usually includes a list of search results returned by a search engine in response to a query (e.g., a text or image query). Each search result may include a link to a web page, and a section of the web page showing content from the web page that is responsive to the query.
The disclosed subject matter relates to generating search results. The method includes receiving a query, obtaining a search result that is responsive to the query, obtaining content from a social networking service that is responsive to the query and related to the search result, modifying the search result to include a first portion associated with the content from the social networking service, providing for display the modified search result and an interface component for receiving a request for interacting with the content, and modifying the search result to include a second portion of the content and to provide an interface to facilitate an interaction in response to receiving a request for interacting with the content.
The disclosed subject matter relates to a non-transitory computer-readable medium that includes instructions. The instructions include code for receiving a query, obtaining a search result that is responsive to the query, issuing a second query to a social networking service to obtain content that is responsive to the query and related to the search result, modifying the search result to include a first portion associated with the content from the social networking service, providing for display the modified search result and an interface component for receiving a request for interacting with the content, and modifying the search result to include a second portion of the content and to provide an interface to facilitate an interaction in response to receiving a request for interacting with the content.
The disclosed subject matter relates to a system that includes a computer. The computer is configured to receive a query, obtain a search result that is responsive to the query, issue a second query to obtain content from a social networking service that is responsive to the query and related to the search result, modify the search result to include a first portion associated with the content from the social networking service, provide for display the modified search result and an interface component for receiving a request for interacting with the content, modify the search result to include a second portion of the content and to provide an interface to facilitate an interaction in response to receiving a request for interacting with the content, and provide for display information received during the interaction together with the modified search result.
Various configurations of the subject technology are shown and described by way of illustration. As will be realized, the subject technology is capable of other and different configurations and its several details are capable of modification in various other respects, all without departing from the scope of the subject technology. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.
The detailed description set forth below is intended as a description of various configurations of the subject technology and is not intended to represent the only configurations in which the subject technology may be practiced. The appended drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a thorough understanding of the subject technology. However, the subject technology is not limited to the specific details set forth herein and may be practiced without these specific details.
Some search engine results pages include annotations of posts from a social networking site. However, to read more details of the posts and interact with the posts, a user may have to leave the search engine results page and log in the social networking site. Therefore, it would be desirable to provide a method and system for integrating posts from a social networking site into search engine results pages and making the posts interactive inline.
In some implementations, the may be indexed, and information associated with the index can indicate whether an author of a post is an expert on a particular topic.
The user device 401 may include a processor 4011, a network interface 4012 and a memory 4013. The processor 4011 is configured to execute computer instructions that are stored in a computer-readable medium, for example, the memory 4013. The processor 4011 may be a central processing unit (CPU). The network interface 4012 is configured to allow the user device 401 to transmit and receive data in the network 403. The network interface 4012 may include one or more network interface cards (NICs). The memory 4013 stores data and instructions. As illustrated, the memory 4013 may store a web browser 4014. With the web browser 4014, a user may submit a query to a search website (e.g., a search website run by the search engine 404), get a search engine results page in response, click on links on the search engine results page to view the results, and interact inline with posts on the search engine results page. A user may also log in a social networking site (e.g., a social networking site run by the social networking server 405) to create and change social graphs.
In some implementations, the search engine results page may also include one or more expert post summaries, e.g., expert post summaries 301 or 302 shown in
In some implementations, the search engine results page may also include search results from other sources, e.g., web chat and comments on the web.
At 803, it may be determined whether there is a user input on a post summary (e.g., the post summary 1011, 1012, 2011, 2012, 2013, 301 or 302 shown in
At 805, the entire post may be displayed inline on the search engine results page, as shown in
The bus 1005 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 1000. For instance, the bus 1005 communicatively connects the processing unit(s) 1010 with the read-only memory 1020, the system memory 1015, and the permanent storage device 1025.
From these various memory units, the processing unit(s) 1010 retrieves instructions to execute and data to process in order to execute the processes of the subject technology. The processing unit(s) can be a single processor or a multi-core processor in different implementations.
The read-only-memory (ROM) 1020 stores static data and instructions that are needed by the processing unit(s) 1010 and other modules of the electronic system. The permanent storage device 1025, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 1000 is off. Some implementations of the subject technology use a mass-storage device (for example a magnetic or optical disk and its corresponding disk drive) as the permanent storage device 1025.
Other implementations use a removable storage device (for example a floppy disk, flash drive, and its corresponding disk drive) as the permanent storage device 1025. Like the permanent storage device 1025, the system memory 1015 is a read-and-write memory device. However, unlike storage device 1025, the system memory 1015 is a volatile read-and-write memory, such a random access memory. The system memory 1015 stores some of the instructions and data that the processor needs at runtime. In some implementations, the processes of the subject technology are stored in the system memory 1015, the permanent storage device 1025, or the read-only memory 1020. For example, the various memory units include instructions for providing a search engine results page in accordance with some implementations. From these various memory units, the processing unit(s) 1010 retrieves instructions to execute and data to process in order to execute the processes of some implementations.
The bus 1005 also connects to the input and output device interfaces 1030 and 1035. The input device interface 1030 enables the user to communicate information and select commands to the electronic system. Input devices used with input device interface 1030 include, for example, alphanumeric keyboards and pointing devices (also called “cursor control devices”). Output device interfaces 1035 enables, for example, the display of images generated by the electronic system 1000. Output devices used with output device interface 1035 include, for example, printers and display devices, for example cathode ray tubes (CRT) or liquid crystal displays (LCD). Some implementations include devices for example a touchscreen that functions as both input and output devices.
Finally, as shown in
The above-described features and applications can be implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium). When these instructions are executed by one or more processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, RAM chips, hard drives, EPROMs, etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.
In this specification, the term “software” is meant to include firmware residing in read-only memory or applications stored in magnetic storage, which can be read into memory for processing by a processor. Also, in some implementations, multiple software technologies can be implemented as sub-parts of a larger program while remaining distinct software technologies. In some implementations, multiple software technologies can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software technology described here is within the scope of the subject technology. In some implementations, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.
A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
These functions described above can be implemented in digital electronic circuitry, in computer software, firmware or hardware. The techniques can be implemented using one or more computer program products. Programmable processors and computers can be included in or packaged as mobile devices. The processes and logic flows can be performed by one or more programmable processors and by one or more programmable logic circuitry. General and special purpose computing devices and storage devices can be interconnected through communication networks.
Some implementations include electronic components, for example microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra density optical discs, any other optical or magnetic media, and floppy disks. The computer-readable media can store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, for example is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.
While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some implementations are performed by one or more integrated circuits, for example application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some implementations, such integrated circuits execute instructions that are stored on the circuit itself.
As used in this specification and any claims of this application, the terms “computer”, “server”, “processor”, and “memory” all refer to electronic or other technological devices. These terms exclude people or groups of people. For the purposes of the specification, the terms display or displaying means displaying on an electronic device. As used in this specification and any claims of this application, the terms “computer readable medium” and “computer readable media” are entirely restricted to tangible, physical objects that store information in a form that is readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.
To provide for interaction with a user, implementations of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.
The subject matter described in this specification can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks).
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In some aspects of the disclosed subject matter, a server transmits data (e.g., an HTML page) to a client device (e.g., for purposes of displaying data to and receiving user input from a user interacting with the client device). Data generated at the client device (e.g., a result of the user interaction) can be received from the client device at the server.
It is understood that any specific order or hierarchy of steps in the processes disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged, or that all illustrated steps be performed. Some of the steps may be performed simultaneously. For example, in certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components illustrated above should not be understood as requiring such separation, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Various modifications to these aspects will be readily apparent, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, where reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more.” Unless specifically stated otherwise, the term “some” refers to one or more. Pronouns in the masculine (e.g., his) include the feminine and neuter gender (e.g., her and its) and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the subject technology.
A phrase for example an “aspect” does not imply that the aspect is essential to the subject technology or that the aspect applies to all configurations of the subject technology. A disclosure relating to an aspect may apply to all configurations, or one or more configurations. A phrase for example an aspect may refer to one or more aspects and vice versa. A phrase for example a “configuration” does not imply that such configuration is essential to the subject technology or that such configuration applies to all configurations of the subject technology. A disclosure relating to a configuration may apply to all configurations, or one or more configurations. A phrase for example a configuration may refer to one or more configurations and vice versa.
This application claims the benefit under 35 U.S. C. §119(e) of U.S. Provisional Application No. 61/599,395, filed Feb. 15, 2012, and entitled “Modifying Search Results,” the entire disclosure of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
6252597 | Lokuge | Jun 2001 | B1 |
6535888 | Vijayan et al. | Mar 2003 | B1 |
6594670 | Genser | Jul 2003 | B1 |
6598043 | Baclawski | Jul 2003 | B1 |
6665836 | Wynblatt et al. | Dec 2003 | B1 |
6758394 | Maskatiya et al. | Jul 2004 | B2 |
6763351 | Subramaniam et al. | Jul 2004 | B1 |
6785670 | Chiang et al. | Aug 2004 | B1 |
6961731 | Holbrook | Nov 2005 | B2 |
7039875 | Khalfay et al. | May 2006 | B2 |
7076743 | Ingram et al. | Jul 2006 | B2 |
7162493 | Weiss et al. | Jan 2007 | B2 |
7228506 | Ivanovic et al. | Jun 2007 | B2 |
7299222 | Hogan et al. | Nov 2007 | B1 |
7493315 | Holbrook | Feb 2009 | B2 |
7725405 | Johnson | May 2010 | B2 |
8041709 | Permandla et al. | Oct 2011 | B2 |
8073830 | Fontes et al. | Dec 2011 | B2 |
8255381 | Fontes et al. | Aug 2012 | B2 |
8650210 | Cheng et al. | Feb 2014 | B1 |
20020010623 | Mccollom et al. | Jan 2002 | A1 |
20020042799 | Slotznick | Apr 2002 | A1 |
20020118214 | Card et al. | Aug 2002 | A1 |
20020133566 | Teeple | Sep 2002 | A1 |
20020194162 | Rios et al. | Dec 2002 | A1 |
20030046259 | Manrique et al. | Mar 2003 | A1 |
20030053091 | Tanaka et al. | Mar 2003 | A1 |
20030146937 | Lee | Aug 2003 | A1 |
20030146939 | Petropoulos et al. | Aug 2003 | A1 |
20030169293 | Savage | Sep 2003 | A1 |
20040017393 | Easwar | Jan 2004 | A1 |
20040090464 | Shake et al. | May 2004 | A1 |
20040203854 | Nowak | Oct 2004 | A1 |
20040205638 | Thomas et al. | Oct 2004 | A1 |
20040205715 | Taylor | Oct 2004 | A1 |
20040225922 | Susarla et al. | Nov 2004 | A1 |
20050144158 | Capper et al. | Jun 2005 | A1 |
20050240391 | Lekutai | Oct 2005 | A1 |
20050261891 | Chan et al. | Nov 2005 | A1 |
20050278314 | Buchheit | Dec 2005 | A1 |
20060048051 | Lazaridis | Mar 2006 | A1 |
20060059418 | Elkady | Mar 2006 | A1 |
20060069670 | Khaliq et al. | Mar 2006 | A1 |
20060074868 | Khaliq et al. | Apr 2006 | A1 |
20060095424 | Petropoulos et al. | May 2006 | A1 |
20060173824 | Bensky et al. | Aug 2006 | A1 |
20060200455 | Wilson | Sep 2006 | A1 |
20060200767 | Glaeske et al. | Sep 2006 | A1 |
20060248078 | Gross et al. | Nov 2006 | A1 |
20060294476 | Buckley | Dec 2006 | A1 |
20080071739 | Kumar et al. | Mar 2008 | A1 |
20090043689 | Yang et al. | Feb 2009 | A1 |
20090307188 | Oldham et al. | Dec 2009 | A1 |
20120110464 | Chen et al. | May 2012 | A1 |
20120110474 | Chen et al. | May 2012 | A1 |
20130036109 | Kulick et al. | Feb 2013 | A1 |
20130110802 | Shenoy et al. | May 2013 | A1 |
20130144868 | Ickman et al. | Jun 2013 | A1 |
20130179427 | Archambault et al. | Jul 2013 | A1 |
20130179428 | Archambault et al. | Jul 2013 | A1 |
20130198177 | Oldham et al. | Aug 2013 | A1 |
Number | Date | Country |
---|---|---|
02019172 | Mar 2002 | WO |
2006001920 | Jan 2006 | WO |
2007059503 | May 2007 | WO |
Entry |
---|
International Search Report and Written Opinion dated May 2, 2007 (13 pages total). |
International Preliminary Report on Patentability issued in corresponding international application No. PCT/US2007/065472, mailed Oct. 9, 2008, 7 pages. |
International Preliminary Report on Patentability issued in corresponding international application No. PCT/US2006/060906, 8 pages. |
European Search Report corresponding to EP 07 759 675 mailed Oct. 5, 2011, 7 pages. |
Office Action from U.S. Appl. No. 11/394,192, dated Apr. 30, 2009, 18 pages. |
Office Action from U.S. Appl. No. 11/394,192, dated Dec. 17, 2009, 14 pages. |
Office Action from U.S. Appl. No. 11/394,192, dated Jul. 7, 2010, 20 pages. |
Office Action from U.S. Appl. No. 11/394,192, dated Feb. 2, 2011, 25 pages. |
Office Action from U.S. Appl. No. 12/084,957, dated Dec. 7, 2011, 49 pages. |
Office Action from U.S. Appl. No. 12/084,957, dated May 8, 2012, 82 pages. |
Office Action from U.S. Appl. No. 12/084,957, dated Oct. 15, 2012, 61 pages. |
Office Action from U.S. Appl. No. 13/615,966 dated Oct. 29, 2013, 17 pages. |
About.com: “Binoculars FAQ”; http://websearch.about.com; Mar. 22, 2006 (print date), 3 pages. |
Browster: “Browse Search Results Instantly!” www.browster.com; Mar. 16, 2006 (print date), 8 pages. |
Dan Farber: “Browsing at 2x Normal Speed”; http://blogs.zdnet.com/BTL; Feb. 14, 2005, 2 pages. |
Dieberger et al., “Exploratory Navigation in Large Multimedia Documents using Context Lenses,” Systems Sciences, 2001, Proceedings of the 35th Hawaii International Conference on System Sciences—Jan. 7, 2001, pp. 1462-1468 (7 pages total). |
Jones et al.: “Interactive Document Summarisation Using Automatically Extracted Keyphrases”; Proceedings of the 35th Annual Hawaii International Conference on System Sciences; Jan. 7-10, 2001,10 pages. |
Roberts et al., “Visual Bracketing for Web Search Result Visualization”, Proceedings of Information Visualization (1V03), pp. 264-269, IEEE Computer Society, Jul. 2003. |
Ulicny, Lycos Retriever: An Information Fusion Engine, Versatile Information System, Inc., 4 pages. |
Xiaoming Li et al., “Search Engine: Principles, Techniques and Systems”, Science Publishing House, Apr. 2005, 19 pages. (English description included). |
OMA Open Mobile Alliance, OMA Release Program and Specifications, http://www.opetnnobilealliance.org/release—program/index.html, Copyright 2002, [retrieved from internet on Jun. 6, 2005], pp. 1-4. |
OMA Open Mobile Alliance, OMA Enabler Releases and Specifications—OMA Browsing V2.3 Candidate Enabler, http://www.openmobilealliance.org/release—program/browsing—v23.html, Copyright 2002, [retrieved from internet on Jun. 6, 2005], pp. 1-2. |
OMA Open Mobile Alliance, OMA Enabler Releases and Specifications—OMA User Agent Profile V2.0 Candidate Enabler, http://www.openmobilealliance.org/release—program/uap—v20.html, Copyright 2002, [retrieved from internet on Jun. 6, 2005], p. 1. |
OMA Open Mobile Alliance, OMA Enabler Releases and Specifications—OMA Browser Protocol Stack 2.1 Candidate Enabler, http://www.openmobileailiance.org/release—program/browser—protocol—v21.html, Copyright 2002, [retrieved from internet on Jun. 6, 2005], pp. 1-2. |
OMA Open Mobile Alliance, WV-040 System Architecture Model, Approved Version 1.2—Jan. 25, 2005, pp. 1-15. |
OMA Open Mobile Alliance, User Agent Profile, http://www.openmobilealliance.org/copyright.html, Version 20—May 2003, pp. 1-47. |
W@P Wireless Application Forum, WMLScript Specification, http://www.wapforum.org/docs/copyright.htm., Version 25—Oct. 2000, pp. 1-136. |
OMA Open Mobile Alliance, OMA Service Environment, Approved Version 1.0—Sep. 7, 2004, pp. 1-32. |
W@P Wireless Application Protocol Forum, Wireless Application Environment Defined Media Type Specification, http://www.wapforum.org/what/copyright.htm, Version 15—May 2001, pp. 1-13. |
W@P, Wireless Application Protocol Forum, HTTP State Management Specification, http://www.wapforum.org/docs/copyright.htm, Dec. 13, 2000, pp. 1-13. |
W@P Wireless Application Protocol Forum, WAP-120-UACACH-20010413-a, httn://www.wapforum.org/what/copyright.htm, Version 013—Apr. 2001, pp. 1-13. |
W@P Wireless Application Protocol Forum, XHTML Mobile Profile, http://wapforum.org/what/copyright.htm, Version 29—Oct. 2001, pp. 1-17. |
W@P Wireless Application Protocol Forum, WAP WML WAP-191-WML, http://wapforum.org/what/copyright.thm, Feb. 19, 2000, pp. 1-110. |
W@P Wireless Application Protocol Forum, Wireless Markup Language, http://www.wapforum.org/what/copyright.htm, Version 11—Sep. 2001, pp. 1-69. |
OMA Open Mobile Alliance, Wireless Transaction Protocol, Version Aug. 27, 2002, pp. 1-75. |
OMA Open Mobile Alliance, Wireless Profiled TCP, Version Mar. 31, 2001, pp. 1-18. |
OMA Open Mobile Alliance, Wireless Profiled HTTP, Version Oct. 31, 2001, pp. 1-16. |
OMA Open Mobile Alliance, Wireless Datagram Protocol, Version Jun. 14, 2001, pp. 1-75. |
Office Action issued in U.S. Appl. No. 13/615,966 on Jun. 4, 2014, 21 pages. |
Number | Date | Country | |
---|---|---|---|
61599395 | Feb 2012 | US |