Aspects of the disclosure are related to computing hardware and software technology, and in particular to search technology and enhanced search services.
Information search services have become ubiquitous in the modern information technology landscape. Through these services, users are able to access a large volume of information in many different ways, ranging from performing general Internet searches to more individual searches of their desktop, mailbox, photos, documents, or other personal information. Users can engage with such services using desktop and laptop computers, tablets, smart phones, gaming devices, or any of a variety of other suitable appliances.
A wide variety of algorithms are employed to find search results that are relevant to a query. The search results are usually ranked in some order related to their relevance to a query. However, why a particular search result is ranked as it is, may not always be apparent to a user. Moreover, as the volume and variety of searchable information expands, it has become increasingly important that search results be presented in a more useful way. Some search services have addressed this concern by accentuating their results and rankings with other information, of which a user's social graph is a prominent example.
A social graph is a data structure that includes information representative of a set of people and their social connections. Social graphs generally include nodes representative of people and edges representative of the connections between them. Other types of nodes can be represented in a social graph, such as documents, projects, and web pages. When a search of a data repository is performed, the search results can be accentuated by taking into account a user's social graph.
In a brief illustration, a user may perform a search of a document repository that returns a set of documents related to a topic. The search results can be accentuated by searching the user's social graph for experts associated with the topic and returning relevant contacts along with the relevant documents for presentation to the user.
In another illustration, a user may perform a web search for a given topic. The search results can be accentuated by showing related endorsements by others in the user's social network. For instance, the user may search for a particular type of restaurant, in response to which a list of restaurants or links to their sites are returned, along with an indication of who in the user's social network “liked” each of the restaurants.
Provided herein are systems, methods, and software for facilitating enhanced search services. In an implementation, an enhanced search service receives a search query associated with a user and responsively identifies documents relevant to the search query. The enhanced search service also identifies a social label for each of the documents that is at least partly representative of how the document relates socially to the user. In some implementations, the social label for each document may be selected from a set of candidate labels based on an evaluation of each of the candidate labels. The enhanced search service replies to the search query with search results indicative of at least the documents and the social label for each of the documents.
This Overview is provided to introduce a selection of concepts in a simplified form that are further described below in the Technical Disclosure. It should be understood that this Overview is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Many aspects of the disclosure can be better understood with reference to the following drawings. While several implementations are described in connection with these drawings, the disclosure is not limited to the implementations disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.
Implementations disclosed herein are directed to social labeling for search results that describes at least one way in which each result is related to a user. In one implementation, such social labeling is supported by an enhanced search service that receives a search query associated with a user. The enhanced search service identifies a set of documents or other types of content in response to the search query. For each document of the set of documents, the enhanced search service identifies a social label that is representative of how the document relates socially to the user. Search results can then be returned to the source of the search that are indicative of the set of documents and the social label for each document.
In a brief illustration, a user may engage in a search by way of any of a variety of search sources. A search query is communicated to an enhanced search service, in response to which the service performs a search of a data repository to identify relevant results, such as a set of documents, web pages, contacts, emails, conversations, meeting invites, or other suitable items.
In addition, the enhanced search service identifies a social label for each item that may express how the item is related to the user. For instance, the social label for any given item may indicate how the user relates to the item. In some scenarios, the relationship between an item and the user is expressed by the social label in terms of another user or users associated with the user. As an example, a social label associated with a document in a set of results may identify a user that recently viewed, modified, or presented the document.
In some implementations, the social label for each item may be selected from a set of potential candidate labels. Selecting the social label from the candidate labels may involve identifying the relationships between the item and users related to the user, such as those in the user's social network, work colleagues, team members, or by some other association. For instance, for a given document, web page, photo, contact, or other item, the enhanced search service analyzes which users have viewed, modified, presented, or otherwise interacted with the item.
Each relationship that is discovered for an item in the search results is then compared to the candidate labels to identify which of the candidate labels relates to, or represents the relationship. It is thus possible for multiple relationships to exist that describe how a given item relates to a user. This may be the case when, for example, multiple other users have interacted with a document or other item, when an individual user has interacted in multiple ways with a given item, or for some other reasons.
Each of the candidate labels can be evaluated based on the relationship or relationships associated therewith to identify which of the candidate labels to use as the social label for a given item. For instance, each candidate label may be scored based on at least a representative trait that is shared in common by each of the candidate labels. The trait may be derived at least in part from a characteristic of each of those of the relationships that relate to each of the candidate labels. Examples of the trait include, but are not limited to, a freshness of each of the candidate labels or a popularity of each of the candidate labels. In still other examples, the strength of a relationship may be considered when evaluating each of the candidate labels. The strength of the relationship may in some situations pertain to how strong the social link is between a person involved in a relationship and the person on behalf of whom a search is being performed. For instance, one candidate label representative how one's boss relates to a document may be chosen as the social label for the document over another candidate label representative of how one's peer or direct report relates to the document. In another scenario, one candidate label representative how one's sibling relates to a document may be chosen as the social label for the document over another candidate label representative of how one's cousin or neighbor relates to the document.
In some implementations, a graph may be queried to identify the relationships between an item, such as a document, and various users. The graph may include nodes representative of documents and possibly other types of items, as well as nodes representative of various users. Edges in the graph may be representative of actions taken by the users with respect to the documents and other items. The relationships considered when selecting the social label for a given result may be representative of the actions taken with respect to each individual document or other items. Thus, relationships between users and search results can be determined by analyzing the nature of the edges connecting search results in the graph to specific users. Examples of possible actions include, but are not limited to, presenting, sharing, creating, modifying, commenting on, viewing, following, and liking a document that is included in a set of search results.
The candidate labels in some scenarios correspond to the various possible actions performed by the users. In such scenarios, the social label identified for the document or other items includes social information that represents at least in part how the document relates socially to the user associated with the search. The social information may describe the relationship in terms of an action taken with respect to the document by at least one various other users related to the user. Examples of the candidate labels include a presented-by label, a shared-by label, a created-by label, a modified-by label, a commented-on-by label, a viewed-by label, a followed-by label, and a liked-by label.
Referring now to the drawings,
Turning to
Enhanced search results 101 include search result 103, search result 105, and search result 107. Each of the search results identifies one item of various items returned by a search engine, as well as a social label corresponding to each item. Other types of content items in place of or in addition to documents are possible, such as photos, web pages, contacts, or any other type of item that can be identified in search results.
In particular, search result 103 identifies document 113 and a social label 123. Social label 123 includes social information representative of how document 113 relates to a user associated with the search. In this case, document 113, which is named alpha.doc, is identified as having been presented to the user by another person or people. Search result 105 includes document 115 (echo.doc) and social label 125. Social label 125 expresses that document 115 was viewed by another person or people associated with the user. Search result 107 includes document 115 (kilo.doc) and social label 127. Social label 125 includes social information that expresses that document 117 was modified recently by a person or people associated with the user.
Enhanced search results 101 may be presented to the user conducting the search in response to a search query. The social labels 123, 125, and 127 accompanying the documents 113, 115, and 117 in the search results 103, 105, and 107, serve to inform the user about how each item in the enhanced search results 101 relate to the user. For instance, social label 123 informs the user that document 113 was presented to her, social label 125 informs the user that document 115 was viewed by another person, and social label 127 informs the user that document 117 was modified recently by another person. This information may assist the user with navigating the enhanced search results 101 as how an item relates socially to the user may help distinguish one item over another.
In operation, query source 201 communicates a search query to enhanced search service 203. Query source 201 is representative of any source from which a search query may be initiated and to which search results may be returned. Query source 201 may be implemented in hardware, in software, or in some combination thereof. Examples of query source 201 include, but are not limited to, email applications, productivity applications, gaming applications, browser applications, operating system applications, social network applications, and any other suitable application, variation, or combination thereof. Such applications may be provisioned and delivered as locally installed and executed applications, browser-based applications, streamlining applications, or in some other manner. In addition, such applications may be experienced on any of a variety of computing systems, such as desktop, laptop, tablet, and notebook computers, smart phones, gaming machines, or any other physical or virtual system, variation, or combination thereof.
In response to the search query, enhanced search service 203 searches information repository 205 to identify documents or other items relevant to the search query. Enhanced search service 203 is representative of any service capable of receiving search queries and returning enhanced search results. Enhanced search service 203 may be a stand-alone search service or may be integrated with other services. Examples of enhanced search service include, but are not limited to, Internet search services, enterprise search services, desktop search services, file system search services, email search services, image search services, or any other suitable search service, variation of service, or combination thereof. Examples of other services with which enhanced search service 203 may be integrated include, but are not limited to, email services, productivity application services, gaming services, social network services, or any other service, variation, or combination thereof.
Enhanced search service 203 may search information repository 205 using any criteria, algorithm, or other such technology to identify relevant documents, emails, contacts, images, or other content items. A wide variety of search techniques are possible and may be considered within the scope of the present disclosure. Information repository 205 is representative of any collection of searchable information, such as a collection of documents, emails, images, web pages, blog posts, text messages, or the like. It may be appreciated that information repository 205 may include other information, such as an index or a graph, to facilitate a search of the content items included therein. Information repository 205 may be a stand-alone repository dedicated to enhanced search service 203 or it may be implemented in an integrated manner with another service or services. Examples of information repository 205 include, but are not limited to, an email mailbox, an Internet search index, an enterprise information storage facility, a document storage facility, an information backup facility, or any other suitable collection of searchable information. Information repository 205 may be implemented on any physical or virtual computing system or collection of computing systems, as well as on any variation or combination thereof.
Upon identifying a set of relevant documents or other content items, enhanced search service 203 employs social label process 300, discussed below with respect to
Social label process 300, illustrated in
In a brief illustration, a document that is returned by a search process may be related to the user in multiple ways. For instance, a person associated with the user may have recently presented the document to the user, while another person may have recently viewed the document. As such, two candidate labels may be generated that correspond to both relationships. It may be appreciated that a variety of relationships are possible, and thus so are a variety of candidate labels, and the scope of the present disclosure is not restricted to just those disclosed herein. The two candidate labels are then evaluated to determine which one to put forth as the social label for the document. The candidate labels may be evaluated based on any suitable criteria, such as the recentness of the relationships associated with each candidate label, a weight given to each type of relationship, a frequency of the relationship, and so on. In some examples, the strength of a relationship may be considered when evaluating each of the candidate labels. The strength of a social link between a person represented in a candidate label and the user associated with the search may be considered. For instance, one candidate label representative how one's manager relates to a document may be chosen as the social label for the document over another candidate label representative of how one's distant peer relates to the document. In another scenario, one candidate label representative how one's close relative relates to a document may be chosen as the social label for the document over another candidate label representative of how one's distant relative relates to the document. In any case, a social label is then selected from the candidate labels based on the evaluation (step 305).
This analysis and evaluation may be carried out for each document that is returned as part of the search, at the end of which a set of documents and a set of corresponding social labels for the documents are assembled. Search results indicative of the documents and their social labels are returned to query source 201 for consideration by the user. In some scenarios, the actual documents or other content items may be returned as part of the search results. However, in many implementations merely an indication of the documents will be returned. For example, a link to each document, an icon representative of each document, or some other indication of each document will be returned. The social labels as identified in the search results may include social information that describes how each document is related to the user. Other types of descriptive data may also be included, such as images of people, color coding, and the like.
Service interface 403 receives the search query from query source 401 and communicates it to search engine 405 for processing. Query source 401 is representative of any source from which a search query may be initiated and to which search results may be returned. Query source 401 may be implemented in hardware, in software, or in some combination thereof. Service interface 403 is representative of any interface to search engine 405 capable of receiving search queries, communicating them to search engine 405, and communicating enhanced search results to query source 401. Service interface 403 may be a stand-alone element or may be integrated with other elements of enhanced search service 402. In addition, service interface 403 may be implemented in hardware, in software, or in some variation or combination thereof.
Search engine 405 searches information repository 407 for any information items that may be relevant to the search query. Search engine 405 is representative of any search engine capable of searching information repository 407. Examples include Internet search engines, email search engines, document search engines, desktop search engines, file system search engines, social network search engines, or any other type of search facility, variation, or combination thereof. Search engine 405 may be implemented in hardware, software, or any variation or combination thereof.
Information repository 407 is representative of any collection of information that may be searched by search engine 405. Information repository 407 may include various documents, photos, contacts, emails, or other content items. Information repository 407 may also include an index to the items, although search engine 405 may maintain an index independently. A variety of information repositories 407 are possible and may be considered within the scope of the present disclosure.
In this scenario, it is assumed for exemplary purposes that search engine 405 identifies documents in information repository 407 that satisfy the search query. Search engine 405 identifies the documents to results integrator 411 such that the documents, or an indication thereof, may be included in enhanced search results.
Social label engine 409 is also made aware of which documents were found to be relevant to the search query. Social label engine 409 is representative of any service capable of identifying social labels for documents found to be relevant to a search query. Social label engine 409 may be implemented in hardware, in software, or in some variation or combination thereof.
While illustrated as coming from information repository 407, it may be search engine 405 or results integrator 411 that communicates with social label engine 409 to identify the relevant search results. In any case, social label engine 409 employs social label process 500, discussed below with respect to
In particular, graph service 415 monitors information repository 407 or services associated with for interactions with the various documents and other content items stored therein. For example, graph service 415 can monitor a document for when a user views, modifies, shares, or presents the document. The various interactions with the various documents on behalf of users may be considered events that are represented in graph 417.
Graph 417 includes nodes and edges representative of the documents, people, and relationships between them that are created when events occur. For example, graph 417 may include a node representative of a document and several other nodes representative of various people in an enterprise. The edges between them would then represent the various actions that the people may take with respect to the document. Graph service 415 may be implemented in a variety of ways that may be considered within the scope of the present disclosure. In other words, how graph service 415 operates and the structure or nature of graph 417 is not intended to limit the scope of the present disclosure.
Having identified a social label for each of the relevant documents, social label engine 409 communicates the social labels to results integrator 411. Results integrator 411 generates search results indicative of the relevant documents and the social labels associated with the relevant documents. Results integrator 411 is representative of any element or collection of elements capable of integrating documents identified by a search with corresponding social labels to generate enhanced search results. Results integrator 411 may be implemented in hardware, in software, or in some variation or combination thereof.
Results integrator 411 communicates the search results, which includes at least an indication of the documents and the social labels, to service interface 403. Service interface 403 then communicates the search results to query source 401. Query source 401 may then present the enhanced search results or otherwise process them such that the user associated with the search may consider the enhanced results.
Next, social label engine 409 determines for each document in the set of relevant documents which of the relationships relate to which of a pool of candidate labels (step 503). In an example, for a document that returned just one relationship, just one candidate label will be identified. However, for another document in the set that return two or more relationships, two or more candidate labels may be identified. In some scenarios, the number of candidate labels may match the number of relationships found for a document, while in other scenarios the number of candidate labels may not match the number of relationships. For example, a given document may return four different relationships, two of which are the same kind of relationship. In such a scenario, social label engine 409 would identify three distinct candidate labels from which to select the social label.
Having identified the candidate social labels, social label engine 409 evaluates each of the candidate social labels based on the relationship or relationships associated therewith (step 505). This may include, for example, assessing the age or freshness of a given relationship. This may be accomplished by time-stamping each edge in graph 417 such that the age of the corresponding relationships can be ascertained. In another example, the popularity of a given candidate label may be assessed. For example, a candidate label that has several relationships associated with it may be given a greater weight than another candidate label that has relatively fewer relationships associated with it. Other criteria include the identity of the other person or people associated with a given relationship. In some examples, the strength of a social link between a person represented in a candidate label and the user associated with the search may be considered, such as when any candidate label corresponding to a relationship associated with a high ranking person may be given priority over a candidate label associated via a relationship with a relatively lower ranking person. Many other criteria for evaluating the candidate labels are possible and may be considered within the scope of the present disclosure.
The social label for each document in the set of relevant documents is selected from the candidate labels for each document based on the evaluation discussed above (step 507). A scoring process or some other technique may be used to weight each candidate label in the evaluations. The candidate label having the highest score may then be used as the social label for a document. In some implementations it may be possible to use multiple social labels for a single document, although it is assumed for the sake of clarity that a single social label is selected for each individual document.
Document 601 is representative of any type of document with respect to which users may perform actions and otherwise interact. Examples of document 601 include, but are not limited to, word processing documents, spreadsheets and workbooks, drawings, and presentations, as well as any other type of document. While visualization 600 makes reference to document 601, it may be appreciated that such a visualization may apply as well to other types of content items, such as photos, music files, video files, blog posts, text messages, images, and contacts, as well as any other type of item with which relationships may be established by virtue of user interactions.
In visualization 600, document 601 has been interacted with in a variety ways by a variety of people. In particular, user 611 has viewed document 601. User 612 has viewed document 601 twice and presented it once. User 613 has presented document 601 and user 614 has modified it. User 615 has presented and viewed document 601. User 616 commented on document 601 and user 617 created it. Lastly, user 618 both modified and commented on document 601.
As mentioned, the relationships visualized in
In candidate label 701, social information included therein describes how the document relates to the user that initiated the search. In particular, candidate label expresses that document 601 was commented on by William on November 13th. Candidate label 703 expresses that document 601 was viewed by three people. Candidate label 705 expresses that document 601 was presented to James by Sarah on July 11th. Candidate label 708 expresses that document 601 was created by Kristin. Other candidate labels in addition to or in place of those disclosed herein are possible and may be considered within the scope of the disclosure.
It may be appreciated from candidate labels 701, 703, 705, and 707 that a wide variety of candidate labels are possible and may be considered within the scope of the present disclosure. In addition, a wide variety of social information may be presented within the candidate labels. The social label may be selected based on a wide variety of weighting criteria and other factors that are evaluated when selecting a social label. It is assumed for exemplary purposes in
Accordingly,
Examples of computing systems 801, 803, and 805 include, but are not limited to, desktop computers, work stations, laptop computers, notebook computers, tablet computers, mobile phones, personal digital assistances, media devices, gaming devices, and any other physical or virtual computing machine or combinations and variations thereof. Computing systems 801, 803, and 805 may be capable of implementing search sources 811, 813, and 815 respectively. Search sources 811, 813, and 815 may each be representative of any hardware, software, or combinations thereof capable of providing an interface to enhanced search service 817 such that users can interact with computing systems 801, 803, and 805 to perform searches. Examples of search sources 811, 813, and 815 include, but are not limited to, a search engine web page, a search engine tool integrated into another application (such as an email client or productivity application), a desktop search tool, a mobile search tool, or any other suitable search source.
Computing system 807 may be any computing system or collection of computing systems capable of implementing enhanced search service 817, which is representative of any enhanced search service, including enhanced search services 203 and 402. Computing system 809 may also be any computing system or collection of systems capable of implementing graph service 819. Graph service 819 is optional and may be excluded in some implementations. Examples of computing system 807 and computing system 809 include server computers, cloud computing platforms, data center equipment, physical or virtual computing machines, and any variation or combination thereof.
Computing system 900 is representative of any computing system suitable for implementing any of computing systems 801, 803, 805, 807, and 809, although the discussion below makes specific reference to computing system 807 for purposes of clarity. In addition, while enterprise search service 817 is illustrated as implemented separately from a search interface, or remotely from the devices with which a user may interact, it may be appreciated that in some implementations all or portions of enterprise search service 817 may be implemented locally with respect to a user, such as in a co-located fashion on a device operated by a user, of which computing systems 801, 803, and 805 are representative.
In operation, computing systems 801, 803, and 805 may communicate with computing system 807 to perform information searches. This may include communicating search requests to and receiving search replies from enhanced search service 817. Enhanced search service 817 handles the search requests in accordance with the various implementations described herein for enhanced search services 203 and 402.
In addition, computing systems 801, 803, and 805 may communicate from time to time with computing system 809 in the context of facilitating graph service 819. Computing system 801, 803, and 805 may communicate with other services that may be separate from enhanced search service 817 or that may include enhanced search service 817 therein, such as such as productivity application services, file storage services, email services, chat services, blog services, voice and video calling services, or any other type of application service. Some or all of the application services may be implemented locally or in part with respect to computing systems 801, 803, and 805. Within the context of these services, events may occur that can be captured and from which an enterprise graph or graphs may be constructed. Graph service 819 may capture the events and construct the graph, although in some implementations these tasks may be allocated to another service or services.
Communication between any of the elements contemplated in
In any of the aforementioned examples in which information is exchanged at least between search sources 811, 813, and 815 and enhanced search service 817, the exchange of information may occur in accordance with any of a variety of protocols, including FTP (file transfer protocol), HTTP (hypertext transfer protocol), REST (representational state transfer), Web Socket, DOM (Document Object Model), HTML (hypertext markup language), CSS (cascading style sheets), HTML5, XML (extensible markup language), JavaScript, JSON (JavaScript Object Notation), and AJAX (Asynchronous JavaScript and XML), as well as any other suitable protocol, variation, or combination thereof.
Referring now to
Computing system 900 may be implemented as a single apparatus, system, or device or may be implemented in a distributed manner as multiple apparatuses, systems, or devices. Examples of computing system 900 include server computers, rack servers, blade servers, cloud computing platforms, and data center equipment, as well as any other type of physical or virtual server machine, and any variation or combination thereof. While typically implemented in a server or collection of servers, enhanced search service 817 may also be implemented all or in part on desktop computers, laptop computers, tablet computers, notebook computers, mobile computing devices, cell phones, media devices, and gaming devices, as well as any other type of physical or virtual computing machine and any combination or variation thereof, of which computing system 900 may also be representative.
Computing system 900 includes, but is not limited to, processing system 901, storage system 903, software 905, communication interface system 907, and user interface system 909, which is optional. Processing system 901 is operatively coupled with storage system 903, communication interface system 907, and user interface system 909. Processing system 901 loads and executes software 905 from storage system 903. When executed by processing system 901, software 905 directs processing system 901 to operate as described herein for enhanced search service 203, enhanced search service 402, social label process 300, social label process 500, and any of the operational scenarios and examples disclosed herein. Computing system 900 may optionally include additional devices or functionality not discussed for purposes of brevity.
Referring still to
Storage system 903 may comprise any computer readable storage media readable by processing system 901 and capable of storing software 905. Storage system 903 may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable program instructions, data structures, program modules, or other data. Examples of storage media include random access memory, read only memory, solid state memory, magnetic disks, optical disks, flash memory, virtual memory and non-virtual memory, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other suitable storage media. In no case is the computer readable storage media a propagated signal.
In addition to computer readable storage media, in some implementations storage system 903 may also include computer readable communication media over which software 905 may be communicated internally or externally. Storage system 903 may be implemented as a single storage device but may also be implemented across multiple storage devices or sub-systems co-located or distributed relative to each other. Storage system 903 may comprise additional elements, such as a controller, capable of communicating with processing system 901 or possibly other systems.
Software 905 may be implemented in program instructions and among other functions may, when executed by processing system 901, direct processing system 901 to operate as described herein for social label process 300 or social label process 500 and their variations, and optionally as described with respect to the various operational scenarios and examples disclosed herein. In particular, the program instructions may include various components or modules that cooperate or otherwise interact to carry out social label process 300 or social label process 500. The various components or modules may be embodied in compiled or interpreted instructions or in some other variation or combination of instructions. The various components or modules may be executed in a synchronous or asynchronous manner, serially or in parallel, in a single threaded environment or multi-threaded, or in accordance with any other suitable execution paradigm, variation, or combination thereof. Software 905 may include additional processes, programs, or components, such as operating system software or other application software. Software 905 may also comprise firmware or some other form of machine-readable processing instructions executable by processing system 901.
In general, software 905 may, when loaded into processing system 901 and executed, transform a suitable apparatus, system, or device (of which computing system 900 is representative) overall from a general-purpose computing system into a special-purpose computing system customized to facilitate enhanced search services as described herein for each implementation. Indeed, encoding software 905 on storage system 903 may transform the physical structure of storage system 903. The specific transformation of the physical structure may depend on various factors in different implementations of this description. Examples of such factors may include, but are not limited, to the technology used to implement the storage media of storage system 903 and whether the computer-storage media are characterized as primary or secondary storage, as well as other factors.
For example, if the computer readable storage media are implemented as semiconductor-based memory, software 905 may transform the physical state of the semiconductor memory when the program instructions are encoded therein, such as by transforming the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory. A similar transformation may occur with respect to magnetic or optical media. Other transformations of physical media are possible without departing from the scope of the present description, with the foregoing examples provided only to facilitate this discussion.
Referring again to
It should be understood that computing system 900 is generally intended to represent a computing system or systems on which software 905 may be deployed and executed in order to implement enhanced search service 203 or enhanced search service 402, and optionally all or portions of the various operational scenarios and examples described herein. However, computing system 900 may also be suitable as any computing system on which software 905 may be staged and from where software 905 may be distributed, transported, downloaded, or otherwise provided to yet another computing system for deployment and execution, or yet additional distribution.
Communication interface system 907 may include communication connections and devices that allow for communication with other computing systems (not shown) over a communication network or collection of networks (not shown). Examples of connections and devices that together allow for inter-system communication may include network interface cards, antennas, power amplifiers, RF circuitry, transceivers, and other communication circuitry. The connections and devices may communicate over communication media to exchange communications with other computing systems or networks of systems, such as metal, glass, air, or any other suitable communication media. The aforementioned media, connections, and devices are well known and need not be discussed at length here.
Communication between computing system 900 and any other computing system (not shown) may occur over a communication network or networks and in accordance with various communication protocols, combinations of protocols, or variations thereof. Examples of communication networks over which computing system 900 may exchange information with other computing systems include intranets, the Internet, local area networks, wide area networks, wireless networks, wired networks, virtual networks, software defined networks, or any combination or variation thereof. The aforementioned communication networks and protocols are well known and need not be discussed at length here.
When applicable, user interface system 909 may include a keyboard, a mouse, a voice input device, a touch input device for receiving a touch gesture from a user, a motion input device for detecting non-touch gestures and other motions by a user, and other comparable input devices and associated processing elements capable of receiving user input from a user. Output devices such as a display, speakers, haptic devices, and other types of output devices may also be included in user interface system 909. In some cases, the input and output devices may be combined in a single device, such as a display capable of displaying images and receiving touch gestures. The aforementioned user input and output devices are well known in the art and need not be discussed at length here.
User interface system 909 may also include associated user interface software executable by processing system 901 in support of the various user input and output devices discussed above. Separately or in conjunction with each other and other hardware and software elements, the user interface software and user interface devices may support a graphical user interface, a natural user interface, or any other type of user interface. For example, a search interface to an enhanced search service may be presented through user interface system 909. In another example, search results returned from an enhanced search service that include social labels, may be presented through user interface system 909.
The functional block diagrams, operational scenarios and sequences, and flow diagrams provided in the Figures are representative of exemplary systems, environments, and methodologies for performing novel aspects of the disclosure. While, for purposes of simplicity of explanation, methods included herein may be in the form of a functional diagram, operational scenario or sequence, or flow diagram, and may be described as a series of acts, it is to be understood and appreciated that the methods are not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a method could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in a methodology may be required for a novel implementation.
The included descriptions and figures depict specific implementations to teach those skilled in the art how to make and use the best option. For the purpose of teaching inventive principles, some conventional aspects have been simplified or omitted. Those skilled in the art will appreciate variations from these implementations that fall within the scope of the invention. Those skilled in the art will also appreciate that the features described above can be combined in various ways to form multiple implementations. As a result, the invention is not limited to the specific implementations described above, but only by the claims and their equivalents.
Number | Name | Date | Kind |
---|---|---|---|
6434556 | Levin et al. | Aug 2002 | B1 |
6745195 | Kornfein et al. | Jun 2004 | B1 |
7031961 | Pitkow et al. | Apr 2006 | B2 |
7055168 | Errico et al. | May 2006 | B1 |
7143091 | Charnock et al. | Nov 2006 | B2 |
7444344 | Galindo-Legaria et al. | Oct 2008 | B2 |
7509320 | Hess | Mar 2009 | B2 |
7571121 | Bezos et al. | Aug 2009 | B2 |
7577718 | Slawson et al. | Aug 2009 | B2 |
7587101 | Bourdev | Sep 2009 | B1 |
7640236 | Pogue | Dec 2009 | B1 |
7756945 | Andreessen | Jul 2010 | B1 |
7761447 | Brill et al. | Jul 2010 | B2 |
7783630 | Chevaller et al. | Aug 2010 | B1 |
7788245 | Eddings | Aug 2010 | B1 |
7873641 | Frieden et al. | Jan 2011 | B2 |
7890501 | Lunt et al. | Feb 2011 | B2 |
7945571 | Wanker | May 2011 | B2 |
7958116 | House et al. | Jun 2011 | B2 |
7962481 | Ganesh et al. | Jun 2011 | B2 |
8005817 | Amer-Yahia et al. | Aug 2011 | B1 |
8060513 | Basco et al. | Nov 2011 | B2 |
8065383 | Carlson et al. | Nov 2011 | B2 |
8117197 | Cramer | Feb 2012 | B1 |
8204870 | Mukkamala et al. | Jun 2012 | B2 |
8204888 | Frieden et al. | Jun 2012 | B2 |
8209349 | Howes et al. | Jun 2012 | B2 |
8214325 | Navas | Jul 2012 | B2 |
8266144 | Tankovich et al. | Sep 2012 | B2 |
8301764 | Konig et al. | Oct 2012 | B2 |
8312056 | Peng et al. | Nov 2012 | B1 |
8341017 | Payne et al. | Dec 2012 | B2 |
8341150 | Riley et al. | Dec 2012 | B1 |
8346765 | Guo et al. | Jan 2013 | B2 |
8346950 | Andreessen | Jan 2013 | B1 |
8380562 | Toebes et al. | Feb 2013 | B2 |
8386515 | Bent et al. | Feb 2013 | B2 |
8463795 | Van Hoff | Jun 2013 | B2 |
8538959 | Jin et al. | Sep 2013 | B2 |
8548996 | Tareen et al. | Oct 2013 | B2 |
8572477 | Moskovitz | Oct 2013 | B1 |
8600981 | Chau et al. | Dec 2013 | B1 |
8601023 | Brave et al. | Dec 2013 | B2 |
8751621 | Vaynblat et al. | Jun 2014 | B2 |
8751636 | Tseng et al. | Jun 2014 | B2 |
8775334 | Lloyd et al. | Jul 2014 | B1 |
8782036 | Chen et al. | Jul 2014 | B1 |
8799296 | Agapiev | Aug 2014 | B2 |
8812947 | Maoz et al. | Aug 2014 | B1 |
8825649 | Eimendinger et al. | Sep 2014 | B2 |
8825711 | Chan et al. | Sep 2014 | B2 |
8874550 | Soubramanien et al. | Oct 2014 | B1 |
8886633 | Smyth et al. | Nov 2014 | B2 |
8898156 | Xu et al. | Nov 2014 | B2 |
8909515 | O'Neil et al. | Dec 2014 | B2 |
8984098 | Tomkins et al. | Mar 2015 | B1 |
8996631 | Staddon et al. | Mar 2015 | B1 |
9165305 | Chandra et al. | Oct 2015 | B1 |
9177293 | Gagnon | Nov 2015 | B1 |
9195679 | Svendsen | Nov 2015 | B1 |
9223866 | Marcucci et al. | Dec 2015 | B2 |
9438619 | Chan et al. | Sep 2016 | B1 |
9514191 | Solheim et al. | Dec 2016 | B2 |
9542440 | Wang et al. | Jan 2017 | B2 |
9576007 | Sivathanu | Feb 2017 | B1 |
20010034859 | Swoboda et al. | Oct 2001 | A1 |
20020038299 | Zernik et al. | Mar 2002 | A1 |
20020091736 | Wall | Jul 2002 | A1 |
20020169759 | Kraft et al. | Nov 2002 | A1 |
20030025692 | Lu et al. | Feb 2003 | A1 |
20030071814 | Jou et al. | Apr 2003 | A1 |
20030115271 | Weissman | Jun 2003 | A1 |
20040103088 | Cragun et al. | May 2004 | A1 |
20040255237 | Tong | Dec 2004 | A1 |
20040267736 | Yamane et al. | Dec 2004 | A1 |
20050076240 | Appleman | Apr 2005 | A1 |
20050076241 | Appelman | Apr 2005 | A1 |
20050201535 | LaLonde | Sep 2005 | A1 |
20050203929 | Hazarika | Sep 2005 | A1 |
20050246420 | Little, II | Nov 2005 | A1 |
20050278321 | Vailaya et al. | Dec 2005 | A1 |
20050278325 | Mihalcea et al. | Dec 2005 | A1 |
20060004892 | Lunt et al. | Jan 2006 | A1 |
20060074883 | Teevan et al. | Apr 2006 | A1 |
20060123014 | Ng | Jun 2006 | A1 |
20060168036 | Schulz | Jul 2006 | A1 |
20060294085 | Rose et al. | Dec 2006 | A1 |
20070162443 | Liu et al. | Jul 2007 | A1 |
20070192306 | Papakonstantinou et al. | Aug 2007 | A1 |
20070208751 | Cowan | Sep 2007 | A1 |
20080005064 | Sarukkai | Jan 2008 | A1 |
20080010337 | Hayes | Jan 2008 | A1 |
20080010350 | Chen | Jan 2008 | A1 |
20080016053 | Frieden et al. | Jan 2008 | A1 |
20080086344 | Martini et al. | Apr 2008 | A1 |
20080091549 | Chang et al. | Apr 2008 | A1 |
20080097968 | Delgado | Apr 2008 | A1 |
20090049053 | Barker et al. | Feb 2009 | A1 |
20090094233 | Marvit | Apr 2009 | A1 |
20090125560 | Munekuni | May 2009 | A1 |
20090132490 | Okraglik | May 2009 | A1 |
20090132516 | Patel et al. | May 2009 | A1 |
20090150866 | Schmidt | Jun 2009 | A1 |
20090182727 | Majko | Jul 2009 | A1 |
20090256678 | Ryu | Oct 2009 | A1 |
20090313295 | Blaxland | Dec 2009 | A1 |
20090327271 | Amitay | Dec 2009 | A1 |
20100063878 | Bachet et al. | Mar 2010 | A1 |
20100082695 | Hardt | Apr 2010 | A1 |
20100083151 | Lanza et al. | Apr 2010 | A1 |
20100169320 | Patnam | Jul 2010 | A1 |
20100169326 | Ma et al. | Jul 2010 | A1 |
20100179874 | Higgins et al. | Jul 2010 | A1 |
20100185610 | Lunt | Jul 2010 | A1 |
20100223266 | Balmin et al. | Sep 2010 | A1 |
20100268703 | Buck | Oct 2010 | A1 |
20100306185 | Smith | Dec 2010 | A1 |
20100332330 | Goel et al. | Dec 2010 | A1 |
20110004831 | Steinberg et al. | Jan 2011 | A1 |
20110040617 | Moonka et al. | Feb 2011 | A1 |
20110055241 | Lewis | Mar 2011 | A1 |
20110060803 | Barlin et al. | Mar 2011 | A1 |
20110087644 | Frieden et al. | Apr 2011 | A1 |
20110099167 | Galbreath et al. | Apr 2011 | A1 |
20110145275 | Stewart | Jun 2011 | A1 |
20110145719 | Chen | Jun 2011 | A1 |
20110153619 | Carter et al. | Jun 2011 | A1 |
20110214046 | Haberman et al. | Sep 2011 | A1 |
20110218946 | Stern et al. | Sep 2011 | A1 |
20110231381 | Mercuri | Sep 2011 | A1 |
20110264737 | Skinner | Oct 2011 | A1 |
20110271224 | Cruz Moreno et al. | Nov 2011 | A1 |
20120030169 | Allen et al. | Feb 2012 | A1 |
20120047114 | Duan et al. | Feb 2012 | A1 |
20120054303 | Priyadarshan et al. | Mar 2012 | A1 |
20120076367 | Tseng | Mar 2012 | A1 |
20120078896 | Nixon et al. | Mar 2012 | A1 |
20120079004 | Herman | Mar 2012 | A1 |
20120084291 | Chung | Apr 2012 | A1 |
20120124041 | Bawri | May 2012 | A1 |
20120158720 | Luan et al. | Jun 2012 | A1 |
20120158791 | Kasneci et al. | Jun 2012 | A1 |
20120209859 | Blount | Aug 2012 | A1 |
20120209878 | Park et al. | Aug 2012 | A1 |
20120210240 | Neystadt et al. | Aug 2012 | A1 |
20120215771 | Steiner | Aug 2012 | A1 |
20120215773 | Si et al. | Aug 2012 | A1 |
20120221558 | Byrne et al. | Aug 2012 | A1 |
20120221566 | Iwasa et al. | Aug 2012 | A1 |
20120239618 | Kung | Sep 2012 | A1 |
20120254790 | Colombino et al. | Oct 2012 | A1 |
20120271807 | Smyth et al. | Oct 2012 | A1 |
20120290399 | England et al. | Nov 2012 | A1 |
20120290637 | Perantatos et al. | Nov 2012 | A1 |
20120296918 | Morris et al. | Nov 2012 | A1 |
20120304215 | McCarthy et al. | Nov 2012 | A1 |
20120310922 | Johnson | Dec 2012 | A1 |
20120311139 | Brave et al. | Dec 2012 | A1 |
20120323998 | Schoen et al. | Dec 2012 | A1 |
20120324002 | Chen | Dec 2012 | A1 |
20120324027 | Vaynblat et al. | Dec 2012 | A1 |
20120330908 | Stowe | Dec 2012 | A1 |
20120330992 | Kanigsberg et al. | Dec 2012 | A1 |
20130006754 | Horvitz et al. | Jan 2013 | A1 |
20130013678 | Murthy | Jan 2013 | A1 |
20130031489 | Gubin et al. | Jan 2013 | A1 |
20130036230 | Bakos | Feb 2013 | A1 |
20130041896 | Ghani et al. | Feb 2013 | A1 |
20130054349 | Ogawa | Feb 2013 | A1 |
20130073280 | O'Neil et al. | Mar 2013 | A1 |
20130073568 | Federov et al. | Mar 2013 | A1 |
20130073632 | Fedorov et al. | Mar 2013 | A1 |
20130073979 | Shepherd et al. | Mar 2013 | A1 |
20130073983 | Rasmussen et al. | Mar 2013 | A1 |
20130080218 | Reapso | Mar 2013 | A1 |
20130086057 | Harrington | Apr 2013 | A1 |
20130091149 | Dunn et al. | Apr 2013 | A1 |
20130097143 | Shenoy et al. | Apr 2013 | A1 |
20130097184 | Berkhin et al. | Apr 2013 | A1 |
20130103683 | Haveliwala et al. | Apr 2013 | A1 |
20130110638 | Ogawa | May 2013 | A1 |
20130110802 | Shenoy | May 2013 | A1 |
20130110827 | Nabar | May 2013 | A1 |
20130110978 | Gordon et al. | May 2013 | A1 |
20130124257 | Schubert | May 2013 | A1 |
20130124437 | Pennacchiotti et al. | May 2013 | A1 |
20130124613 | Plache et al. | May 2013 | A1 |
20130132138 | Doganata et al. | May 2013 | A1 |
20130151611 | Graham et al. | Jun 2013 | A1 |
20130155068 | Bier et al. | Jun 2013 | A1 |
20130159096 | Santhanagopal et al. | Jun 2013 | A1 |
20130167059 | Legris | Jun 2013 | A1 |
20130191416 | Lee | Jul 2013 | A1 |
20130204706 | Tang et al. | Aug 2013 | A1 |
20130212081 | Shenoy et al. | Aug 2013 | A1 |
20130218885 | Satyanarayanan | Aug 2013 | A1 |
20130218899 | Raghavan et al. | Aug 2013 | A1 |
20130227011 | Sharma et al. | Aug 2013 | A1 |
20130238449 | Ferreira et al. | Sep 2013 | A1 |
20130238587 | Annau | Sep 2013 | A1 |
20130238588 | Annau | Sep 2013 | A1 |
20130246404 | Annau | Sep 2013 | A1 |
20130246405 | Annau | Sep 2013 | A1 |
20130246521 | Schacht et al. | Sep 2013 | A1 |
20130262588 | Barak | Oct 2013 | A1 |
20130268973 | Archibong et al. | Oct 2013 | A1 |
20130288715 | Shieh et al. | Oct 2013 | A1 |
20130290323 | Saib | Oct 2013 | A1 |
20130298084 | Spivack et al. | Nov 2013 | A1 |
20130326369 | Buchanon | Dec 2013 | A1 |
20130332523 | Luu | Dec 2013 | A1 |
20130346329 | Alib-Bulatao et al. | Dec 2013 | A1 |
20140007860 | Lu | Jan 2014 | A1 |
20140013353 | Mathur | Jan 2014 | A1 |
20140032563 | Lassen | Jan 2014 | A1 |
20140040008 | Belani et al. | Feb 2014 | A1 |
20140040244 | Rubinstein | Feb 2014 | A1 |
20140040245 | Rubinstein et al. | Feb 2014 | A1 |
20140040246 | Rubinstein et al. | Feb 2014 | A1 |
20140040367 | Lessin et al. | Feb 2014 | A1 |
20140040370 | Buhr | Feb 2014 | A1 |
20140040729 | Marlow et al. | Feb 2014 | A1 |
20140041038 | Lessin et al. | Feb 2014 | A1 |
20140046982 | Chan et al. | Feb 2014 | A1 |
20140074602 | van Elsas et al. | Mar 2014 | A1 |
20140074856 | Rao | Mar 2014 | A1 |
20140074888 | Potter et al. | Mar 2014 | A1 |
20140074934 | van Hoff et al. | Mar 2014 | A1 |
20140089401 | Filev | Mar 2014 | A1 |
20140114986 | Bierner et al. | Apr 2014 | A1 |
20140156652 | Abiola | Jun 2014 | A1 |
20140164388 | Zhang | Jun 2014 | A1 |
20140173459 | Gaiser et al. | Jun 2014 | A1 |
20140181083 | Macho et al. | Jun 2014 | A1 |
20140181091 | Lassen | Jun 2014 | A1 |
20140188899 | Whitnah et al. | Jul 2014 | A1 |
20140189530 | Anand et al. | Jul 2014 | A1 |
20140195605 | Kallayil | Jul 2014 | A1 |
20140195977 | Chang et al. | Jul 2014 | A1 |
20140207860 | Wang et al. | Jul 2014 | A1 |
20140208234 | Amit et al. | Jul 2014 | A1 |
20140215351 | Gansca et al. | Jul 2014 | A1 |
20140229293 | Huang et al. | Aug 2014 | A1 |
20140278986 | Rouse | Sep 2014 | A1 |
20140280080 | Solheim et al. | Sep 2014 | A1 |
20140280108 | Dunn et al. | Sep 2014 | A1 |
20140282029 | Vishria | Sep 2014 | A1 |
20140324850 | Magnaghi et al. | Oct 2014 | A1 |
20140330551 | Bao et al. | Nov 2014 | A1 |
20140330809 | Raina et al. | Nov 2014 | A1 |
20140330818 | Raina | Nov 2014 | A1 |
20140330819 | Raina | Nov 2014 | A1 |
20140337316 | Abuelsaad et al. | Nov 2014 | A1 |
20140344288 | Evans et al. | Nov 2014 | A1 |
20140359023 | Homsany | Dec 2014 | A1 |
20150039596 | Stewart | Feb 2015 | A1 |
20150039632 | Leppanen | Feb 2015 | A1 |
20150046515 | Pei et al. | Feb 2015 | A1 |
20150058758 | Tseng | Feb 2015 | A1 |
20150067505 | Metcalf et al. | Mar 2015 | A1 |
20150081449 | Ge et al. | Mar 2015 | A1 |
20150100644 | Gulik | Apr 2015 | A1 |
20150106191 | Ge et al. | Apr 2015 | A1 |
20150127677 | Wang et al. | May 2015 | A1 |
20150142785 | Roberts et al. | May 2015 | A1 |
20150187024 | Karatzoglou et al. | Jul 2015 | A1 |
20150220531 | Helvik et al. | Aug 2015 | A1 |
20150242402 | Holm et al. | Aug 2015 | A1 |
20150242473 | Brugard et al. | Aug 2015 | A1 |
20150248222 | Stickler et al. | Sep 2015 | A1 |
20150248410 | Stickler et al. | Sep 2015 | A1 |
20150248480 | Miller et al. | Sep 2015 | A1 |
20150249715 | Helvik et al. | Sep 2015 | A1 |
20150294138 | Barak | Oct 2015 | A1 |
20150363402 | Jackson et al. | Dec 2015 | A1 |
20150363407 | Huynh et al. | Dec 2015 | A1 |
20150379586 | Mooney et al. | Dec 2015 | A1 |
20150381552 | Vijay et al. | Dec 2015 | A1 |
20160034469 | Livingston et al. | Feb 2016 | A1 |
20160070764 | Helvik et al. | Mar 2016 | A1 |
20160117740 | Linden et al. | Apr 2016 | A1 |
20160203510 | Pregueiro et al. | Jul 2016 | A1 |
20170072002 | Bafundo et al. | Mar 2017 | A1 |
20170091644 | Chung et al. | Mar 2017 | A1 |
20170212931 | Chen et al. | Jul 2017 | A1 |
20190180204 | Stickler et al. | Jun 2019 | A1 |
20200358864 | Helvik et al. | Nov 2020 | A1 |
20210056472 | Stickler et al. | Feb 2021 | A1 |
20210232631 | Holm et al. | Jul 2021 | A1 |
20210263917 | Helvik et al. | Aug 2021 | A1 |
Number | Date | Country |
---|---|---|
1666279 | Sep 2005 | CN |
101398836 | Apr 2009 | CN |
102150161 | Aug 2011 | CN |
102298612 | Dec 2011 | CN |
102567326 | Jul 2012 | CN |
102693251 | Sep 2012 | CN |
102708168 | Oct 2012 | CN |
102906689 | Jan 2013 | CN |
102930035 | Feb 2013 | CN |
2409271 | Jan 2012 | EP |
2426634 | Mar 2012 | EP |
2764489 | Aug 2014 | EP |
2008097969 | Aug 2008 | WO |
2008111087 | Sep 2008 | WO |
2010029410 | Mar 2010 | WO |
2012129400 | Sep 2012 | WO |
2013026095 | Feb 2013 | WO |
2013043654 | Mar 2013 | WO |
2013123550 | Aug 2013 | WO |
2013173232 | Nov 2013 | WO |
Entry |
---|
P. Resnick, Request for Comments (RFC) 5322, Oct. 2008, Network Working Group. |
PCT International Preliminary Report on Patentability Issued in Application No. PCT/US2014/061658 , dated May 12, 2016, 7 Pages. |
PCT International Preliminary Report on Patentability Issued in Application No. PCT/US2016/012399, dated Jul. 11, 2017, 9 Pages. |
“Bing Ads targeting—training”, Published on: Mar. 31, 2013 Available at: http://advertise.bingads.microsoft.com/en-ca/cl/245/training/bing-ads-targeting. |
“Campaign Element Template Parameters—Training”, Retrieved on: Oct. 1, 2014 Available at: https://www-304.ibm.com/support/knowledgecenter/SSZLC2_7.0.0/com.ibm.commerce.management-center_customization.doc/concepts/csbcustargdef.htm. |
“Connections Enterprise Content Edition”, Published on: Nov. 22, 2013 Available at: http://www-03.ibm.com/software/products/en/connections-ecm/. |
“Enterprise Search from Microsoft”, Published on: Jan. 2007, Available at: https://www.google.co.in/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&ved=0CDMQFjAB&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2Fd%2F0%2F1%2Fd0165e6d-11cb-464b-b24a-c019d82def0d%2FEnterprise%2520Search%2520from%2520Microsoft.doc&ei=lAq9UqueHoTtrAe5yoC4Bg&usg=AFQjCNEax9yYC0KGTUhr4bNIxTJpyyyhsA&bvm=bv.58187178,d.bmk. |
“Facets for Enterprise Search Collections”, Retrieved on: Jun. 17, 2014, Available at: http://pic.dhe.ibm.com/infocenter/analytic/v3r0m0/index.jsp2topic=%2Fcom.ibm.discovery.es.ad.doc%2Filysafacets.htm. |
“Getting Started with your My Site”, Published on: Apr. 6, 2013, Available at: http://office.microsoft.com/en-in/sharepoint-server-help/getting-started-with-your-my-site-HA101665444.aspx. |
“How to Segment and Target Your Emails—Training”, Published on: Aug. 15, 2014 Available at: http://www.marketo.com/_assets/uploads/How-to-Segment-and-Target-Your-Emails.pdf?20130828153321. |
“Introducing Delve (codename Oslo) and the Office Graph”, Published on: Mar. 11, 2014, Available at: http://blogs.office.com/2014/03/11/introducing-codename-oslo-and-the-office-graph/. |
“Introduction to Managed Metadata”, Retrieved on: Jun. 23, 2014 Available at: http://office.microsoft.com/en-001/office365-sharepoint-online-enterprise-help/introduction-to-managed-metadata-HA102832521.aspx. |
“Persistent Search: Search's Next Big Battleground”, Available at: http://billburnham.blogs.com/burnhamsbeat/2006/04/persistent_sear.html, Published on: Apr. 10, 2006, 3 pages. |
“Turn search history off or on”, retrieved from http://onlinehelp.microsoft.com/en-US/bing/ff808483.aspx, Retrieved date: Dec. 12, 2013, 1 page. |
“Yammer the Enterprise Social Network”, Published on: Sep. 9, 2013 Available at: https://about.yammer.com/product/feature-list/. |
Amitay et al., “Social Search and Discovery using a Unified Approach”, In Proceedings of the 20th ACM Conference on Hypertext and Hypermedia, Jun. 29, 2009, pp. 199-208. |
Bailly, Nestor, “Finding the Best Video Content Using the Power of the Social Graph”, Published on: Jul. 17, 2013 Available at: http://iq.intel.com/iq/35820000/finding-the-best-video-content-using-the-power-of-the-social-graph. |
Bobadilla et al., “Recommender Systems Survey”, In Journal of Knowledge-Based Systems, vol. 46, Jul. 2013, pp. 109-132. |
Daly et al., “Social Lens: Personalization around user Defined Collections for Filtering Enterprise Message Streams”, In Proceedings of the Fifth International AAAI Conference on Weblogs and Social Media, Published on: Jul. 17, 2011, 8 pages. |
Diaz et al., “SIGIR 2013 Workshop on Time Aware Information Access (#TAIA2013)”, In Proceedings of the 36th International ACM SIGIR Conference on Research and Development in Information Retrieval, Aug. 1, 2013, 41 pages. |
Elbassuoni et al., “Language-Model-Based Ranking for Queries on RDF-Graphs”, In Proceedings of the 18th ACM Conference on Information and Knowledge Management, Nov. 2, 2009, 10 pages. |
Fan et al., “Tuning Before Feedback: Combining Ranking Discovery and Blind Feedback for Robust Retrieval”, Retrieved at http://filebox.vt.edu/users/wfan/paper/ARRANGER/p52-Fan.pdf, 27th Annual International ACM SIGIR Conference on Research and Development in Information Retrieval, Jul. 25, 2004, 8 pages. |
Fox, Vanessa, “Marketing in the Age of Google”, John Wiley & Sons, Mar. 8, 2012, 3 pages. |
Giugno et al., “GraphGrep: A Fast and Universal Method for Querying Graphs”, In Proceedings of the 16th International Conference on Pattern Recognition, vol. 2, Aug. 11, 2002, 4 pages. |
Gruhl et al., “The Web beyond Popularity—A Really Simple System for Web Scale RSS”, In Proceedings of the 15th International Conference on World Wide Web, May 23, 2006, pp. 183-192. |
Guy et al., “Finger on the Pulse: The Value of the Activity Stream in the Enterprise”, In Proceedings of 14th IFIP TC 13 International Conference on Human-Computer Interaction, Sep. 2, 2013, 18 pages. |
Guy et al., “Personalized Recommendation of Social Software Items Based on Social Relations”, In Proceedings of the Third ACM Conference on Recommender Systems, Oct. 2009, pp. 53-60. |
Hackett, Wes, “Extending the Activity Feed with Enterprise Content”, In Proceedings of ActivityFeed, Development, Featured, Sharepoint, Social Features, Jun. 16, 2011, 27 pages. |
Hanada, Tetsuya, “Yammer—Enterprise Graph SharePoint”, In Australian Sharepoint Conference, Jun. 11, 2013, 23 pages. |
Josh, “Send Notifications to your Customers in their Timezone—training”, Published on: Aug. 19, 2014 Available at: https://mixpanel.com/blog/2014/08/19/announcement-send-notifications-in-your-customer-s-timezone. |
Kelly et al., “The Effects of Topic Familiarity on Information Search Behavior”, Retrieved at http://www.ils.unc.edu/˜dianek/kelly-jcd102.pdf, Joint Conference on Digital Libraries, Portland, Oregon, USA, Jul. 13, 2002, 2 pages. |
Khodaei et al., “Social-Textual Search and Ranking”, In Proceedings of the First International Workshop on Crowdsourcing Web Search, Apr. 17, 2012, 6 pages. |
Kubica et al., “cGraph: A Fast Graph-Based Method for Link Analysis and Queries”, In Proceedings of the IJCAI Text-Mining & Link-Analysis Workshop, Aug. 2003, 10 pages. |
Li et al., “Personalized Feed Recommendation Service for Social Networks”, In IEEE 2nd International Conference on Social Computing, Aug. 20, 2010, 8 pages. |
Li et al., “Research of Information Recommendation System Based on Reading Behavior ”, In International Conference on Machine Learning and Cybernetics, vol. 3, Jul. 12, 2008, 6 pages. |
Liang et al., “Highlighting in Information Visualization: A Survey”, In Proceedings of 14th International Conference Information Visualisation, Jul. 26, 2010, pp. 79-85. |
Masuch, Lukas, “Hack: Enterprise Knowledge Graph—One Graph to Connect them All”, Published on: Mar. 28, 2014, Available at : http://www.managementexchange.com/hack/enterprise-knowledge-graph-one-graph-connect-them-all. |
Pecovnik, Simon, “Enterprise Graph Search—take 1”, Published on: Jan. 28, 2014, Available at: http://www.ravn.co.uk/2014/01/28/enterprise-graph-search/. |
Perer et al., “Visual Social Network Analytics for Relationship Discovery in the Enterprise”, In IEEE Conference on Visual Analytics Science and Technology, Published on: Oct. 23, 2011, 9 pages. |
Ronen et al., “Social Networks and Discovery in the Enterprise (SaND)”, In Proceedings of the 32nd International ACM SIGIR Conference on Research and Development in Information Retrieval, Jul. 19, 2009, 1 page. |
Roth et al., “Suggesting Friends Using the Implicit Social Graph”, In Proceedings of the 16th ACM SIGKDD International Conference on Knowledge Discovery and Data Mining, Jul. 25, 2010, 9 pages. |
Soussi, Rania, “Querying and Extracting Heterogeneous Graphs from Structured Data and Unstrutured Content”, In Doctoral Dissertation, Ecole Centrale Paris, Jun. 22, 2012, 208 pages (1 page Abstract). |
Ubbesen, Christian, “Enterprise Graph Search”, Published on: Jan. 28, 2013, Available at: http://www.findwise.com/blog/enterprise-graph-search/. |
Yeung, Ken, “Yammer Unveils the Open Graph for the Enterprise, to Help make Business Apps More Social”, Published on: Oct. 29, 2012, Available at: http://thenextweb.com/insider/2012/10/29/yammer-using-the-enterprise-graph/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+TheNextWeb+(The+Next+Web+All+Stories). |
Zhibao et al., “EISI: An Extensible Security Enterprise Search System”, In 2nd International Conference on Computer Science and Network Technology, Dec. 29, 2012, pp. 896-900. |
Fazio, Stephanie, “How Social is Enterprise Search?”, Published on: Mar. 14, 2012, Available at: http://blogs.opentext.com/vca/blog/1.11.647/article/1.26.2007/2012/3/14/How_Social_is_Enterprise_Search%3F. |
Muralidharan, et al., “Social Annotations in Web Search”, In Proceedings of the ACM Annual Conference on Human Factors in Computing Systems, May 5, 2012, 10 pages. |
Yap, Jamie, “Graph Search Capabilities Offer Enterprise Benefits”, Published on: Feb. 14, 2013, Available at: http://www.zdnet.com/graph-search-capabilities-offer-enterprise-benefits-7000011304/. |
U.S. Appl. No. 13/802,734, Solheim, et al., “Visualizing Ranking Factors for Items in a Search Result List”, filed Mar. 14, 2013. |
Yong Yin at al., An improved Search Strategy for Even Degree Distribution Networks, Jul. 2013, Academy Publisher, vol. 8, No. 7, pp. 1558-1565 (Year: 2013). |
Jason J. Jung, Understanding information propagation on online social tagging systems, Nov. 4, 2012, Springer Science+ Business Media, Edition or vol. 48, pp. 745-754 (Year: 2012). |
Barbie E. Keiser, Semisocial information Discovery, Novi Dec. 2013, Online searcher, pp. 16-22 (Year: 2013). |
Anthony Stefanidis et al., Harvesting ambient geospatial information from social media feeds, Dec. 4, 2011, GeoJournal, Edition or vol. 78, pp. 319-338 (Year: 2011). |
Chinese Office Action in Application 2014800588740 dated Dec. 5, 2018, 14pgs. |
“International Search Report & Written Opinion Issued in PCT Patent Application No. PCT/US2014/061658”, dated Jan. 9, 2015, 8 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 14/192,235”, dated Dec. 26, 2018, 16 Pages. |
“Final Office Action Issued in U.S. Appl. No. 14/593,650”, dated Jan. 4, 2019, 35 Pages. |
“8 Things Marketers Ought to Know About Facebooks New Trending Feature”, Retrieved from: https://web.archive.org/save/https://www.facebook.com/notes/brandlogist/8-things-marketers-ought-to-know-about-facebooks-new-trending-feature/650859898308191/, Jan. 30, 2014, 5 Pages. |
“Trending—Definition and Synonyms”, Retrieved from: https://web.archive.org/web/20170618063522/http://www.macmillandictionary.com:80/us/dictionary/american/trending, Jul. 18, 2014, 1 Page. |
Dayal, Priyanka, “How Many Tweets Make a Trend?”, Retrieved from https://www.vuelio.com/uk/blog/how-many-tweets-make-a-trend/, Aug. 28, 2013, 5 Pages. |
“Final Office Action Issued in U.S. Appl. No. 14/194,700”, dated May 20, 2019, 25 Pages. |
“Notice of Allowance Issued in U.S. Appl. No. 14/195,243”, dated May 1, 2019, 10 Pages. |
“Final Office Action Issued in U.S. Appl. No. 14/296,747”, dated May 1, 2019, 30 Pages. |
Bakhshandeh, et al., “Personalized Search Based on Micro-Blogging Social Networks”, In Proceedings of the CSI International Symposium on Artificial Intelligence and Signal Processing, May 2, 2012, 4 Pages. |
Mishra, et al., “Improving Mobile Search through Location Based Context and Personalization”, In Proceedings of the International Conference on Communication Systems and Network Technologies, May 11, 2012, 5 Pages. |
“Office Action Issued in European Patent Application No. 15771764.6”, dated May 13, 2019, 9 Pages. |
“Final Office Action Issued in U.S. Appl. No. 14/192,235”, dated Jul. 25, 2019, 14 Pages. |
“Second Office Action Issued in Chinese Patent Application No. 201580011895.1”, dated Aug. 9, 2019, 6 Pages. |
“Final Office Action Issued in U.S. Appl. No. 15/833,453”, dated May 4, 2020, 30 Pages. |
“Office Action Issued in Mexican Patent Application No. MX/a/2017/002699”, dated Feb. 14, 2020, 7 Pages. |
“Office Action Issued in Chinese Patent Application No. 201580047507.5”, dated Apr. 3, 2020, 13 Pages. |
“Final Office Action Issued in U.S. Appl. No. 14/296,747”, dated Sep. 3, 2020, 31 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 15/833,453”, dated Sep. 11, 2020, 36 Pages. |
Pradel, et al., “Natural Language Query Interpretation into SPARQL using Patterns”, Retrieved From: https://hal.archives-ouvertes.fr/hal-01143219/document, Oct. 22, 2013, 14 Pages. |
Brinkley, et al., “A Query Integrator and Manager for the Query Web”, In Journal of Biomedical Informatics, vol. 15, Issue 5, Oct. 1, 2012, pp. 975-991. |
“Non Final Office Action Issued in U.S. Appl. No. 16/057,229”, dated Jun. 9, 2020, 8 Pages. |
“First Examination Report Issued in Indian Patent Application No. 201647027554”, dated Sep. 14, 2020, 6 Pages. |
“Second Office Action Issued in Chinese Patent Application No. 201580010703.5”, dated Oct. 24, 2019, 5 Pages. |
“Office Action Issued in Chinese Patent Application No. 201580047507.5”, dated Sep. 28, 2020, 14 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 14/194,700”, dated Nov. 5, 2019, 27 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 15/833,453”, dated Dec. 17, 2019, 42 Pages. |
“Notice of Allowance Issued in U.S. Appl. No. 14/194,700”, dated Apr. 15, 2020, 9 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 14/192,235”, dated Apr. 17, 2020, 16 Pages. |
“First Office Action and Search Report Issued in Chinese Patent Application No. 201580011895.1”, dated Mar. 5, 2019, 18 Pages. |
“Office Action Issued in European Patent Application No. 15710632.9”, dated Feb. 18, 2019, 07 Pages. |
“First Office Action and Search Report Issued in Chinese Patent Application No. 201580010703.5”, dated Mar. 8, 2019, 12 Pages. |
“Second Office Action and Search Report Issued in Chinese Patent Application No. 201480058874.0”, dated Jun. 26, 2019, 14 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 16/275,386”, dated Aug. 29, 2019, 36 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 14/296,747”, dated Jan. 30, 2020, 32 Pages. |
“Notice of Allowance Issued in U.S. Appl. No. 16/275,386”, dated Mar. 6, 2020, 10 Pages. |
Oyama, et al., “Analysis of Topics and Relevant Documents for Navigational Retrieval on the Web”, In Proceedings of International Workshop on Challenges in Web Information Retrieval and Integration, Apr. 8, 2005, 6 Pages. |
Chen, et al., “Towards Topic Trend Prediction on a Topic Evolution Model with Social Connection”, In Proceedings of ACM International Conferences on Web Intelligence and Intelligent Agent Technology, Dec. 4, 2012, 5 Pages. |
“Final Office Action Issued in U.S. Appl. No. 14/192,235”, dated Nov. 18, 2020, 17 Pages. |
“Non Final Office Action Issued in U.S. Appl. No. 14/296,747”, dated Jan. 4, 2021, 30 Pages. |
“Office Action Issued in Chinese Patent Application No. 201580047507 5,” dated Jan. 11, 2021, 11 Pages. |
“Notice of Allowance Issued in U.S. Appl. No. 16/895,056”, dated Aug. 5, 2021, 11 Pages. |
Aiello, et al., “Sensing Trending Topics in Twitter”, In Journal of IEEE Transactions on Multimedia, vol. 15, Issue 6, Oct. 1, 2013, pp. 1268-1282. |
Kim, et al., “Evolution of Social Networks Based on Tagging Practices”, In Journal of IEEE Computer Society, vol. 6, Issue 2, Apr. 1, 2013, pp. 252-261. |
“Non Final Office Action Issued in U.S. Appl. No. 14/192,235”, dated Aug. 20, 2021, 17 Pages. |
“Final Office Action Issued in U.S. Appl. No. 14/296,747”, dated Sep. 10, 2021, 31 Pages. |
Pang, et al., “Association-Based Recommendation of Web Information”, In Proceedings of International Conference on Systems, Man and Cybernetics, vol. 7, Oct. 6, 2002, 5 Pages. |
Tran, et al., “User Interest Analysis with Hidden Topic in News Recommendation System”, In Proceedings of International Conference on Asian Language Processing, Dec. 28, 2010, 4 Pages. |
“Notice of Allowance Issued in U.S. Appl. No. 16/895,056”, dated Sep. 20, 2021, 11 Pages. |
Number | Date | Country | |
---|---|---|---|
20150120700 A1 | Apr 2015 | US |