Abstract:
Described is a collection of search-related references authored from a set of search results, in which the collection may be persisted. Search results may be obtained via a federated search of multiple data sources (e.g., local files, the Internet, a corporate network/database). Search results may be presented as individual reference items or grouped into dynamic collection query reference sets, which may be added to the collection. A collection may also embed one or more other collections. Upon opening a collection, search results may be automatically updated by re-running any dynamic collection queries. The user authors the collection by selecting items from a search results interface and dropping or pasting the item reference into a collection interface, and/or by activating an item collection affordance associated with the item. Manual or automatic layout of collection item references is provided, such as to provide a tabular layout or a two-dimensional layout.

Description:
BACKGROUND 
       [0001]    Computer users frequently deal with large amounts of information in their file systems, databases, and online search engines. These users often have a need to collect various individual data into a presentation, such as for reference or for publishing purposes. 
         [0002]    Current search user interfaces are becoming the primary portal to a user&#39;s information. However, existing search applications do not have facilities for collecting search results. Existing mechanisms for saving search-related results (e.g., cutting-and-pasting relevant search information into a document) lose information, and/or are not sufficiently flexible. 
       SUMMARY 
       [0003]    This Summary is provided to introduce a selection of representative concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used in any way that would limit the scope of the claimed subject matter. 
         [0004]    Briefly, various aspects of the subject matter described herein are directed towards a technology by which a user interacts with a set of search results to author a collection from the search results. The collection may then be persisted, such as in the form of a named compound query document. The search results may be obtained by performing a federated search of multiple data sources (e.g., local files, the Internet, a corporate network/database). The search results may be presented as individual item reference or grouped into dynamic collection queries, whereby individual item references or dynamic collection queries (reference sets) may be added to the collection. A collection may also embed one or more other collections. Upon opening a collection, the search results therein may be automatically updated by re-running the dynamic collection query or queries. 
         [0005]    In one aspect the user is able to select an item for inclusion as a reference in the collection, such as by dragging or cutting/copying the item reference from the search results interface and dropping or pasting the item reference into a collection interface. Alternatively, or in addition to, the user is able to select an item reference for inclusion in the collection via an item collection affordance associated with the item. Activation of an item collection affordance will automatically create and open a collection if one is not already open for editing. 
         [0006]    In one aspect, the user is able to interact with the collection, including to edit its layout, such as to arrange a tabular layout or a two-dimensional layout of the item references, and also may request automatic layout. The user may also choose a particular visualization for a dynamic collection query, e.g., a slideshow of pictures, the properties of a document, and so forth. 
         [0007]    In one aspect, a user authors a static collection to view search-related abstract items, including one or more single data items, one or more dynamic collection queries, and/or one or more other static collections. A search results interface comprises a unified display interface coupled to a data integration layer to obtain search results from a federated search of a plurality of sources, including a network source, a local machine source or an Internet source, or any combination of network, local machine or Internet sources. The search results interface may include an item collection affordance to add item references that can be included into the collection. A collection interface receives the user interaction input for editing a layout of item references in the collection, to automatically lay out the item references in the collection, for adding another static collection to the collection, for adjusting the visualization of a dynamic collection query, and/or for viewing the layout in a tabular arrangement or two-dimensional arrangement. 
         [0008]    Other advantages may become apparent from the following detailed description when taken in conjunction with the drawings. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0009]    The present invention is illustrated by way of example and not limited in the accompanying figures in which like reference numerals indicate similar elements and in which: 
           [0010]      FIG. 1  is a block diagram representing the general concept of authoring a collection based on search results. 
           [0011]      FIG. 2  is a block diagram representation of example components involved with the authoring of a collection. 
           [0012]      FIG. 3  is a flow diagram representing example steps taken with respect to creating and/or authoring a collection. 
           [0013]      FIG. 4  is a representation of a user interface mechanism by which grouped search result items may be presented to a user for authoring a collection. 
           [0014]      FIG. 5  is a representation of a user interface mechanism by which grouped search result items may be alternatively presented to a user for authoring a collection. 
           [0015]      FIG. 6  is a representation of a user interface mechanism by which a collection may be authored. 
           [0016]      FIG. 7  is a representation of how a compound query document may be logically arranged to persist a collection. 
           [0017]      FIG. 8  shows an illustrative example of a general-purpose network computing environment into which various aspects of the present invention may be incorporated. 
       
    
    
     DETAILED DESCRIPTION 
       [0018]    Various aspects of the technology described herein are generally directed towards collecting search results into a lightweight list, in which references to the search items are maintained, as opposed to the items themselves. Some of the various aspects are directed towards the integration of authoring with a search experience, a straightforward mechanism (e.g., a single-click) for collection of items in search results, and automatic layout of collected items. Other aspects are directed towards on-demand synthesis of a collection container, multi-modal authoring (e.g., as a tabular list or two-dimensional arrangement), the embedding of dynamic queries within a static collection, and the dynamic presentation of static queries within a static collection. 
         [0019]    As will be understood, various examples are shown herein that facilitate the above concepts and aspects. However, these are only non-limiting examples for the purposes of describing the technology. As such, the present invention is not limited to any particular embodiments, aspects, concepts, protocols, formats, structures, functionalities or examples described herein. Rather, any of the embodiments, aspects, concepts, protocols, formats, structures, functionalities or examples described herein are non-limiting, and the present invention may be used various ways that provide benefits and advantages in computing in general. 
         [0020]    Turning to  FIG. 1 , there is shown a block diagram representing general concepts related to list collections. In general, one or more search mechanisms  102  perform a federated search of multiple data sources  104   1 - 104   m , such as a local file system, the Internet, a corporate database, and so forth. The search results  106  are then returned. 
         [0021]    As represented in  FIG. 1 , a lightweight list collection mechanism  110  includes a user interface  112  (e.g., a set of application windows, dialogs, wizards or other such interactive mechanisms) by which a user can preview and build one or more collections  114   1 - 114   n  from items returned in the search results  106  (or using search results of subsequent searches). As described below, such items include dynamic collection queries (e.g., sub-queries arranged as groups) and single data items. 
         [0022]    In one implementation, each collection (e.g.,  114   1 ) comprises a compound query document that contains references to the dynamic collection queries and single data items. Moreover, a collection may contain other static collections, and even searches, e.g., the search terms used to locate items. 
         [0023]    In general, and as described below, a user authors the collection via the user interface  112 , and thereafter can access the items in a collection. Thus, for example, a user can retrieve a document via a reference to that document (e.g., a file location on a local drive or server) maintained in that collection. With respect to dynamic queries, the lightweight list collection mechanism  110  is coupled to the search mechanisms  102 , and may execute a new search to obtain updated search results whenever the user accesses such a dynamic item. 
         [0024]      FIG. 2  represents components in an example list collection implementation. As represented in  FIG. 2  and as analogous to  FIG. 1 , a user conducts a search, drawing from a plurality of search providers, such as providers located on the Internet (e.g., web search  202 ), on the local machine (e.g., local file system  203 ) and/or on a local network (e.g., database  204 ). Search results are collated in the data integration layer  206  and in one implementation are presented in a consistent manner in the unified display interface  208 . 
         [0025]    For example, within the unified display interface, results can be inspected via a floating preview  210 , which appears in a separate window atop a primary window when the user hovers over an item, e.g., like a tooltip, containing an image representative of an item, a set of properties for the item, and so forth. Alternatively, results may be presented in a rich item display  211 , which appears within the unified display interface, or within a preview pane  212 , which appears adjacent to the unified display interface  208 , e.g., showing a magnified view of an item. 
         [0026]    Each of these different views contains an item collection affordance, represented by blocks  214 - 216 , respectively. For example, an affordance may be in the form of an accompanying icon which when clicked activates a collection process, within a right-click dropdown menu, and so forth. 
         [0027]    When the user activates the respective item collection affordance, a collection process is initiated for that item. In one implementation, if a collection is already started, the indicated item is placed into that collection by the process; otherwise a new collection is automatically started, and the indicated item placed into the newly started collection by the collection process. This concept is represented in  FIG. 2  by the list accumulation user interface (UI)  222 . Note that entire searches may be placed within the collection, and these searches may retain their dynamic qualities. For example, if new items match the search, they can be displayed within the collection even if they were created after the collection. 
         [0028]    Once a collection exists, the user may arrange and rearrange items within the collection as desired, such as by dragging items around a canvas. This concept is represented in  FIG. 2  by the list editing user interface (UI)  224 . The user further may add graphical and textual annotations, e.g., in association with a selected item. 
         [0029]    As represented by the block  226 , the user may also select an automatic list layout, which arranges the contents of the collection in tabular format. Automatic list layout may also arrange items in another format, such as a two dimensional layout. 
         [0030]    Once the collection is organized in a form that the user desires, the user can persist the collection; (note that a user also can re-edit a collection at a later time). As described below, in one implementation the collection is saved as a compound query document that contains the references to the items, including dynamic items. The collection may also contain other static collections, and searches, either as references thereto or as the references/search terms themselves. Thus, the collection is lightweight because it contains references to large-sized items, rather than the contents of large items. Moreover, having a collection facilitates leaving a document in place; for example, a document on a server may get updated by various users, whereas a local copy made from that server document in one state becomes outdated if that document is changed. 
         [0031]      FIG. 3  is a flow diagram representing various aspects of collection authoring, beginning at step  302  where the user conducts a search  302 . Step  304  gives the user an option of viewing the search results as a list (step  306 ) or in groups (step  320 ). Examples of grouping are set forth below. Note that if a list view is selected, a user may interact with any partial results as they are returned, however in general grouping is performed only when a search is complete. 
         [0032]    If the user selects the list view, the user can select an item and add it to the collection by a selection mechanism (e.g., dragging and dropping an item, step  308 ) or via its affordance (step  310 ), e.g., into an open collection at step  316 . Note that in this example if the user activates an item&#39;s affordance at step  310 , and no collection is currently open (step  312 ), a collection is automatically created and opened at step  314 , (an on-demand synthesis of a collection container) before the item is added to the collection at step  316 .  FIG. 6  shows an example of a canvas  600 , corresponding to a “mix” window, for placing and then rearranging items (and groups, described below) during the collection authoring process. 
         [0033]    Step  328  represents looping back to add more items to the collection until the user is done; note that a new search may be conducted, or the user may continue to interact with the current search results. 
         [0034]    If at step  304  the user chooses to view the results as dynamic collection queries, e.g., groups, step  320  is performed. Examples of grouping include grouping by item type (such as differentiating documents, pictures, emails), grouping by document author or owner, grouping by date and so forth, essentially grouping by any property set/metadata accompanying an item.  FIGS. 4 and 5  show different ways groups may be represented in a results window, e.g., as a stack representation  400  or as an arrangement  500  of groups with their respective single items set forth below. 
         [0035]    As represented by step  322 , groups can be selected and placed (e.g., dragged/copied and dropped/pasted into a list collection.  FIG. 6  shows an example of a canvas  600 , corresponding to a “mix” window, for placing single static items and groups during the authoring process and then rearranging them (manually or automatically) as desired. 
         [0036]    A user can also choose a visualization for a group, as represented via step  324 , e.g., using a visualization selection mechanism  402  in  FIGS. 4 and 5 . For example, a user may choose to put a group of pictures into a slideshow visualization, show detailed text of a debug report, show properties of documents, and so forth. Whether a user chooses a visualization or uses the default visualization, the group (dynamic query) is placed into the collection at step  326 . 
         [0037]    Once the collection is authored, the collection is saved, as represented at step  322 , e.g., in a named compound query document containing the items. The collection may also be shared, as represented via step  334 . 
         [0038]    An example of a compound query document is represented in  FIG. 7 , and may be (logically) hierarchically arranged. In  FIG. 7 , static collections are represented by a circle, dynamic collection queries by a triangle, and single data items by a square. Note that the top abstract item is a static collection, and corresponds to the Mix canvas when saved (e.g., named “Static Collection X”. As can be seen in  FIG. 7 , single static items may be embedded into a static collection, dynamic queries may be embedded into a static collection, and/or other static collections may be embedded into a static collection (e.g., “Project 1” and Scratch” which contain single items and a combination of single items and a dynamic collection query, respectively). Any practical number of abstract items may be maintained in a collection, and arranged and nested as desired by the collection author. 
         [0039]    Further, a search and/or its results may be saved as an abstract item within a collection. However, with respect to sharing a collection, note that as can be readily appreciated, while in general a user may want to share a collection, the user may not want to share every item found within a collection. For example, a collection may dynamically search a user&#39;s email messages corresponding to an “email” group or the like, whereby any new emails, including sensitive or personal ones, would be accessible. To prevent this, an author may choose to make search results static instead of dynamic. When the collection is re-opened, a new search will not be performed on any search marked static, essentially pinning the result set. Note that the search query still exists and can be reused, but opening the collection (e.g., via the Mix user interface will not re-run the query. 
       Exemplary Operating Environment 
       [0040]      FIG. 8  illustrates an example of a suitable computing system environment  800  on which the examples represented in  FIGS. 1-7  may be implemented. The computing system environment  800  is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment  800  be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment  800 . 
         [0041]    The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to: personal computers, server computers, hand-held or laptop devices, tablet devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like. 
         [0042]    The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, and so forth, which perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in local and/or remote computer storage media including memory storage devices. 
         [0043]    With reference to  FIG. 8 , an exemplary system for implementing various aspects of the invention may include a general purpose computing device in the form of a computer  810 . Components of the computer  810  may include, but are not limited to, a processing unit  820 , a system memory  830 , and a system bus  821  that couples various system components including the system memory to the processing unit  820 . The system bus  821  may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus. 
         [0044]    The computer  810  typically includes a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by the computer  810  and includes both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by the computer  810 . Communication media typically embodies computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer-readable media. 
         [0045]    The system memory  830  includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM)  831  and random access memory (RAM)  832 . A basic input/output system  833  (BIOS), containing the basic routines that help to transfer information between elements within computer  810 , such as during start-up, is typically stored in ROM  831 . RAM  832  typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit  820 . By way of example, and not limitation,  FIG. 8  illustrates operating system  834 , application programs  835 , other program modules  836  and program data  837 . 
         [0046]    The computer  810  may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,  FIG. 8  illustrates a hard disk drive  841  that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive  851  that reads from or writes to a removable, nonvolatile magnetic disk  852 , and an optical disk drive  855  that reads from or writes to a removable, nonvolatile optical disk  856  such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive  841  is typically connected to the system bus  821  through a non-removable memory interface such as interface  840 , and magnetic disk drive  851  and optical disk drive  855  are typically connected to the system bus  821  by a removable memory interface, such as interface  850 . 
         [0047]    The drives and their associated computer storage media, described above and illustrated in  FIG. 8 , provide storage of computer-readable instructions, data structures, program modules and other data for the computer  810 . In  FIG. 8 , for example, hard disk drive  841  is illustrated as storing operating system  844 , application programs  845 , other program modules  846  and program data  847 . Note that these components can either be the same as or different from operating system  834 , application programs  835 , other program modules  836 , and program data  837 . Operating system  844 , application programs  845 , other program modules  846 , and program data  847  are given different numbers herein to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer  810  through input devices such as a tablet, or electronic digitizer,  864 , a microphone  863 , a keyboard  862  and pointing device  861 , commonly referred to as mouse, trackball or touch pad. Other input devices not shown in  FIG. 8  may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit  820  through a user input interface  860  that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor  891  or other type of display device is also connected to the system bus  821  via an interface, such as a video interface  890 . The monitor  891  may also be integrated with a touch-screen panel or the like. Note that the monitor and/or touch screen panel can be physically coupled to a housing in which the computing device  810  is incorporated, such as in a tablet-type personal computer. In addition, computers such as the computing device  810  may also include other peripheral output devices such as speakers  895  and printer  896 , which may be connected through an output peripheral interface  894  or the like. 
         [0048]    The computer  810  may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer  880 . The remote computer  880  may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer  810 , although only a memory storage device  881  has been illustrated in  FIG. 8 . The logical connections depicted in  FIG. 8  include one or more local area networks (LAN)  871  and one or more wide area networks (WAN)  873 , but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet. 
         [0049]    When used in a LAN networking environment, the computer  810  is connected to the LAN  871  through a network interface or adapter  870 . When used in a WAN networking environment, the computer  810  typically includes a modem  872  or other means for establishing communications over the WAN  873 , such as the Internet. The modem  872 , which may be internal or external, may be connected to the system bus  821  via the user input interface  860  or other appropriate mechanism. A wireless networking component  874  such as comprising an interface and antenna may be coupled through a suitable device such as an access point or peer computer to a WAN or LAN. In a networked environment, program modules depicted relative to the computer  810 , or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,  FIG. 8  illustrates remote application programs  885  as residing on memory device  881 . It may be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used. 
         [0050]    An auxiliary subsystem  899  (e.g., for auxiliary display of content) may be connected via the user interface  860  to allow data such as program content, system status and event notifications to be provided to the user, even if the main portions of the computer system are in a low power state. The auxiliary subsystem  899  may be connected to the modem  872  and/or network interface  870  to allow communication between these systems while the main processing unit  820  is in a low power state. 
       CONCLUSION 
       [0051]    While the invention is susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in the drawings and have been described above in detail. It should be understood, however, that there is no intention to limit the invention to the specific forms disclosed, but on the contrary, the intention is to cover all modifications, alternative constructions, and equivalents falling within the spirit and scope of the invention.