{'fraction_non_alphanumeric': 0.030726256983240222, 'fraction_numerical': 0.007262569832402235, 'mean_word_length': 4.562111801242236, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Task-aware search assistant

When users search the web, their goal is to accomplish something, which we call a search task. Previous studies have observed an average of 2.6–3.3 queries per search task [2, 3, 4] and Jones and Klinkner [2] found 16% of tasks were revisited over a three-day span of Yahoo! logs. These statistics suggest that a task-aware search assistant may aid users in continuing previous search tasks as well as new ones. There are several existing tools that are related or similar in nature to a task-aware search assistant, the most basic of which are built-in browser histories and extensions that make them easier to navigate. Both Google and Bing provide search histories over their respective services. However, these lack a task-oriented view of searches. The most closely related work that we are aware of is Yahoo’s Search Pad, which attempts to automatically identify that a user is conducting research (e.g., planning a vacation). It then notifies the user and begins tracking queries and result clicks in an interface, to which the user can add and remove content. Two drawbacks are its lack of support for non-research tasks and its restriction to Yahoo! search only. Our approach to aiding users during search—both for new and continuing tasks—is to present them with an easy to use sidebar implemented as a browser extension. The interface consists of a collapsible sidebar in the browser with multiple panes that can be paged through using streamlined navigation buttons. The primary pane displays three key groupings: (1) a list of the most recent search tasks, (2) a list of related queries entered in the past, and (3) a list of related tasks conducted in the past. Note that a task consists of a cluster of queries and visited documents. This primary