Systems and methods for using lexically-related query elements within a dynamic object for semantic search refinement and navigationDownload PDF
- Publication number
- Grant status
- Patent type
- Prior art keywords
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- G06F17/3066—Query translation
- G06F17/30657—Query processing
- G06F17/3061—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F17/30—Information retrieval; Database structures therefor; File system structures therefor
- G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
- G06F—ELECTRICAL DIGITAL DATA PROCESSING
- G06—COMPUTING; CALCULATING; COUNTING
- G06F17/30672—Query expansion
- This patent application is a continuation application of prior U.S. patent application Ser. No. 11/279,327, filed on Apr. 11, 2006, entitled “SYSTEMS AND METHOD FOR USING LEXICALLY-RELATED QUERY ELEMENTS WITHIN A DYNAMIC OBJECT FOR SEMANTIC SEARCH REFINEMENT AND NAVIGATION,” which claims the benefit of U.S. Provisional Patent Application No. 60/678,963, entitled “SYSTEM AND METHOD FOR USING LEXICALLY-RELATED QUERY ELEMENTS WITHIN A DYNAMIC OBJECT FOR SEMANTIC SEARCH REFINEMENT AND NAVIGATION,” filed on May 9, 2005. For purposes of disclosure, the foregoing applications are incorporated herein by reference in their entireties.
- 1. Technology Field
- The present invention relates generally to computer based search and navigation. More specifically, embodiments of the present invention relate to the use of lexically-related strings, sub-strings, and/or search elements within one or more dynamically-created list objects that can be used for generating a search query or for navigation.
- 2. Related Technology
- Information systems, including the Internet, intranets, databases, lexicons, and any collection of documents or electronic information, are growing at an explosive rate. As the size and corresponding amount of information and content of these systems grow, new search techniques and methodologies are needed to efficiently and conveniently access and navigate that information.
- Currently, more efficient methods of searching usually require some form of indexing of the content stored within these systems. For example, there are established and conventional techniques for indexing information systems, such as PageRank™ used by the Google™ search engine for the Internet, or relevance or other computational linguistic methodologies for locating search results within an information system. Searching the Internet is particularly problematic. The Internet is a complex and unstructured database that is constantly growing and from which terabytes of information can be retrieved. However, traversing and navigating the Internet is becoming increasingly difficult and time consuming as its explosive growth continues, and locating relevant information on the Internet can be difficult and frustrating. Hence, for both the Internet as well as other content systems, there is a general and ongoing need to improve the quality of information that is returned in response to a user query.
- Searchers are often frustrated by the sheer volume and lack of relevance of search results that result from many existing search engines and methodologies. Moreover, improved processing speeds often are not the solution. For example, the improved speed of systems such as Google's might appear to save the searcher's time, but often the exact opposite is true due to the huge volume of (often irrelevant) search results that are returned. Irrelevant and inaccurate search results is an increasing problem due in part to the ever-expanding size of the body of content being indexed; in essence immediate relevance is inversely related to breadth or size of the body of content being searched.
- Existing search methodologies are lacking in other respects as well. As is known, the quality of results returned often is dictated by the quality of the search terms used in the search query. However, the articulation of an appropriate search term is often difficult. This problem typically stems from the searcher not knowing the “vocabulary” or “lexicon” of the information system/database into which they are entering their query string. What is the best or even approximate query to use? Often the user conducts the search on an iterative basis by adding to or changing their query string many times, in a “hit or miss” fashion, before arriving at the appropriate search query. The process can be time consuming and frustrating.
- In a common search setting, a user might use a conventional search engine from search services available on the Internet at Google.com, Yahoo.com, OpenText.com, UltraSeek.com, Clusty.com, and the like, or a search methodology used on Internet sites such as PCConnection.com, LLBean.com, Corbis.com, Wikipedia.org. In environments such as these, a user looking for specific information typically submits a query (i.e., a Boolean logic construct of words) to the search engine/method. In response, the search tool uses the query to search for the desired information, and then returns a “hit” list containing zero or more search results that satisfy the query.
- Typically, this type of search returns a large set of “hits” or results; a scenario that is increasingly common due to the growth of the Internet and related networks and databases. In addition to the large number of results that are returned, the manner in which the search results are presented to the user is often not helpful. A list of search results returned by a conventional search method is often sorted in accordance with some form of computational linguistic calculation. For example, the order of the listing may be based on a calculated relevance. In one example, relevance may be based on how many times the word(s) in the user's query are found in each result. Unfortunately, this presentation approach may not prioritize the result presentation in the most appropriate manner and, in any event, does little to address the problems presented when a large number of search results are returned. As a result, the user is required to spend more and more time sifting through the results of a search in order to find the information that is actually of interest.
- In view of the foregoing problems and shortcomings, there is a need to provide a user with a better opportunity to construct an appropriate search query in the first instance. In this way, the user would be provided with a more relevant and manageable list of search results. Preferably, a solution would entail the use of semantic search tools that take advantage of the user's own knowledge of the content being searched, and that would also provide semantically- and lexically-related alternatives to the string or prompt being entered or provided by the user. The user would then be in the position of selecting the most appropriate search criteria. This type of assistance would preferably be provided dynamically or in “real time” as the user is constructing a search, thereby increasing the speed and efficiency of the search process. The use of more appropriate search criteria would result in more appropriate more relevant and more manageable search results, thereby alleviating many of the drawbacks present in currently available search systems.
- In view of these and other needs and drawbacks, it is one purpose of the present invention to provide a system and method for assisting a user with the identification of appropriate search criteria that can be used to search or otherwise navigate the content of a particular information system. For example, in one disclosed embodiment, the user is provided with a dynamic search environment that provides search suggestions or alternatives. Preferably, those suggestions or alternatives relate to the specific lexicon of the particular information system that is being searched. This assistance to the user allows for dynamic refinement of the user's query string for the purpose of composing and selecting a more highly-relevant search query.
- In an example embodiment, a system is configured with a search query receiver (for example a search box), a query controller, a controlled-vocabulary database, a search query element viewer, and an administration module for importing, configuring, and maintaining the controlled vocabulary.
- In an example system, a user, seeking to search or otherwise navigate the content of a particular information system (such as an Internet site or other LAN/WAN-based information system), enters an initial query element into the search query receiver. The search query receiver can be implemented within a client browser on a client device, such as a desktop or portable computer. The initial query element can be submitted via a keyboard text entry, a voice prompt, or any other suitable entry method. As the search query is entered, the search query receiver can (either on a word-by-word or character-by-character basis) create an “incremental” query which is passed via a network (LAN, WAN, Internet, intranet, etc.) to the query controller. The query controller interrogates the controlled-vocabulary database to find “matches” to the initial query entered thus far. From matches found in the controlled-vocabulary database, the query controller returns, via the network to the search query element viewer, semantically and lexically-related elements that relate to the user's initially entered search criteria, and to the information system/database that is being searched.
- In an illustrated embodiment, the lexically-related alternative elements are presented to the user via the search query element viewer, preferably implemented as a dynamic semantic list object. In preferred embodiments, this lexically-related content is delivered into the query element viewer immediately (i.e., in substantially real-time) in response to an action by the user. While other approaches might be used, in preferred embodiments this functionality is implemented by way of a client-side object that is implemented as a dynamically-generated screen or device object such as a drop-down menu, iFrame, or browser window. The search query element viewer thus provides a real-time “view” into the specific lexicon of the information system that is being searched.
- In illustrated embodiments, the dynamically created lexically-related alternative element(s) is obtained by the query controller logic from the controlled vocabulary database. The controlled vocabulary database can be administered and maintained as a database that is separate and discrete from the information system that is actually being searched/navigated.
- Upon presentation of the dynamically created search query element viewer, the user can then choose to interact with the lexically-related alternative elements within the search query element viewer. For example, the user might select, add to, or change a lexically-related element that best matches their intended search or navigation requirements. In alternate embodiments, the user may iterate the above process numerous times to find the best search query. Hence, in one application a user might select one or more alternatives in the search query element viewer and from this selection perform a direct search of the information system of interest (e.g., use the selected value as a search term in a conventional search engine search). Alternatively, the user might select one of the alternatives in the search query element viewer, and load that value in the search query receiver for identification of additional possible alternatives before settling on a particular search/navigation query element. The dynamic and iterative nature of the search query element viewer greatly enhances a user's ability to identify the most appropriate query element for use in connection with a particular information system.
- It will be appreciated that while example embodiments have been summarized as including a single search query receiver for a given application, the invention should not be so limited. Depending on the needs of a particular application, a search environment may include two or more search query receivers, each of which may connect or interact with one or more query controllers which are in turn interfaced with one or more controlled vocabulary databases. Each search query receiver may be associated with a search query element viewer. Alternatively, a search query receiver might be selectively associated with multiple lexicons of different controlled vocabulary databases. Depending on an option, for example selected by a user, when a user enters an initial query, the search query element viewer displays alternatives from a particular lexicon.
- Another embodiment provides a method and system for the user to set display attributes such as user preferences, colors, formats, and symbols for displaying and arranging the lexical elements within the search query element viewer.
- One advantage of disclosed embodiments results from the ability of the system to help the user with disambiguation of query/navigation terms prior to the user performing any one of a series of selective or navigational actions. Such actions include, but are not limited to, submission of the query for the purpose of a search, selecting from pull-down menus or any other selective screen object such as screen menus, buttons, lists, navigational aide, or any process associated with interrogation of or inquiry by an information system, its content, or any of its navigation aides.
- Another advantage of disclosed embodiments is the ability for the user to know immediately if a search query is within the scope and content of the information system they are searching. This provides a method for both “heads-up” lexicon content confirmation and focus. For example, conventional search methods are natural-language based, meaning that if you search for (enter a query for) “hard drive” and the information system's lexicon contains only the term “disk drive,” then no search results will be returned. In contrast, illustrated embodiments will return lexical alternatives listed in the search query element viewer. Thus, in one example embodiment, as the user enters “hard dr” on a type-ahead basis en route to entering “hard drive,” they might see “disk drive” listed as an alternative in the search query element viewer in addition to or instead of the term “hard drive.” In disclosed embodiments, the user will be able to select any of the alternatives displayed in the search query element viewer for the purpose of initiating a search or continuing to refine the search query or navigation.
- A related advantage is provided by the ability to view or learn of alternate search query strings or elements within the information system lexicon that relate to the user's original query.
- Yet another advantage is realized due to the speed by which the user has to consider alternative query strings. By offering a heads-up form of “what you see is what is there,” a user can more rapidly determine the query that is best for the information system lexicon with which they are engaged. For example, presently preferred embodiments might be used in connection with a commercial website, such as PCConnection.com. In that type of application environment, a user might enter “giga” into the search query receiver and then interact in the search query element viewer with lexical alternatives such as “hard drive, disk drive, gigabyte drive, Seagate 250 GB,” which might all be terms/phrases that are contained in the controlled-vocabulary database associated with the PCConnection.com information system lexicon of part numbers or product names.
- The foregoing, together with other features and advantages of the present invention, will become more apparent when referred to the following specification, claims and accompanying drawings.
- To further clarify various aspects of exemplary embodiments of the present invention, a more particular description of the invention will be rendered by reference to specific exemplary embodiments thereof which are illustrated in the appended drawings. It is appreciated that these drawings depict only exemplary embodiments of the invention and are therefore not to be considered limiting of its scope. The drawings are not drawn to scale. The invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
FIG. 1is a block diagram of an overall architecture of one presently preferred embodiment of the present invention;
FIG. 2a is a flowchart illustrating one example method of the present invention;
FIG. 2b is a flowchart illustrating an example of the user's interaction with an example embodiment of the present invention;
FIG. 3is a flowchart illustrating one example of how a “controlled vocabulary” is implemented and maintained;
FIG. 4is an example screen display of a search query receiver [SQR];
FIG. 5is an example screen display of use of the search query receiver;
FIG. 6is an example screen display of use of the search query element viewer with matched elements;
FIG. 7is an example screen display of use of the search query element viewer with semantically- and lexically-matched elements;
FIG. 8is an example screen display of use of the search query element viewer with semantically- and lexically-matched elements with sample qualifiers;
FIG. 9a is an example screen display of use of the search query element viewer with semantically- and lexically-matched elements with sample depth (sub-string) indicators;
FIG. 9b is an example screen display of use of a secondary layer over the search query element viewer with semantically- and lexically-matched elements;
FIG. 10is an example screen display of use of the search query receiver and the search query element viewer with semantically- and lexically-elements matched to the depth (sub-string) indicators;
FIG. 11is an example screen display of use of the search query receiver and the search query element viewer with additional semantically- and lexically-elements matched to the depth (sub-string) indicators;
FIG. 12a illustrates one example of sample text-based search results from an information system; and
FIG. 12b illustrates one example of sample image-based search results from an information system.
- Reference will now be made to the drawings to describe presently preferred embodiments of the invention. It is to be understood that the drawings are diagrammatic and schematic representations of example embodiments, and are not limiting of the present invention, nor are they necessarily drawn to scale.
- In general, embodiments of the present invention relate to computer-based systems and methods for improving a user's ability to search, or otherwise navigate content within an information system, such as might be accessible via a networked environment such as the Internet. In particular, disclosed embodiments provide the ability to pre-suppose or harness lexically-related terms that already exist in the information system and that can be viewed dynamically (in substantially “real-time”) by the user to help the user better articulate and select the most meaningful search or navigational query. Such techniques provide the user with a method and system for dynamically refining and navigating between alternative search query elements. Advantageously, this provides the user with better and more manageable search results and allows the user to gain access to the information that is actually being sought.
- Reference is first made to
FIG. 1, which illustrates one example of an overall system, generally designated at 5, for generating, displaying and using lexically and/or semantically-related query elements within a dynamic object for the purpose of semantic search refinement and navigation. In the illustrated embodiment, the system 5 is implemented to provide a dynamically-generated object containing lexically-related content by way of a “search and navigation palette,” denoted at 10. In this way, the user can more easily and effectively refine or perform a sub-search before conducting an actual search of an information system and retrieving (potentially irrelevant) search results, such as might be accomplished by a conventional search engine such as Google™.
- In the embodiment of
FIG. 1the “search and navigation palette” (also referred to as a “search palette”) is denoted at 10. In example embodiments, the search palette 10 is provided by way of a user's (client) device/computer browser (or similar environment) upon the user loading or visiting an “information system” of interest, denoted at 20, such as a HTML, RSS, DHMTL or other type of page or document specific to the information system 20 being searched or otherwise navigated. As is shown, the client-side device is operatively connected with the desired information system 20 via any appropriate communication scheme, such as the Internet, an intranet or any suitable LAN/WAN-type network, including wire-based and/or wireless-based communication schemes.
- Also included within the example system of
FIG. 1is a server-side computing device, such as is denoted at 30, which could be implemented as any computer-based programmable device. The server 30 is operatively connected with the client side-device by way of, for example the Internet or any other appropriate network interface. Included with the server 30 is a query controller function, denoted at 200, and a controlled-vocabulary database, denoted at 300. Optionally, preferred embodiments can include an administration module, denoted at 700, for importing, configuring, and maintaining the contents of the controlled vocabulary database 700.
- As is represented in the example of
FIG. 1, the “search and navigation palette” 10 includes a client-side search query receiver function 100 and a dynamically-generated search query element viewer 500. As will be described in further detail, the dynamically-generated search query element viewer 500 functions to provide an interactive “view” into the specific lexicon of the information system 20 that is being searched/navigated (for example, a website on the Internet). In particular, the viewer 500 can be used to provide a dynamic refinement of the user's query element, such as a text string, initially entered at the search query receiver 100, resulting in better composition and selection of a more relevant search query for use in connection with the information system of interest.
- With continued reference to
FIG. 1, in a typical application a user enters an initial query element into the search query receiver 100. Entry of the initial query element can be accomplished by any appropriate means, depending on, for example, the needs of the application involved and the information system being searched and/or otherwise navigated. For example, entry could occur by means of typing on a keyboard, using a stylus, using a voice prompt or video input, or through use of any alternate method of input. In a typical application, the initial query element might be a text search string entered into the search query receiver 100 (which can be implemented, for example, as a conventional search box or browser text object) by way of a keyboard. One implementation example of a search query receiver 100 and a portion of an initial query element 110 is shown in FIG. 5.
- With continued reference to the system of
FIG. 1, as the user enters the initial search query, the query controller 200 running on, for example, the server 30 (or alternatively as a software application or client-side application) interrogates the controlled vocabulary database, designated at 300, to find “matches” (functionally denoted at 400 in FIG. 1) to the “incremental” user input initial query element (such as is shown at 110 in FIG. 5) entered thus far. In the illustrated embodiment, these “matches” are semantic and/or lexically-related alternatives to the initial query element string or prompt entered or initially provided by the user. As is shown in FIG. 1, the semantically and lexically-related alternatives are “dynamically” retrieved from the controlled vocabulary database 300 by way of the query controller 200. Moreover, the query controller 200 passes, via network 20, the alternatives to client environment 10, and the semantically and lexically-related alternative query elements are displayed dynamically and in substantially real-time by way of the search query element viewer 500. Preferably, the alternative query elements are displayed in real time as the user enters the initial query element. Hence, the displayed alternatives are updated and refined as the user continues to enter or add to the initial query element. One example of this functionality is represented in the example search and navigation palette 10 shown in the example of FIG. 6, which denotes an example search query element viewer at 500, along with dynamically generated alternative query elements denoted at 508.
- As noted, lexically-related query elements are identified, retrieved and displayed via the search query element viewer 500 “dynamically.” As used herein, the term “dynamic” or “dynamically” means substantially real-time, such that retrieval and display of the alternative query elements is substantially instantaneous in response to an action by the user. In preferred embodiments, this dynamic presentation is provided by way of a search query element viewer that is implemented as a dynamically-generated object that can be implemented with any appropriate dynamically-generated screen or device object, function or method. In one presently preferred embodiment, the dynamically-generated object is provided by way of a client-side iFrame object or a drop-down menu object. The dynamic objects, such as might be provided with an iFrame object, can also include any variety of screen or device objects such as drop-down menus and text areas.
- Once displayed via the search query element viewer 500, the user can select any of the alternative query elements to further refine the initial query by resubmitting the selection to the search query receiver and identifying lexical alternatives to that submitted query. Alternatively, the user may select one of the alternatives and submit that as a search term for use in searching the information system of interest.
- The semantically and lexically-related elements (such as those denoted at 508 in
FIG. 6) dynamically displayed via the search query element viewer 500 preferably semantically and/or lexically relate both to the user's initially entered search criteria, and to the information system that is being searched or otherwise navigated. Alternatives can consist of full or partial words or symbols that represent or otherwise relate to the lexicon of the information system being searched, and to the query element entered in the search query receiver 100. The relation of alternate lexical elements can be based on a pre-defined, controlled or structured vocabulary stored within the controlled vocabulary database, which is designated at 300 in FIG. 1. As will be described further below, any one of a number of different relationships can be defined depending on the needs of a particular application. In general however, the term “lexically-related” includes any items such as words, concepts, objects, entities, etc. that are part of and reside in the controlled vocabulary database and that are “connected” by virtue of some relation, be it linguistically (e.g., broader/narrower), functionally associated (e.g., “door” is associated with “house”), financially (e.g., price, discount, time limit), visually (e.g., photo examples of a product), alternatives or options, etc., with the lexicon of the information system of interest. In addition, in alternate embodiments, the nature of the relationship between the search query element entered in the search query receiver and the lexically related alternatives retrieved from the database and displayed in the search query element viewer might be specified by way of wildcard operators included within the specified search query element. For example, a predetermined connector (such as a ‘+’ character) could be used to indicate that non-contiguous words are extracted from the controlled vocabulary database (e.g., if the user enters “learn+alc” a result of “Learned behavior is . . . of alcohol abuse” might be returned). Similar types of “relational” operators and techniques could be used.
- By way of example and not limitation, lexically-related alternatives can include corresponding broader terms, narrower terms, associative terms or synonyms, homograms, associatively-related terms, tags, sub-strings, symbols, portions of titles or captions, content of knowledge bases or meta-words and/or other controlled vocabulary pre-defined or pre-structured informational elements contained within the controlled vocabulary database. Lexically-related alternatives can include complete sentences or portions of sentences. Symbols can be graphical representations such as icons, or can be conceptual, or linguistic such as Chinese script and characters. Lexically-related elements could also include translation equivalents for other languages such as Chinese or German. Depending on the application, lexical alternatives could be prices, special offers, and the like, or could be in the form of non-visual alternatives such as might be provided by way of voice prompts provided via a mobile device.
- The relation of alternate lexical elements can be based on a pre-defined, controlled or structured vocabulary stored within the controlled vocabulary database 300. One example might be a thesaurus-derived vocabulary, which includes synonyms of words/phrases in the information system to be searched. That vocabulary may be developed manually or as computer-generated and extracted keywords, concepts, or phrases. Such computer-generated content may be the result of clustering, extraction, or similar summarization techniques wherein vocabulary elements may be related by virtue of parent/child (broader/narrower), synonym (associative), tags, definitions, labels, categories or similar such semantically related associations.
- Creation of a controlled vocabulary database 300 in accordance with the above objectives would occur for any given “information system” of interest. For example, a database might be constructed for a particular commercial website (e.g. www-pcconnection.com), government website (e.g. www-uspto.gov), or an information system located on a corporate intranet. The controlled vocabulary database would likely be updated on a regular basis, especially if the content of the corresponding information system changes or otherwise evolves.
- Continued reference is made to
- As the query controller 200 receives the user input, the controlled vocabulary database 300 is dynamically “interrogated” so as to identify any lexically-related alternatives to the initial query thus far entered by the user, as is denoted at process step 117. In this particular example the interrogation is in the form of an index lookup using any of numerous conventional methods for indexed search against a database. For matches found in the controlled-vocabulary database 300, the query controller 200 returns to the search query element viewer 500 (for example, via the server 30 and the network 20) lexically-related alternative elements and displays them to the user. This is represented at process steps 119 and 121. Again, this interrogation of the database 300 and presentation of lexical alternatives occurs dynamically—in substantially real time as the user is entering an initial query element. An example of this dynamic presentation is shown in
FIGS. 6 and 7, showing example lexically-related elements at 508 and 512. As previously noted, in different embodiments, the lexically-related elements can be broader, associative, tags, terms, strings, sub-strings, symbols, voice prompts and the like, depending on the particular application and configuration of the controlled-vocabulary database. Also, as is represented in the embodiment of FIGS. 7 and 8lexically-related elements such as 508 and 512 ( FIG. 7) and any associated symbols or navigational aides such as is denoted at 516, 520 ( FIG. 8) are passed to the search query element viewer 500, such as data that already contains display markup coding from the query controller 20 such as HTML, or such as AJAX-based raw data that is interpreted and displayed by the client. In one embodiment the alternate lexical elements, for example “ketchup” and “mustard” 590 as shown in FIG. 9a can be separated or delimited by commas, a graphical separator, or other meaningful cue to denote separation between alternate groupings of lexical elements.
- As is denoted at process step 125, the user can dynamically interact with the search query element viewer 500. For example, the user can “select” which of the displayed lexically-related elements best matches the user's search or query intent. At process step 125, the user can click on an alternate lexical element (such as 508 or 512 in
FIG. 7), and the selected element is submitted as the search query to the information system (represented at step 127), resulting in a return of corresponding search results (one example of which is shown in FIGS. 12a and 12 b).
- Alternatively, by using the lexical elements, symbols, and navigation aides associated with the initial search query and the alternatives provided within the search query element viewer 500, the user may iterate this process, such as is represented at process steps 123 and 125 in
FIG. 2a, numerous times to find the best alternative element within the alternative elements shown in the search query element viewer 500. When the user has found the desired query element, they can either click directly on the lexically-related alternative element (for example 508, 512 in FIGS. 6 and 7) or they can click on a Search button 610 as shown in FIG. 5or any input means to submit the then current search query (e.g., “condominium” in FIG. 12b) to the information system which returns search results 620 as shown in FIG. 12a in the conventional formats such as the title, URL and description, or as images such as shown in FIG. 12b or in any other format appropriate to the content of the information system such as video or audio.
- A number of variations and alternatives can be provided in connection with the general process of
FIG. 2a. For example, FIG. 9b demonstrates how a user might pass a selection device, such as a mouse or stylus, “over” the desired alternative lexical element, for example over 535, 550, or 590, and a secondary layer such as a pop-up, window, or other device object 595 (that may be temporarily displayed or is always displayed) on top of or within the search query element viewer 500 with additional alternative elements or clarifying data such as element type, date, category, or class wherein the user can select from this secondary layer to invoke actions similar to what otherwise could be achieved by selecting elements 508 or 512 (e.g., FIG. 7).
- In another embodiment, alternative lexical elements displayed in the search query element viewer 500 may be displayed with associated toggles, icons or other graphical representations through which the user can directly invoke preferences such as logical switches, display options, etc.
- In another embodiment, any one of an array of numbers or symbols (such as 516 and 520 shown in
FIG. 8) returned to the search query element viewer conveys to the user, before the user submits their search query, the “depth” or number of potential search results that will be returned by submitting that lexical element as the query to the information system. In this embodiment the indication of “pre-results” (for example a count of potential search results or hits, or an indication of the number of other lexically-related elements related to the user input 110 or are contained 530, FIG. 9a, within the user input 110) to the user helps the user decide if they need to “drill down” more or if the associated lexical element is the one they want to submit as their search query.
- In another embodiment, the user clicks on or selects any one of an array of numbers or symbols (e.g., 516 and 520 in
FIG. 8) associated with a lexical element which functionally causes the lexical element associated with the selected number to be loaded into the search query receiver 100 and that lexical element automatically submitted to the query controller as a new query string/sub-string resulting in a new display of alternative lexical elements related to this new query in the search query element viewer 500. Of course, the interaction with, or selection of an alternative lexical element can be by way of the search query element viewer 500 exclusively, i.e., resubmission via the search query receiver 100 is not necessary depending on the particular implementation.
- In another embodiment, as an alternate form of lexical relationship, when the query controller 200 interrogates the controlled vocabulary database 300, the query controller finds and counts all the strings and expressions within the controlled vocabulary database 300 that “contain” the lexical element 508. This count may alternatively be returned as part of the associated symbols or navigational aides 530, such as are shown in the example of
FIG. 9a and passed to the search query element viewer 500. For example, if the lexical element 508 is “George Bush,” the value returned (530 in FIG. 9a) will be an “instance counter” of all the instances within the controlled vocabulary that contain the string “George Bush,” such as “The President George Bush” and “She is the wife of George Bush.”
- The interrogation by the query controller 200 of the controlled vocabulary database 300 may be based alternatively on any of several Boolean or other linguistic comparison methods (which can be selected by the information system Administrator as globally applicable, or can be selected by the user under Preferences as is represented in the example “administration” process of
FIG. 3). Boolean or other linguistic comparison methods can include “exact” string matches so that only lexical elements containing just the exact string “George Bush” are returned, or an “approximate matches” “fuzzy-logic contains near” matching that returns lexical elements that contain the words George AND Bush such as “He stood behind the bush with George,” or so that lexical elements containing any of the words George OR Bush are returned 544 (or as shown in FIG. 10. any related lexical elements or strings containing the words “Prince of Conde” or rotated versions thereof). In this example the lexical element 535 can be passed by the client browser 10 or server 30 to the search query receiver 100 and then become the new query string 540 in the search query receiver as shown in FIG. 10.
- In one embodiment the user may set preferences to select what type of alternative lexical elements are displayed in the search query element viewer 500 (for example related terms, such as 512 in
FIG. 7or 550 in FIG. 11) or how the lexical content is displayed (for example, color preferences, symbol preferences instead of numbers 520 in FIG. 8or 548 as shown in FIG. 11).
- In another embodiment the lexically-related content from the controlled vocabulary database that is displayed in the search query element viewer might consist of translated equivalents of what the user has entered. Thus in one example, if the user selects “English” from a switch object such as a checkbox or drop-down menu or from their preferences, as they enter “netw” in the search query receiver, the search query element viewer could be implemented to display multiple columns, the first of which displays all matching English-based words containing “netw . . . ” and additional columns, each for a different language such as German or Chinese, and in each of these respective columns the search query element viewer will display a row of the translated equivalents of the English word(s) appearing in the first column of the row.
- It will be appreciated that the column/row format for displaying multiple relationships/groupings, be they between languages such as English or German or Chinese, or between broader, narrower terms, etc., is just one format possible for displaying content within the search query element viewer. Other formats or methods to designate such “groupings” might include “mouse over” AJAX-based windows or other pop-up objects, word-wheel-type arrangements, visual models, graphical clusters, price arrays, and the like, depending on the needs of any given application.
- The notion of displaying different “groupings” of lexically-related alternatives, such as in multiple columns (for example, 508 and 512 in
FIGS. 7 and 548and 550 in FIG. 11), wherein each group might have a different semantic or lexical relationship to the query element (e.g., 540 in FIG. 540), is represented in the example process flow of FIG. 2b.
- It will be appreciated by those of ordinary skill in the art that other embodiments do not necessarily require the back-end of a network 20 or server 30 such as is shown in the embodiment of
FIG. 1. Using this approach, the query controller 200 and controlled vocabulary database 300 can reside solely within a LAN or within a single-user computer, such that the single-user (standalone) computer runs an application (software) local to the computer's operating system that creates the search query receiver function 100 and a form of the search query element viewer 500 in association with a localized database 300 located on the user's computer, or alternatively a controlled vocabulary database that is accessed across the LAN or network 20.
- It will be appreciated by those of ordinary skill in the art that in another embodiment the present invention and the search query element viewer/dynamic semantic list object can be used with RSS aggregation technology and tools in conjunction with controlled vocabularies, keyword sets such as those available from third parties, and all lexical elements associated with such vocabularies.
- In yet another embodiment, the search query element viewer 500 can be associated with an information system's individual pages and documents so that as the user enters a query into the search query receiver 100, non-structured lexical elements such as titles, keywords, phrases from the information system's pages or documents can be displayed in the search query element viewer from which the user can select an element for the purposes of navigating between pages or documents. For example, a Web site dealing with U.S. History is a form of an information system and as such, it may have thousands of pages, each with a title and content. In an example embodiment, the user could enter into the search query receiver “linco” and see within the search query element viewer all that Web site's pages that Lincoln in the title or body of the page or document.
- In still another embodiment the lexical elements of an information system displayed and selectable from within the search query element viewer could also include facts such as those from the CIA FactSheet site on countries, definitions, part numbers, page abstracts or key points, etc.
- In another embodiment, instead of pre-defined or pre-structured informational or lexical elements, the controlled vocabulary can be generated on-the-fly or dynamically from structured or unstructured data through use of clustering or extraction technology such as ExtractSum™ from SurfWax®. In this embodiment, which might be used for example with a Web site, the web pages on the site are parsed in real time and titles and keywords and concepts extracted and related using a series of dictionaries, word grouping and/or clustering techniques. These extracted items become lexical elements appropriate for that Web site (information system) and are thus available for use within the search query element viewer.
- As part of the back-office capability of one embodiment of the present invention, an administrative system 700 and interface, such as might be implemented in accordance with the process steps of
FIG. 3, allows the information system Administrator to load and maintain the controlled-vocabulary database along with setting global attributes and default user preferences for displaying the content within the search query element viewer.
- It should also be appreciated that while, for purposes of clarity and convenience, the example embodiment of
FIG. 1and corresponding description illustrate the use of a single search query receiver 100, that applications might utilize multiple search query receivers within a single search environment application. For example, a representative embodiment might include more than one search query receivers 100 within the same search page/environment. The search query receivers could be implemented to interact with one or more query controller(s) 200 which are in turn interfaced with one or more controlled vocabulary databases (300). Each search query receiver 100 could have its own search query element viewer/dynamic list object. For example, there could be a search query receiver labeled “authors” and another labeled “titles.” As the user interacts with the “author” search query receiver, the corresponding search query element viewer might show lexically-related content, such as author names. When the user interacts with the search query receiver for “titles,” the corresponding search query element viewer will contain lexically-related content, such as book titles. In a related application, the lexically-related element selected from one search query element viewer could be used to automatically (based on similar lexical relationships as previously discussed) constrain the vocabulary values appearing in the second search query element viewer for “titles.” For example, if the user enters “Hemi” in the author search query receiver and then selects “Ernest Hemingway” in the author search query element viewer, then when the user starts to enter/interact with the titles search query receiver, only titles lexically related to the author Ernest Hemingway might appear in the Titles search query element viewer, such as “Old Man and the Sea” and “For Whom the Bells Toll.”
- In a related variation, multiple lexicons could be served/accessed from one search query receiver. For example, the user may switch between lexicons (or portions thereof) using a separate screen object such as a pull-down menu or checkboxes that permit selection of one lexicon from multiple lexicons such as Author or Titles or ISBN. Then whatever the user enters in the single search query receiver, based on the switch selected by the user, the single search query element viewer will display/contain values from the respective lexicon. In this embodiment one search query receiver and its respective search query element viewer can provide access to multiple lexicons. Other variations on these above themes could be provided.
- It will be evident that there are numerous embodiments of the present invention, which, while not specifically described above, are clearly within the scope and spirit of the invention. Consequently, the above description is considered to be exemplary only, and the full scope of the invention is to be determined solely by the appended claims.
Patent Citations (8)
|Publication number||Priority date||Publication date||Assignee||Title|
|US5794249A (en) *||1995-12-21||1998-08-11||Hewlett-Packard Company||Audio/video retrieval system that uses keyword indexing of digital recordings to display a list of the recorded text files, keywords and time stamps associated with the system|
|US20020087408A1 (en) *||1999-06-25||2002-07-04||Burnett Jonathan Robert||System for providing information to intending consumers|
|US7181438B1 (en) *||1999-07-21||2007-02-20||Alberti Anemometer, Llc||Database access system|
|US20030069877A1 (en) *||2001-08-13||2003-04-10||Xerox Corporation||System for automatically generating queries|
|US20030050927A1 (en) *||2001-09-07||2003-03-13||Araha, Inc.||System and method for location, understanding and assimilation of digital documents through abstract indicia|
|US20030115191A1 (en) *||2001-12-17||2003-06-19||Max Copperman||Efficient and cost-effective content provider for customer relationship management (CRM) or other applications|
|US20060095331A1 (en) *||2002-12-10||2006-05-04||O'malley Matt||Content creation, distribution, interaction, and monitoring system|
|US7890526B1 (en) *||2003-12-30||2011-02-15||Microsoft Corporation||Incremental query refinement|
Cited By (38)
|Publication number||Priority date||Publication date||Assignee||Title|
|US9495358B2 (en)||2006-10-10||2016-11-15||Abbyy Infopoisk Llc||Cross-language text clustering|
|US9323747B2 (en)||2006-10-10||2016-04-26||Abbyy Infopoisk Llc||Deep model statistics method for machine translation|
|US9235573B2 (en)||2006-10-10||2016-01-12||Abbyy Infopoisk Llc||Universal difference measure|
|US9098489B2 (en)||2006-10-10||2015-08-04||Abbyy Infopoisk Llc||Method and system for semantic searching|
|US9075864B2 (en)||2006-10-10||2015-07-07||Abbyy Infopoisk Llc||Method and system for semantic searching using syntactic and semantic analysis|
|US9633005B2 (en)||2006-10-10||2017-04-25||Abbyy Infopoisk Llc||Exhaustive automatic processing of textual information|
|US8805676B2 (en)||2006-10-10||2014-08-12||Abbyy Infopoisk Llc||Deep model statistics method for machine translation|
|US9069750B2 (en)||2006-10-10||2015-06-30||Abbyy Infopoisk Llc||Method and system for semantic searching of natural language texts|
|US9053090B2 (en)||2006-10-10||2015-06-09||Abbyy Infopoisk Llc||Translating texts between languages|
|US8892423B1 (en)||2006-10-10||2014-11-18||Abbyy Infopoisk Llc||Method and system to automatically create content for dictionaries|
|US8892418B2 (en)||2006-10-10||2014-11-18||Abbyy Infopoisk Llc||Translating sentences between languages|
|US9588958B2 (en)||2006-10-10||2017-03-07||Abbyy Infopoisk Llc||Cross-language text classification|
|US9471562B2 (en)||2006-10-10||2016-10-18||Abbyy Infopoisk Llc||Method and system for analyzing and translating various languages with use of semantic hierarchy|
|US8959011B2 (en)||2007-03-22||2015-02-17||Abbyy Infopoisk Llc||Indicating and correcting errors in machine translation systems|
|US20090006078A1 (en) *||2007-06-27||2009-01-01||Vladimir Selegey||Method and system for natural language dictionary generation|
|US8849651B2 (en)||2007-06-27||2014-09-30||Abbyy Infopoisk Llc||Method and system for natural language dictionary generation|
|US8812296B2 (en)||2007-06-27||2014-08-19||Abbyy Infopoisk Llc||Method and system for natural language dictionary generation|
|US20100235338A1 (en) *||2007-08-06||2010-09-16||MLS Technologies PTY Ltd.||Method and/or System for Searching Network Content|
|US8898132B2 (en) *||2007-08-06||2014-11-25||MLS Technologies PTY Ltd.||Method and/or system for searching network content|
|US20160283596A1 (en) *||2007-08-06||2016-09-29||MLS Technologies PTY Ltd.||Method and/or system for searching network content|
|US9396266B2 (en) *||2007-08-06||2016-07-19||MLS Technologies PTY Ltd.||Method and/or system for searching network content|
|US20150046426A1 (en) *||2007-08-06||2015-02-12||MLS Technologies PTY Ltd.||Method and/or system for searching network content|
|US9262409B2 (en)||2008-08-06||2016-02-16||Abbyy Infopoisk Llc||Translation of a selected text fragment of a screen|
|US9037565B2 (en)||2010-11-16||2015-05-19||Microsoft Technology Licensing, Llc||System level search user interface|
|US8515984B2 (en) *||2010-11-16||2013-08-20||Microsoft Corporation||Extensible search term suggestion engine|
|US20120124071A1 (en) *||2010-11-16||2012-05-17||Microsoft Corporation||Extensible search term suggestion engine|
|US8903844B2 (en) *||2011-04-27||2014-12-02||International Business Machines Corporation||Providing effective interactive query suggestions without query logs|
|US8898182B2 (en)||2011-04-27||2014-11-25||International Business Machines Corporation||Methods and arrangements for providing effective interactive query suggestions without query logs|
|US20120296635A1 (en) *||2011-05-19||2012-11-22||Microsoft Corporation||User-modifiable word lattice display for editing documents and search queries|
|US8972240B2 (en) *||2011-05-19||2015-03-03||Microsoft Corporation||User-modifiable word lattice display for editing documents and search queries|
|US9015152B1 (en)||2011-06-01||2015-04-21||Google Inc.||Managing search results|
|US8965750B2 (en)||2011-11-17||2015-02-24||Abbyy Infopoisk Llc||Acquiring accurate machine translation|
|US8989485B2 (en)||2012-04-27||2015-03-24||Abbyy Development Llc||Detecting a junction in a text line of CJK characters|
|US8971630B2 (en)||2012-04-27||2015-03-03||Abbyy Development Llc||Fast CJK character recognition|
|US20140040302A1 (en) *||2012-05-08||2014-02-06||Patrick Sander Walsh||Method and system for developing a list of words related to a search concept|
|US9626353B2 (en)||2014-01-15||2017-04-18||Abbyy Infopoisk Llc||Arc filtering in a syntactic graph|
|US9697557B2 (en)||2014-05-28||2017-07-04||Blake Quinn||System and method of electronic searching and shopping carts|
|US9626358B2 (en)||2014-11-26||2017-04-18||Abbyy Infopoisk Llc||Creating ontologies by analyzing natural language texts|
Also Published As
|Publication number||Publication date||Type|
|US5454106A (en)||Database retrieval system using natural language for presenting understood components of an ambiguous query on a user interface|
|US6778979B2 (en)||System for automatically generating queries|
|US7890526B1 (en)||Incremental query refinement|
|Shneiderman et al.||Clarifying search: A user-interface framework for text searches|
|US6026388A (en)||User interface and other enhancements for natural language information retrieval system and method|
|US7844599B2 (en)||Biasing queries to determine suggested queries|
|US7039635B1 (en)||Dynamically updated quick searches and strategies|
|US20060253427A1 (en)||Suggesting and refining user input based on original user input|
|US7747639B2 (en)||Alternative search query prediction|
|US7783644B1 (en)||Query-independent entity importance in books|
|US20070162481A1 (en)||Pattern index|
|US20110035345A1 (en)||Automatic classification of segmented portions of web pages|
|US20040215663A1 (en)||Media agent|
|US6850934B2 (en)||Adaptive search engine query|
|US20060031207A1 (en)||Content search in complex language, such as Japanese|
|Kowalski et al.||Information storage and retrieval systems: theory and implementation|
|US20110106807A1 (en)||Systems and methods for information integration through context-based entity disambiguation|
|US20090254540A1 (en)||Method and apparatus for automated tag generation for digital content|
|US5963940A (en)||Natural language information retrieval system and method|
|US20090144240A1 (en)||Method and systems for using community bookmark data to supplement internet search results|
|US20020099685A1 (en)||Document retrieval system; method of document retrieval; and search server|
|US7509313B2 (en)||System and method for processing a query|
|US20080040313A1 (en)||System and method for providing tag-based relevance recommendations of bookmarks in a bookmark and tag database|
|US6957213B1 (en)||Method of utilizing implicit references to answer a query|
|Yu et al.||The impact of web search engines on subject searching in OPAC|
Owner name: VISION POINT SERVICES, LLC, DELAWARE
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SURFWAX, INC.;REEL/FRAME:026855/0436
Effective date: 20110822
Owner name: SURFWAX, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HOLT, THOMAS D.;BURKE, LARRY S.;SIGNING DATES FROM 20060410 TO 20060411;REEL/FRAME:026855/0407
Owner name: GULA CONSULTING LIMITED LIABILITY COMPANY, DELAWAR
Free format text: MERGER;ASSIGNOR:VISION POINT SERVICES, LLC;REEL/FRAME:037328/0552
Effective date: 20150826