HRP20040440A2 - File system shell - Google Patents

Description

Field of invention

This invention relates to file systems, and more specifically, to a file system shell.

Background of the invention

Existing computer file systems have a number of undesirable limitations. One of the limitations is that it is generally not possible for users to control the structure that is presented to them. In other words, when the folders are organized, the user has to choose a structure and this structure is very difficult to change later. As a specific example, for the "music" folder, the user can choose to organize music files in an artist/album format, where all album folders for each individual artist are grouped into a folder for that specific artist, and all songs from a specific album are grouped into a folder of that album. The artist/album format is not suitable for playing a specific type of music (eg, playing two jazz tracks by two different artists), or playing a selection of albums by different artists.

As an additional circumstance, the user may have a large number of files that are difficult to organize. Some users apply strict placement principles for files, creating rigid hierarchies for them. Managing such files becomes increasingly complex and difficult as the number of available files increases, making search and retrieval also complex. This problem is further exacerbated when using additional files from other locations, such as file shares, etc.

Users also have to deal with the fact that files are located in different locations, such as on different devices, on different PCs or on the network. For example, a user can choose to listen to their music on a computer (as it can be accessed by a music program) or they can connect to a network and listen to music from Web sites, but there is a strong division between these two sources. Music coming from different locations is organized differently, and is not kept in the same way or in the same place. As another example, files stored on the corporate network may be separated in advance from the files the user owns on the current machine.

Users must also take care not only of which data files are stored, but also where they are stored. For example, for music files, users are forced to keep copies on various systems and try to keep track of where which music files are located. This can make finding files difficult even if they are stored locally.

Sometimes it is also difficult to find and return to files that the user owns. It can be difficult for the user to remember where and how he saved certain files. In a given set of folders and even a group of similar files, it is often difficult for users to find the file they want in a short time. For files stored in a place that is difficult to find, locating is all the more complicated. Additionally, once users have enough files in a folder, it becomes even more difficult to analyze the folder in a short amount of time, especially if the content is similar.

Sometimes users also find it difficult to find and return to files online. Sharing and publishing files is often difficult to do, and it can often be even more difficult to obtain such a file from someone who makes it available. Users usually have to remember or write down the various locations and names they need to find files online.

Namespaces can vary, which can cause confusion for users as to what is "correct". This is especially true for a network where there are different naming conventions, restrictions, and so on. For example, certain operating systems may require short names without spaces in order for files to be visible to them.

Programs also often store files in their own folder or other namespace, which can make it difficult for users to find their way back to files. Programs often have default folders and locations where they store documents. The user often has to search through their hard drive and guess where the file is stored.

Related items are also often stored in separate locations. Associated files owned by the user may be stored on different parts of the hard disk, etc. This problem becomes more common with the development of digital media services that contain multiple types of content (eg, images, music, video).

Another problem with file systems is the address bar. As users navigate within the file system on a computer, a common graphical interface control, called the address bar, shows users where they are within the file system hierarchy. The usual address bar shows the current location with respect to the hierarchical structure of folders, subfolders and files of the file system. Changing the user's location displayed in the usual address bar is typically done in one of two ways. The first way is to manually change the address in the address bar. Manually changing the address in the address bar allows the user to move to any number of locations in the file system hierarchy, but requires the user to have specific information regarding the organization of the file system on the computer, i.e. a specific location within the file system. Another method involves using external navigation tools that, when used, refresh the address bar to show the new address or location. Although this avoids manually changing the address in the address bar, the use of external navigation tools still requires the user to have specific information regarding the organization of the file system and to navigate through the hierarchical structure. However, a normal address bar cannot reference files or data stored among multiple file system locations, such as folders or devices, because of the one-to-one relationship between an address in the address bar and a specific location in the file system hierarchy.

Previous developments in this area lack an address bar that allows users to specify addresses that display files stored among multiple file system locations. Prior achievements also lack an address bar that also allows users to simply change an address in the address bar without manually changing that address or requiring them to have specific knowledge of the underlying file system organization. Also missing from earlier advances in this area is an address bar that presents alternative file selections to the user and from which the user can choose to navigate to those file selections. Such an address bar could also selectively display a normal address bar interface to the user, allowing them to interact with the address bar in accordance with their previous experience, according to the user's preferences.

Another problem with file systems has to do with identifying things stored on a computer. The need to readily identify things stored in a computing environment such as a personal computer (PC) is increasing dramatically due to the increase in the number of individuals using computers in their daily routines and because the type of data stored varies between images, music, documents, etc. Documents and contents of various media are usually stored in computers in a hierarchical manner and are organized as data files or media records stored inside folders. File system browsers allow users to navigate through the file system and find and open files and folders. For example, WINDOWS® EXPLORER™, manufactured by Microsoft Corporation, is an operating system utility that allows users to browse the file system.

Many users find it difficult to correctly identify a file based on the information currently available in common file system browsers. Of course, it is possible to check the contents of the file by opening it using an application program, but this method of viewing files is extremely inefficient. The ability to view file metadata within a file system browser can greatly assist a user in identifying a particular file without having to open it. In WINDOWS® 9X operating systems, manufactured by Microsoft Corporation, for example, a user can view metadata about an object by accessing the property page for a particular object. A property page presents the user with a list of an object's attributes or settings in the form of a selection of property pages arranged with index-tab-like inserts, each of which includes standard dialog-style controls for adjusting parameters. However, using the property page to find items can be slow and clunky, and some users find it difficult to find relevant metadata within the property page. Similarly, using the info tooltip to find files can be slow and clunky because the user must hover over each file to see the limited metadata displayed in the info tooltip.

Common file system browsers do not allow users to enter and modify metadata related to files and folders, which would greatly improve the user's ability to locate the file later. To date, the ability of users to enter and modify metadata has been limited to special purpose software programs. For example, media players for electronic music files provide the user with the ability to change the metadata associated with a music album and artist. Another example of such programs includes application programs for electronic image files. However, the use of media players and other such programs is limited to the specific file type supported by the program, unlike a general-purpose file system browser that supports multiple data types.

The WINDOWS® XP operating system, manufactured by Microsoft Corporation, includes a picture viewer for use in the "My Pictures" folder. The My Pictures folder is endowed with special features that allow users to view pictures as photos and not just as document icons. Image browsing capabilities in the My Pictures folder include the ability to view thumbnails and large versions of photos, rotate photos that are sideways, and create an image slideshow. The user can also view details about the photo, such as its dimensions, the date and time it was created, and the name of the camera that took it. The preview control area in the My Pictures folder contains a zoomed-in preview image of the image the user has selected, toggle buttons to help the user scroll through a series of images, and controls to rotate the image clockwise and counterclockwise on an hour. Although the image viewing capabilities of WINOWSIMA® XP have advanced the state of the art in this area by alleviating the need to call an application program to view and manage images, users are still unable to enter and modify metadata associated with images.

Accordingly, there is a need for an improved user experience within a file system shell or browser that allows users to readily locate an object based on the metadata associated with that object. There is also a need for a system and method that allows users to enter and modify metadata associated with objects of various types within a shell browser without having to call an application program. There is also a need for a file system or shell browser that offers users enhanced file content recognition capabilities so that users can readily locate their files. There is also a need for an improved graphical user interface for the shell viewer that allows selecting a pre-viewer for a specific file type from among the many available pre-viewers. There is also a need for an extensible shell browser that would allow software developers to provide additional information and functionality to users based on file types. There is also a need to provide a similar user interface experience across different subject sets.

Summary of the invention

In accordance with one aspect of the invention, a system and method using virtual folders is provided. Virtual folders expose regular files and folders (also known as directories) to users in various views based on their metadata instead of based on the actual physical background structure of the file system on disk. In this way, the system is able to take a property that is stored in the database and display it as a folder-like container. Given that users are already familiar with working with maps, by displaying virtual maps in a similar way, users can quickly adapt to the new system.

In accordance with another aspect of the invention, virtual folders are provided in accordance with a method used on a computer system having a display and data storage memory. According to the method, the metadata property is selected. The system then searches for items that have the selected metadata property, and provides a virtual folder display object that represents the set of items that have that metadata property.

In accordance with another aspect of the invention, the system includes a map processor that obtains queries from users and a relational database for storing item information. The map processor first obtains a query from the user and forwards the query to the relational database. The relational database provides results back to the map processor, and based on the results from the relational database, the map processor provides the results to the user as virtual maps. In one embodiment, the results provided back to the map processor include database rows and columns. The rows and columns of the database are converted by the map processor into a numerator structure, which is then used to populate the screen with the resulting virtual maps.

In accordance with another aspect of the invention, users can work with virtual maps through direct management. In other words, the mechanisms provided to manage virtual folders are similar to those currently used to manage regular physical folders (eg, click and drag, copy, paste, etc.).

In accordance with another aspect of the invention, a method for performing direct management of virtual folders is provided in a computer system having a display and memory for storing items. In accordance with the method, subject groups are represented as virtual folders. Defined actions are provided that can be performed to directly manage virtual folders, where when the defined action is performed, the virtual folder is managed in the manner specified by the defined action. An example of a defined action would be clicking and dragging a virtual folder. In one embodiment, the act of clicking and dragging a virtual folder to a second virtual folder performs the function of copying items from the first virtual folder to the second virtual folder. Copying items to a virtual folder may include adding or otherwise modifying selected metadata properties associated with the items.

In accordance with another aspect of the invention, filters are provided for managing virtual folders. Filters are basically tools for narrowing down a set of items. In one embodiment, filters are dynamically created based on properties of separate objects. For example, for a collection of items, the filter mechanism can inspect the properties, and if the items generally have “authors” as a property, the filter can provide a list of authors. After that, by clicking on a specific author, items that do not have that author disappear. This allows users to narrow down the content.

In accordance with another aspect of the invention, a method for filtering items is provided in a computer system having a display and memory for storing items with metadata properties. Display objects are provided on the screen so that each one represents one or more objects. The metadata properties of the objects represented by the rendering objects are evaluated. A filter boundary is provided on the screen to correspond to a metadata property that is shared among the plurality of data, wherein selecting the filter boundary causes the objects displayed on the screen to be narrowed down to those objects that share the particular metadata property.

In accordance with another aspect of the invention, a plurality of objects are displayed on the screen, and the filter boundary is dynamically generated based on the metadata property of the object. When a filter limit is selected, it narrows the objects that are presented on the screen to those that have a metadata property that matches the filter limit.

In accordance with another aspect of the invention, a plurality of objects are displayed on the screen, and a filter area is provided in which the user can enter a filter boundary. When a filter limit is entered by the user, the items displayed on the screen are narrowed to those that contain the filter limit. As the user types the filter limit, additional items can be filtered by matching each new character to the filter limit.

In accordance with another aspect of the invention, a back button is provided that can be used to backtrack through the filtering process. For example, after the user has entered a filtering limit, the user may wish to return to the set of items that were displayed on the screen before the filtering limit was applied. The back button allows the user to return to the desired point in the filter navigation.

In accordance with another aspect of the invention, quick links are provided. In one embodiment, the quick links are a set of predefined links (eg, located on the left side of the screen) that can be clicked to create useful views of sets of items. These can be predefined by the program, or set by the user. For example, clicking on “all authors” might return a view organized by authors. “All Documents” can return a flat view of all documents across all storage areas. Users can also create their own quick links. For example, a user can filter out all the documents they changed in January 2003, and then save it as a quick link.

In accordance with another aspect of the invention, a method for providing quick links is embodied in a computer system having a screen and memory for storing items. According to the method, the user first navigates to view the desired set of items. A quick link corresponding to the desired set of items is stored and given a name. The name of the quick link is displayed on the screen in such a way that by clicking on the quick link the user can return to the view of the desired set of subjects.

In accordance with another aspect of the invention, libraries are provided. Libraries consist of large groups of usable file types that can be linked together. For example, photos can be one library, music can be another, and documents can be a third. Libraries provide tools and activities related to a specific type of subject. For example, in the photo library, there are tools and filters related to photo management, such as creating image slideshows or sharing images.

In accordance with another aspect of the invention, a method for creating libraries is provided in a computer system having a display and memory for storing items. The method begins by creating a library that will contain objects with one or more specified metadata properties. After that, objects with one or more specific metadata properties are automatically grouped into a library. Tools are provided to manage items in the library.

In accordance with another aspect of the invention, a wide range of files or objects may be accessible. In other words, the system is capable of displaying files/items from multiple physical locations (eg, different hard drives, different computers, different network locations, etc.) so that it appears to the user that all the items are from one location. For example, a user can have all his music files displayed on one screen, and he can manage all files from a single view, even though the files may be physically stored on different hard drives, different computers, or different network locations.

In accordance with another aspect of the invention, the array is used in a method for displaying an object in a computer system having a screen. The method includes determining a range of physical memory locations from which to retrieve items, wherein the range consists of present computer memory and at least one other physical location. Once a query is received, objects are retrieved from the physical locations specified by the range in response to the query, and the objects retrieved by the query are then displayed in the view on the screen. In one embodiment, the at least one other physical location may be another computer, a network location, or an external data storage device. In one embodiment, the screen view can be switched to a physical folder view that indicates the physical locations where items are physically stored.

In accordance with another aspect of the invention, objects other than files may be displayed in virtual folders. In other words, files that are stored in memory are located in local storage. Virtual folders can be made to include items that are not currently represented in the physical repository. Examples of non-file items are e-mails and contacts.

In accordance with another aspect of the invention, a method for displaying non-file items is embodied in a computer system having a display and memory for storing the items. The method includes providing a database that allows both non-file objects and file objects to be searched by queries. Once a query is received, both the non-file items and the file items that satisfy the query are retrieved, and the items that satisfy the query are then displayed on the screen. In one embodiment, a relational database is provided that includes selected file object data, and may contain certain non-file objects in its entities.

In accordance with another aspect of the invention, a virtual address bar is provided for selecting content stored in a computer file system. A virtual address bar consists of many segments. Each segment corresponds to a filter for selecting content stored in a computer file system. Collectively, the corresponding filters of each segment in the virtual address bar represent a virtual address for selecting content stored in the computer file system.

Each segment is an interactive segment that can respond to user interaction to change the virtual address from the virtual address bar. Selecting a segment in the virtual address bar causes those segments that follow the selected segment to be removed from the address bar. Alternatively, selecting a segment in the virtual address bar causes the user to display a list of selectable peer-to-peer filters. Co-level filters are filters on the same level as the filter corresponding to the selected segment. The consequence of selecting one of the co-level filters is that the alternatively selected segment replaces its corresponding filter with the selected co-level filter. Additionally, those segments that follow the alternatively selected segment are removed from the virtual address bar.

Segments can be added to the virtual address bar in accordance with external user actions. The segments are added to the end of the segments in the virtual address bar. Any segments that conflict with the added segment are removed. An existing segment in the virtual address bar conflicts with the added segment when the existing segment is mutually exclusive with the added segment. An existing segment in the virtual address bar also conflicts with the added segment when the existing segment is wider or narrower in range than the added segment.

In accordance with another aspect of the invention, a shell browser is provided that includes a window and a change control. The window displays a group of items and also displays the metadata values associated with one or more displayed items. A change control allows the user to change at least some of the metadata values displayed in the window.

In accordance with another aspect of the invention, the graphical user interface is embodied in a computer-readable medium and is executable on a computer. The graphical user interface includes a first screen area that displays a set of objects in a shell browser and a second screen area that displays metadata associated with one or more displayed objects. The graphical user interface also gives the user a means within the shell browser to change the displayed metadata.

In accordance with another aspect of the invention, computer-implemented methods are provided to enable a user to modify metadata within a shell browser. One such method includes displaying a plurality of items, receiving a first input from the user representing a selection of at least one of the displayed items, displaying metadata associated with the selected item(s), and providing a change control for the user to modify the displayed metadata. Another such method includes displaying a welcome box and metadata associated with the welcome box and providing a change control for the user to modify the displayed metadata.

In accordance with another aspect of the invention, a data structure containing metadata associated with one or more objects is displayed in a shell browser. The data structure, which is stored on one or more computer-readable media, includes a field containing user-modifiable metadata associated with one or more displayed objects, and the user-modifiable data contained in the data structure is also displayed in the shell browser.

In accordance with another aspect of the invention, a shell browser is provided that includes a default pre-browser and an extensibility mechanism. The default previewer provides a standard level of functionality for multiple item types. The extensibility mechanism provides functionality beyond the standard level provided by the default previewer for one or more item types.

In accordance with another aspect of the invention, a shell browser is provided that includes a first pre-browser and a second pre-browser. The first previewer provides a standard level of functionality for multiple item types, and the second previewer provides an alternative or extended level of functionality for one or more item types. The shell viewer is set to selectively use either the first pre-browser or the second pre-browser for one or more object types.

In accordance with another aspect of the invention, a graphical user interface is provided for a shell browser that supports multiple object types. The graphical user interface includes a first screen area for displaying a set of objects in a shell viewer and means for selecting a preview viewer for the displayed objects from among a plurality of available preview viewers.

In accordance with another aspect of the invention, there is provided a computer-implemented method for selecting a pre-viewer in a shell browser that supports multiple data types. The method includes providing a plurality of previewers in a shell browser for a particular item type and selecting one of the previewers for a particular item type. The method then associates the selected previewer with a specific item type.

In accordance with another aspect of the invention, a computer-implemented method is provided for enabling the use of third-party previewers in a shell browser that supports multiple object types. The method includes providing a shell viewer that has a default preview viewer for the multiple object types and providing an extensibility mechanism that allows third parties to develop an alternative preview viewer for at least one of the multiple object types.

In accordance with another aspect of the invention, a data structure is provided that contains information that points to a plurality of previewers in a shell browser. The data structure, which is stored on one or more computer-readable media, includes a first field that contains information pointing to a default previewer that supports multiple object types. The second field contains information indicating an alternate previewer for the first item type, and the third field contains information indicating whether the default previewer or the alternate previewer should be invoked when items of the first item type are displayed in the shell browser.

In accordance with another aspect of the invention, different object types are grouped into libraries that are provided with a similar set of basic user interface capabilities. In other words, a similar set of basic user interface capabilities is provided for different types of libraries, such as document libraries, photo libraries, and music libraries. This set of basic user interface options may include options such as filtering, creating new categories, changing item metadata, changing pivots, etc. A similar set of basic user interface options for libraries allows the user to process and organize different types of items using the properties and capabilities provided by already meet.

Brief description of the drawing

The foregoing aspects of the invention and many of the advantages present will become more fully appreciated upon better understanding by reference to the following detailed description, especially when considered in conjunction with the accompanying drawings, in which:

SECTION 1 is a block diagram of a general purpose computer system suitable for carrying out the present invention;

PARAGRAPH 2 presents a block diagram of a virtual folder system in accordance with the present invention;

SECTION 3 is a flowchart illustrating a routine by which a user provides a query that plots selected files and folders;

NUMBER 4 is a flowchart illustrating a routine by which virtual maps are constructed and displayed on the screen in accordance with either an assumed query or a user query;

PARAGRAPH 5 tree diagram of the folder structure in accordance with the physical arrangement of the folders on the hard disk;

PARAGRAPH 6 is a tree diagram of the structure of virtual folders;

ITEM 7 is a tree diagram of the structure of the virtual folders from ITEM 6, where the stack of clients is further filtered by contract and year;

ITEM 8 is a tree diagram of the structure of the virtual folders from ITEM 7, where the client stack contracts are further filtered by year;

ITEM 9 is a tree diagram of the structure of virtual folders from ITEM 6, where the contract stack is further filtered by clients and year, of which clients are further filtered by year;

FIGURE 10 is a diagram illustrating a display of a screen showing document library stacks;

NUMBER 11 is a diagram illustrating a screen display showing documents from ABC Corp. therefore from PARAGRAPH 10;

ITEM 12 is a diagram illustrating a display of a screen in which a stacking function is selected for the documents of ITEM 11;

ITEM 13 is a diagram illustrating a display screen in which the “arrange by author” parameter is selected for the stacking function of ITEM 12;

ITEM 14 is a diagram illustrating the display of the screen in which the files from ITEM 13 are arranged by author;

ITEM 15 is a diagram illustrating a display screen in which the stack function is selected and the “stack by category” option is further selected to re-stack the files of ITEM 14;

ITEM 16 is a diagram illustrating a display screen in which the files from ITEM 14 are re-arranged into a table by category;

POINT 17 is a diagram illustrating a display of a screen in which a quick link is selected to display physical maps;

ITEM 18 is a diagram illustrating a display of a screen in which physical folders containing virtual folder stack files from ITEM 17 are displayed;

FIGURE 19 is a flow diagram illustrating a routine by which a user can directly manage virtual maps;

ITEM 20 is a diagram illustrating a screen display in which a new “West Coast” stack is added to the stacks of ITEM 10;

NUMBER 21 is a diagram illustrating a screen view in which direct control was used to copy files from the “ABC Corp.” stack. in the stack "West Coast" from ITEM 20;

FIGURE 22 is a flowchart illustrating a routine for a system that dynamically creates new filtering conditions;

FIGURE 23 is a flow diagram illustrating a routine for an item filtering system depending on the selection of filtering conditions;

ITEM 24 is a diagram illustrating a screen display in which the stacks from ITEM 10 are filtered by condition “AB”;

ITEM 25 is a diagram illustrating a screen display in which the stacks from ITEM 10 are filtered by the condition “ABC”;

ITEM 26 is a diagram illustrating a screen display in which the filtering condition “year 2002” is selected for the stacks of ITEM 10;

ITEM 27 is a diagram illustrating a display screen in which the stacks from ITEM 10 are filtered by the condition “year 2002” and further, the selection of the filtering condition “month” (“month”);

NUMBER 28 is a diagram illustrating a display of a screen displaying a list for selecting a month to filter;

ITEM 29 is a diagram illustrating the display of the screen where the stacks of ITEM 10 are further filtered by the month of January, and further shows the filtering condition "day";

NUMBER 30 is a flow chart illustrating a routine for creating a new fast link;

ITEM 31 is a diagram illustrating a screen display for creating a new quick link named “January Work” based on the filtering of ITEM 29;

PARAGRAPH 32 is a diagram illustrating the display of the screen in which the "All Authors" quick link is selected;

ITEM 33 is a diagram illustrating the display of the screen in which the list of all authors from ITEM 32 is displayed;

ITEM 34 is a diagram illustrating the display of a screen in which "Author 1" is selected from the list in ITEM 33 and all documents of Author 1 are displayed;

NUMBER 35 is a flowchart illustrating the routine for creating a new library;

FIGURE 36 is a diagram illustrating a display of a screen showing a set of various available libraries;

NUMBER 37 is a flow diagram illustrating a routine for determining the scope of a set of virtual folders;

FIGURE 38 is a block diagram illustrating the various sources that may comprise the scope of a set of virtual maps;

FIGURE 39 is a flowchart illustrating a routine for including non-file objects in a set of virtual folders;

FIGURE 40 is a diagram illustrating a display of a screen showing various non-file items included in a virtual folder;

ITEM 41 is a pictorial diagram of an exemplary network computing environment suitable for carrying out this invention;

FIGURE 42 is a pictorial diagram illustrating an exemplary file browser having a conventional address bar associated with displaying files in a computer file system, as has been previously common in the art;

ITEM 43 is a pictorial diagram illustrating an exemplary file browser for displaying files in a computer file system according to a virtual address in a virtual address bar configured in accordance with the present invention;

ITEM 44A is a pictorial diagram of the exemplary file browser of ITEM 5 illustrating selecting a segment of a virtual address in a virtual address bar to navigate within a file system;

ITEM 44B is a pictorial diagram of the exemplary file browser of ITEM 44A illustrating the results of selecting a segment of a virtual address in a virtual address bar;

NUMBERS 45A-45D are pictorial diagrams illustrating the selection of an equal level filter associated with a virtual address segment in a virtual address lane;

NUMBERS 46A-46D are pictorial diagrams illustrating adding additional filters to a virtual address in a virtual address bar;

NUMBERS 47A and 47B are pictorial diagrams illustrating an exemplary virtual address bar displaying virtual addresses wherein the virtual address exceeds the display capacity of the virtual address bar;

FIGURE 48A is a pictorial diagram illustrating an exemplary virtual address bar having a virtual address with filters that reference both virtual and physical locations in the file system;

ITEM 48B is a pictorial diagram illustrating the exemplary virtual address bar of ITEM 48A adjusted to display a conventional address bar;

NUMBER 49 is a flow diagram illustrating an alternative filter selection routine for selecting alternative filters in a virtual address bar;

ITEM 50 is a flow diagram showing an exemplary add filter routine for adding a filter to a virtual address in a virtual address bar;

FIGURE 51A is a block diagram of an exemplary graphical user interface for a shell browser having a change control in accordance with an embodiment of the present invention;

ITEM 51B is a block diagram of an exemplary graphical user interface for a shell browser having one or more change controls in accordance with an embodiment of the present invention;

FIGURE 52 is a schematic diagram of a shell browser welcome screen;

ITEM 53 is a schematic diagram of the selected screen in the shell browser;

ITEM 54 is a schematic diagram of a selected screen of ITEM 53 that includes a context menu that allows a user to change metadata in a shell browser in accordance with an embodiment of the present invention;

ITEM 55 is a flow diagram illustrating a method for enabling a user to modify metadata displayed on a welcome screen within a shell browser in accordance with an embodiment of the present invention;

ITEM 56 is a flow diagram illustrating a method for enabling a user to modify metadata displayed on a selection screen within a shell browser in accordance with an embodiment of the present invention;

ITEM 57 is a block diagram of a data structure containing user-modifiable metadata associated with an object displayed in a shell browser;

FIGURE 58 is a schematic diagram of a prior art graphical user interface for viewing images stored in a folder within a shell browser environment used to view other non-image files and folders;

FIGURE 59 is a block diagram of an exemplary graphical user interface for a shell browser;

FIGURE 60 is a schematic diagram of a shell browser welcome screen;

ITEM 61 is a schematic diagram of the selected screen in the shell browser;

FIGURE 62 is a schematic diagram of a selected screen in a shell browser with extended controls in accordance with an embodiment of the present invention;

ITEM 63 is a schematic diagram of a select screen similar to that of ITEM 61 but including a context menu that allows the user to select a preview in a shell browser in accordance with an embodiment of the present invention;

ITEM 64A is a flow diagram illustrating a method for enabling a user to select a preview in a shell browser in accordance with an embodiment of the present invention;

ITEM 64B is a flow diagram illustrating a method for enabling a system to select a preview in a shell browser in accordance with an embodiment of the present invention;

FIGURE 65 is a flowchart illustrating a method of enabling the use of third-party previewers in a shell browser in accordance with an embodiment of the present invention; and

ITEM 66 is a block diagram of a data structure that contains information that references multiple pre-viewers in the shell browser.

A detailed description of the preferred performance

The present invention is directed to a file system shell that includes a number of desirable features. Essentially, the shell provides users with the ability to view and manage files and other items stored on the computer. The following description first summarizes the features shown in PARAGRAPHS 1-66, and then provides a detailed discussion.

In summary, PARAGRAPHS 1-9 are generally directed to the overall virtual folder system. Virtual folders provide a method to allow a common user interface to expose regular files and folders (also known as directories) to users in different views based on their metadata rather than the actual physical background structure of the file system on disk. Items 10-18 are generally focused on stacks, which are related to the ability of virtual folders to take any property stored in the database and represent it as a folder-like container. CLAUSES 19-21 are generally directed to direct management of virtual folders, which refers to providing mechanisms for managing virtual folders that are similar to the mechanisms currently used for managing standard folders (eg, copy, paste, click and drag, etc.). PARAGRAPHS 22-29 are generally focused on filters, which provide a set of tools for narrowing down a set of files/items. PARAGRAPHS 30-43 are generally directed to quicklinks, which are a set of pre-defined clickable links to create useful views of sets of files/items. CLAUSES 35-36 are generally directed to libraries, which refer to the concept that groups of usable file types can be linked together, and that tools and actions associated with specific object types can be provided. PARAGRAPHS 37-38 are generally directed to scope related to the concept that it is possible to obtain files/items from multiple locations (eg, different hard drives, different computers, from a computer in a network location, etc.) so that the user has all the files /items displayed with equal comfort as if provided from a single location. PARAGRAPHS 39-40 are generally directed to items other than files, which may be included in the database along with files, and which may include items such as e-mail messages and contacts. SECTIONS 41-50 are generally directed to a virtual address bar composed of a plurality of segments, each segment corresponding to a content selection filter. CLAUSES 51-57 are generally directed to a shell browser, whereby a user can readily identify an object based on the metadata associated with that object. CLAUSES 58-66 are generally directed to extending the functionality of an object previewer in a shell browser configured to display a plurality of objects representing a plurality of object types. The following description provides a detailed discussion of each of these aspects of the invention.

As noted above, CLAUSES 1-9 are generally directed to a system for performing virtual maps. Virtual folders use the same or similar user interfaces to those currently used for file systems. Virtual folders expose regular files and folders (also known as directories) to users in different views based on their metadata instead of the actual physical background structure of the file system on disk. Location-independent views are created that allow users to manage their files and folders using similar controls to those currently used to manage file systems. In general, this means that users can organize and rearrange their files based on the inherent properties of the files themselves, rather than management and organization being performed as a separate part of the system. Virtual folders can display files or items from different physical locations, such as multiple disk drives within the same computer, between multiple computers, or different network locations, so that a single view of files or items can reveal files or items located in different physical locations . In one embodiment, the various objects or files only need to be connected via an IP network to be included.

Virtual folder modeling can also be used for traditionally non-file entities. An application of this is to have a set of user interfaces similar to files and folders (that is, objects and containers) for displaying traditionally non-file entities. One example of such non-file entities would be e-mail messages, while another example would be contact information from a contact database. In this way, virtual folders provide a location-independent, metadata-based view system that works regardless of whether the data being displayed is from files or from non-file entities. Overall, these aspects allow more flexibility by allowing users to manage their files and data, using both common user interface techniques (drag and drop, double-click, etc.) as well as providing rich integration of different data types.

PARAGRAPH 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which virtual maps, and any of the other aspects of the invention described herein, may be implemented. Although not required to do so, the invention will be described in the general context of computer-executable instructions, such as program modules, that are executed on a personal computer. In general, program modules include routines, programs, characters, components, data structures, etc., that perform specific tasks or implement specific abstract data types. As will be appreciated by those skilled in the art, the invention may be applied to other computer system configurations, including handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention can also be applied in distributed computing environments in which tasks are performed on remote processing devices that are connected through a communication network. In distributed computing environments, program modules can reside on both local and remote storage devices.

With reference to PARAGRAPH 1, an exemplary system for carrying out the invention includes a general purpose computing device in the form of a conventional personal computer 20, including a processing unit 21, a system memory 22, and a system bus 23 connecting various parts of the system including a connection of the system memory 22 to the processing 21. The system bus 23 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. System memory includes read-only memory (ROM) 24 and random access memory (RAM) 25. Basic Input/Output System (BIOS) 26, which contains basic routines and helps transfer data between elements within the personal computer 20, such as at system boot, it is stored in ROM 24. The personal computer 20 further includes a hard disk drive 27 for reading from or writing to the hard disk 39, a magnetic disk drive 28 for reading from and writing to a removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disc 31, such as a CD-ROM or other optical media. The hard disk drive 27, the magnetic disk drive 28, and the optical disk drive 30 are connected to the system bus 23 by the hard disk drive interface 32, the magnetic disk drive interface 33, and the optical disk drive interface 34, respectively. The drives and associated computer-readable media provide persistent storage of computer-readable instructions, data structures, program modules, and other data for the personal computer 20. Although the exemplary environment described herein utilizes a hard disk 39, a removable magnetic disk 29, and a removable optical disk 31, Those skilled in the art will appreciate that other types of computer-readable media capable of storing computer-accessible data, such as magnetic tapes, flash memory cards, digital video discs, Bernoulli cartridges, random access memories (RAMs), read-only memories (ROMs), and the like, may also be used in an exemplary operating environment.

A number of program modules may be stored on a hard disk 39, magnetic disk 29, optical disk 31, ROM 24 or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37 and program data 38 The user may enter commands and data into the personal computer 20 through input devices such as a keyboard 40 and a pointing device 42. Other input devices (not shown) may include a microphone, joystick, game controller, satellite dish, scanner, or alike. These and other input devices are often connected to the processing unit 21 through a serial input interface 46 which is connected to the system bus 23, but may also be connected using other interfaces, such as a parallel input, a joystick input, or a universal serial bus. (USB). A display in the form of a monitor 47 is also connected to the system bus 23 via an interface, such as a video card or adapter 48. One or more speakers 57 may also be connected to the system bus 23 via an interface, such as an audio adapter 56. In addition to the screen and speakers, personal computers typically include other peripheral output devices (not shown), such as printers.

Personal computer 20 may operate in a network environment using logical connections to one or more personal computers, such as remote computer 49. Remote computer 49 may be another personal computer, server, router, network PC, peer device, or other common network node. , and typically includes many or all of the elements described above with respect to the personal computer 20. The logical connections shown in ITEM 1 include a local area network (LAN) 51 and a wide area network (WAN) 52. Such network environments are common in offices, computer networks around company, intranet, and Internet.

When used in a LAN network environment, the personal computer 20 is connected to a local area network 51 through a network interface or adapter 53. When used in a WAN network environment, the personal computer 20 typically includes a modem 54 or some other means of establishing communication over a wide area network 52 , such as the Internet. Modem 54, which may be internal or external, is connected to system bus 23 via serial port interface 46. In a network environment, the program module described with respect to personal computer 20 or portions thereof may be stored on remote memory storage devices. It should be kept in mind that the network connections shown are examples, and other ways of establishing a communication link between computers can also be used.

As implemented on a system of the type illustrated in SECTION 1, the present invention utilizes virtual folders that facilitate the basic tasks of file management and folder navigation (browsing) for users and that provide a higher level of storage capabilities that may be included in new features. Virtual folders expose files and objects to users in different views based on their metadata instead of the actual physical background structure of the file system on disk.

SECTION 2 is a block diagram of a virtual map system 200 in accordance with the present invention. As will be described in more detail later, virtual folders allow the user to change the “pivot” that controls how the data is viewed. As an example, a user can view their music as a flat list of all songs, which can be grouped by album. Alternatively, the user can change the view to show only genres or artists or years, etc. The user can tailor the view to show only those items that match the current task. This is made possible by an improved browsing experience that eliminates the need for further navigation through folders (both downward and backward). The same lessons and capabilities apply to modeling other types of data that are not stored as databases. Contacts, for example, can be exposed to the user in this way, giving them familiar interface capabilities, as well as a richer infrastructure for managing them than is provided by a flat address book.

As illustrated in ITEM 2, the virtual folder system 200 includes a folder processing unit 210, a relational database 230, a virtual folder description database 232, a shell other folder component 234, a folder manager component 236, and a shell and view browser component 240 Map processing unit 210 includes a native code management component 212, a driver factory component 214, a property writer component 216, a rowset disassembler component 218, a query builder component 220, an enumerator component 222, and a property factory component 224.

The relational database 230 stores properties about all files in the system. It also stores some items, such as contacts (ie, non-file items), entirely. In general, it stores metadata about file types and the objects they contain. The relational database 230 receives SQL queries from the query builder 220. The relational database 230 also sends SQL rowsets to the rowset parser component 218, with one row per subject column, where the columns are subject properties.

Virtual folder description database 232 includes virtual folder descriptions. The virtual folder description database 232 sends data to the query builder component 220, including a list of types to display in the folder, an initial filter, and physical locations from which to display results (ranges).

With respect to the other shell folder component 234, the folder processing unit 210 delegates to existing shell folders of many object types, including all files, for controls or properties. The other shell folder component 234 sends properties from the other folders to the property factory 224. The other shell folder component also sends controllers to the controller factory 214.

The folder manager component 236 provides code behavior for objects that exist only in the database, such as contacts. This is what allows non-file objects to behave like files. The map manager component 236 sends the managers to the manager factory 214 .

For the native code management component 212, the map processing unit 210 directly applies certain managers based on object properties. The native code management component 212 sends controls to the controller factory 214. For the native code management component 212 and the folder manager component 236, as well as for all namespaces, virtual folders must provide a set of controls (context menu, icon, thumbnail, info entry, . . .) for their subjects. For most of these (info entry, data object, drag and drop handler, background context menu . . .) the virtual folder provides a common (native) handler for all the types it contains. However, there are others that the type author must provide (a context menu on the object itself, a writeable property storage, . . .). The default controller can also be bypassed. Virtual folders again exploit this for files and allow non-file objects to do the same.

The handler factory 214 takes ID lists and produces code behaviors that provide context menus, icons, etc. In general, the map processing unit 210 can use native handlers, external handlers, or delegate to other shell handlers to obtain handlers, as described above with respect to to the native code management component 212, the other shell folder component 234, and the folder manager component 236. The driver factory component 214 sends drivers to the shell browser in the view 240, as requested by the view. The driver factory component 214 sends the property manager to the property writer 216 .

The property writer 216 converts user intents such as cut, copy, and paste into property rights on a file or object. The shell and view browser component 240 sends data to the property writer 216, including direct manipulation (cut/copy/paste) or modification of metadata. In general, since virtual folders represent an organization based on object properties, operations such as move and copy (moveC1-drop) become changes to those properties. For example, moving a document, in a view sorted by author, from Author 1 to Author 2 means changing the author. The property writer component 216 accomplishes this function.

The rowset parser 218 takes the database rowsets and stores the properties of all objects in the ID list structure of the shell. The rowset takes a virtual folder definition that refers to a particular object and builds an SQL string that can then be passed to the database. Rowset disassembler component 218 sends ID lists to enumerator component 222. As described above, rowset disassembler component 218 also receives data from relational database 230, including SQL rowsets, with one row per subject, the columns being properties of the subject.

The query builder component 220 builds SQL queries. The query builder component 220 receives data from the enumerator component 222, including new filters from the navigation. The query builder component 220 also receives data from the virtual folder description database 232, including a list of types to display in the folder, a filter, and physical locations from which to display results (ranges). The query builder component 220 sends SQL queries to the relational database 230 .

Generally, the query builder component 220 includes sets of rows (in other words, a table). This is what the execution of the query results in. The rowset parser component 218 takes each row and, using the column names, converts the row into an ID list. An ID list is a well-known shell structure used to reference objects in a namespace. Doing this allows virtual folders to be just like any other namespace to the rest of the shell. Also, caching this data helps keep database access, which can be very expensive, to a minimum.

The enumerator component 222 operates in response to navigation to a virtual folder. As described above, the enumerator component 222 receives ID lists from the rowset disassembler component 218, and sends new filters from the navigation to the query builder component 220. The enumerator 222 also sends data to the shell and view browser components 240, including the ID lists returned to would be inserted into the view after navigation.

The property factory component 224 takes ID lists and property identifiers and returns values for those properties. The property factory component 224 receives data from the manager factory component 214 including the property manager. As described above, the properties factory component 224 also receives data from the shell's other folders component 234, including properties from other folders. The property factory component 224 also sends data to the shell and view browser components 240 , including object properties, as requested by the view.

The shell and view browser component 240 displays the contents of a folder in a window, and handles all user interactions with displayed files or objects, such as clicking, dragging, and navigating. In this way, the shell and view browser component 240 receives the user's actions. The shell and view browser component 240 also obtains data related to the code behaviors it needs from the map, in this case the map processing unit 210 .

As described above, virtual folders expose ordinary files and folders (also known as directories) to users in different views based on their metadata rather than based on the actual physical background structure of the file system on disk. In this way, the system is able to take a property that is stored in the database and display it as a folder-like container. Given that users are already familiar with working with folders, displaying virtual folders in a similar way allows users to adapt to the new system more quickly.

FIGURE 3 is a flow diagram illustrating a routine 300 by which a user provides a query that draws back selected objects. At block 302, the map processing unit receives a request from the user. In block 304, the map processing unit submits the query to the relational database. At block 306, the relational database provides the results back to the map processing unit. At block 308, the map processing unit provides results to the user in the form of virtual maps and items.

SECTION 4 is a flow diagram illustrating a routine 320 by which virtual maps are constructed and displayed on the screen in accordance with either a default query or a user query. At block 322, when the user first opens the virtual folder, the default query is used. This default query is taken from the registry. For example, a default query for a music library might be to show all songs grouped by album. At block 324, the map processing unit constructs a query object for this query, and then forwards this query to the relational database. At block 326, the relational database creates the query results and passes them back to the map processing unit as database rows and columns.

At block 328, the map processing unit takes these results and converts them from rows and columns of data into an enumerator structure, which is used by the map view to populate the screen with the resulting virtual maps and objects for the user to interact with. At decision block 330, the user decides whether to change the view (by issuing a different prompt or “pivot”). For example, the user can specify the pivot “show all artists”. If the user wishes to change the view, then the routine returns to block 324 where the map processing unit forwards this new query to the relational database, and receives back new rows and columns of results and builds a new enumerator structure. The process then continues as described above, as the map view is cleaned and rebuilt, using the enumerator to draw the “artist” objects to the screen.

In one example, album objects are provided that represent containers that users can navigate to. For example, double-clicking on the “Beatles” albums will navigate the view to see all Beatles songs. The map processing unit issues a “show all Beatles songs” query to the relational database, which returns rows and columns of data for those songs. The map processing unit creates an enumerator of all these tracks, which are then plotted on the screen.

The user can also select a view at any time while browsing the virtual folders. From the example above, after narrowing down to show only Beatles songs, the user can change the view to show only songs as albums. The process of changing the view of an object to another representation is called "stacking". This is because objects are conceptually arranged into "stacks" based on these representations. In this case, the songs are rearranged into stacks for each of the different albums. Users can then navigate to one of those stacks and view only songs from that particular album. Again, the rooter can rearrange the view of those remaining tracks into stacks based on a property (eg, rating, for example). When the rating property was selected, songs from that Beatles album would be displayed in stacks with one, two, or three star ratings.

The results of each query depend on which physical locations are included in the scope. For example, the scope can be made to include only folders in the user's “my documents” folder. Alternatively, the scope could include all folders on a computer, or even all folders on several networked computers. The user is able to view and change the scope through the scope properties page. In one example, a scope's properties page can be revealed by right-clicking on a virtual folder and selecting “properties”. The user could add new folders to the scope, or remove folders that were previously added.

One group of users for whom virtual folders will provide special functionality are knowledge workers. Virtual folders allow knowledge workers to easily switch between viewing documents by file type, project, case number, author, etc. Since knowledge workers all tend to have different methods for organizing documents, virtual folders can be used to provide these different tendencies.

PARAGRAPH 5 is a tree diagram of the folder structure in accordance with the physical arrangement of folders on the hard disk. The physical arrangement of folders is based on the traditional folder design, which can be based on NTFS or some other existing file system. We call these folders physical folders because their structure is based on the actual physical background structure of the file system on the disk. As will be described in more detail later, this contrasts with virtual folders, which create location-independent views that allow the user to manage files and folders in ways similar to those currently used to manage physical folders.

As illustrated in ITEM 5, folder 400 is a “my documents” folder. At the first level, folder 400 includes folders 410, 420, and 430, corresponding to Clients 1, 2, and 3, respectively. At the second level, each of the folders 410, 420, and 430 contains a folder 411, 421, and 431, respectively, each corresponding to the contracts for the selected client. At the third level, folders 411, 421, and 431 each contain folders 412, 422, and 432, respectively, all of which correspond to the year 2001. At the third level, folders 411, 421, and 431 also each contain folders 413, 423, and 433, respectively. , where each corresponds to the year 2002.

It is easy to see that there are a number of obstacles for a user who wants to navigate through the file structure of physical folders as illustrated in ITEM 5. For example, if a user wants to work with all user-generated contracts, the user will first have to navigate to the folder 411 to work with the contracts of Client 1, and then he will have to navigate again to folder 421 to get to the contracts for Client 2, and he will have to navigate again to folder 431 for the contracts of Client 3. This arrangement makes it difficult for the user to access all the contracts, and in general prevents simultaneous viewing and management of all contracts. Similarly, if the user wants to see all contracts produced in 2001, the user will have to navigate and re-navigate to folders 412, 422 and 432, respectively. As will be described in more detail later, the virtual folders of the present invention provide an improved file system structure.

PARAGRAPH 6 is a tree diagram of the structure of virtual folders. As will be described in more detail later, virtual folders create location-independent views that allow users to manage their files and folders in appropriate ways. As shown in ITEM 6, virtual folders are represented as stacks. Virtual folder 500 is an “all subjects” folder. At the first level, virtual folder 500 contains virtual folders 510, 520, and 530, corresponding to clients, contracts, and year, respectively. As will be described in more detail later, this structure allows the user to access files according to the desired parameter.

ITEM 7 is a tree diagram of the structure of virtual folders from ITEM 6, wherein at the second level, virtual folder 510 further includes virtual folders 511 and 512, corresponding to contracts and year, respectively. In other words, the virtual folder client stack 510 is further filtered by contract and year. The process for determining which files and items are contained in each of the virtual folders will be described in more detail later.

ITEM 8 is a tree diagram of the virtual folder structure of ITEM 7, wherein at the third level, virtual folder 511 contains virtual folder 513, which corresponds to the year. In other words, the contract stack from virtual folder 511 is further filtered by year. Although the virtual folder structures for virtual folders 510, 511 and 513 were structured according to clients, contracts and year, it should be noted that virtual folders allow other structural sequences to appear, as will be described in more detail later, with reference to PARAGRAPH 9.

ITEM 9 is a tree diagram of the virtual folder structure from ITEM 6, where at the second level, virtual folder 520 has been further filtered into virtual folders 521 and 522, corresponding to clients and year. At the third level, virtual folder 521 was further filtered into virtual folder 523, which corresponds to the year. The contrast between the organizational structures of PARAGRAPHS 8 and 9 helps illustrate the flexibility of the virtual folder system. In other words, in a virtual folder system, the user is able to navigate through virtual folders according to desired parameters, as opposed to being dependent on location-dependent views of the physical file structure as illustrated in SECTION 5.

FIGURE 10 is a diagram illustrating a screen view 600 showing document library stacks. As noted above, stacks can be used to represent a type of virtual folder. As will be explained in more detail below, display screen 600 includes quick link elements 610-613, filter elements 620-626, activity elements 630-633, information and control elements 640-645, and virtual map stacks 651-655.

Quick link elements include an “all categories” quick link 610, an “all authors” quick link 611, a “January job” quick link 612, and an option to display additional quick links 613. As will be described in more detail later, quick links can be selected by the user in order to perform the desired navigation of virtual maps. Quick links may be provided by the system, and some quick links may be created and stored by the user.

Filter elements include a “filter by” indicator 620 , an input field 621 , a “by date” indicator 622 , a “year” menu 623 , a “select author” menu 624 , a “select category” menu 625 , and a “more filters” menu 626 . The “filter by” indicator 620 alerts the user to the fact that the items listed below can be used to filter virtual folders or items. An input field 621 provides an area where the user can type the desired new filtering condition. The "by date" indicator 622 points the user to the fact that by selecting a date from the "year" menu 623, virtual folders or items can be filtered by the selected year. The “select author” menu 624 allows the user to filter by a specific author. The "select category" menu 625 allows the user to filter according to the selected category. The “more filters” menu 626 allows the user to call up additional filters on the screen.

Activity menus include a “create new category” menu 630, “activity” menus 631 and 632, and “more activities” menu 633. As will be described in more detail later, the activities presented may be for generally desirable functions, or may even more precisely be directed to activities useful for the type of virtual maps currently displayed. For example, the “create new category” menu 630 may be selected by the user to create a new category to be represented by the new stack.

As noted above, activity menus 631 and 632 may be more specifically directed to the type of maps or items being displayed. For example, the current view is a view of a document library, for which “activity” menus 631 and 632 may be directed to activities tailored specifically for documents, such as modifying or creating attachments. If the current library was a photo library, the “activities” menu 631 and 632 could be for activities specifically focused on photos, such as creating photo albums or sharing photos with other users.

Information and control elements include information lines 640 and 641, control line 642, return control 643, and information lines 644 and 645. Information lines 640 and 641 provide information about current navigation through virtual folders or items. In the present example, information line 640 indicates that the current navigation state is a document library, while information line 641 indicates a more complete navigation, indicating that the document library is within the storage area. Control line 642 provides several standard controls, and back button 643 allows the user to return through the navigation. Information line 644 provides numerical information about the content of the current navigation. In the present example, information line 644 indicates that there are 41 objects and that they occupy 100 MB in the document library stacks. Information line 645 is available to provide additional information, such as additional information about the file that is selected.

Document library stacks include “ABC Corp.” stack 651, “backups” stack 652, “business plans” stack 653, “XYZ Corp.” stack 654, and “marketing reports” stack 655. The numbers at the top of each stack indicate how many items are in each stack. For example, "ABC Corp." stack 651 is shown to include 8 items. The total number of items in the stacks added up gives the number of items indicated in information line 644, which in this example is 41 as described earlier. A SB selection box is provided which can be used by the user to select the desired subject. Selecting "ABC Corp." therefore 651 provides a view of items from that stack, as will be described later with respect to PARAGRAPH 11.

ITEM 11 is a diagram illustrating a display of a screen that displays objects in “ABC Corp.” stack 651 from PARAGRAPH 10. It should be noted that information lines 640 and 641 now indicate that the current navigation shows “ABC Corp.” stack. "ABC Corp." stack 651 is shown to contain 8 documents 751-758, corresponding to documents 1-8, respectively. Information line 644 accordingly indicates that there are 8 objects occupying 20 MB of memory. Documents from ITEM 11 may further be organized into stacks within ABC Corp. therefore. In other words, within the virtual folder presented by ABC Corp. thus 651, additional virtual folders may be organized to contain documents, as will be described later with respect to ITEM 12-16.

ITEM 12 is a diagram illustrating a display screen in which the document stacking function of ITEM 11 is selected. As shown in ITEM 12, the user is able to invoke function box 760. Function box 760 includes selecting “view” 761, selecting “ edit icons by” 762, select “stacks” 763, select “refresh” 764, select “open containing folders” 765, select “cut” 766, select “copy” 767, select “undo” 768, select “new” 769, and the “properties” selection 770. The SB selection box is displayed so that it surrounds the “stacks” selection 763.

ITEM 13 is a diagram illustrating a display of a screen in which the “stack by author” parameter is selected for the stacking function of ITEM 12. As shown in ITEM 13, a frame 780 representing a range of stacking options is displayed. The stacking options include the “unstack” option 781, the “stack by category” option 782, the “stack by author” option 783, and the “stack by user” option 784. A selection box is displayed so it is around the option "stack by author" 783.

ITEM 14 is a diagram illustrating a screen view in which the files from ITEM 13 are stacked by author. As shown in ITEM 14, stacks 791 and 792 correspond to authors Bob and Lisa, respectively. As indicated by the numbers at the top of each stack, the Bob 791 stack includes two items, while the Lisa 792 stack includes five items. Item 758 (corresponding to document 8) had no author and is therefore not included in the "author" stack. Stacks 791 and 792 illustrate the fact that stacks can be organized at multiple levels, such as within “ABC Corp.” therefore 651. In this way, virtual folders can be formed at multiple levels, such as the “Lisa” stack 792 located within “ABC Corp.” therefore 651 located within the document library.

NUMBER 15 is a diagram illustrating a display screen in which the “stack by category” option is further selected to restack the files from NUMBER 14. As shown in NUMBER 15, the SB selection box is located around the “stack by category” option 782. Since some items have already been placed on stacks 791 and 792, selecting the “stack by category” option 782 will re-stack the items, as will be described in more detail later with respect to ITEM 16.

ITEM 16 is a diagram illustrating a display screen in which the files from ITEM 14 are re-stacked by category. As shown in ITEM 16, stacks 793 and 794 correspond to the categories “XYZ Corp.” and “marketing reports”, respectively. Items 751 and 752, which correspond to documents 1 and 2, were not designed for any additional categories and therefore did not fall under any of the other category stacks.

NUMBER 17 is a diagram illustrating a screen view in which a quick link for physical folders is selected. The SB selection box is shown to be located around the “all folders” quick link 616. As will be described later in more detail with respect to SECTION 18, the “all folders” quick link 616 provides the ability to switch to the physical folders view.

FIGURE 18 is a diagram illustrating a display of a screen showing physical folders. The physical folders shown contain the virtual folder stack files of ITEM 17. In other words, the items contained within stacks 651-655 of ITEM 17 are also contained in certain physical folders in the system. These are shown in ITEM 18 as the “My Documents” folder 851 located on the current computer, the “Desktop” folder 852 located on the current computer, the “Foo” folder 853 located on the C: hard drive, the “My Files” 854 which is located on the server, the “External Device” folder 855 which is located on the external device, the “My Documents” folder 856 which is located on another computer, and the “Desktop” folder 857 which is located on another computer.

As shown in ITEM 18, the user is able to switch between displaying the virtual files of ITEM 17 to displaying the physical files of ITEM 18. This allows the user to switch between displaying the virtual files and displaying the physical files, depending on what is desired for the current task. . The different locations of physical folders 851-857 also illustrate that the scope of a virtual file system can be relatively wide, as will be described in more detail later.

FIGURE 19 is a flow diagram illustrating a routine 880 by which a user can directly manipulate virtual folders. As will be described in more detail later, the mechanisms provided for managing virtual folders are more similar to those currently used for managing regular folders (eg, click and drag, copy, paste, etc.). As shown in ITEM 19, at block 882, the system provides defined actions that the user can perform to directly control the virtual folders that are displayed as objects on the screen. At block 884, the user performs the defined action. As noted earlier, one example of this might be a user clicking and dragging a virtual folder to copy its contents to another virtual folder. At block 886, the virtual folder and/or content is managed as determined by the action taken by the user.

ITEM 20 is a diagram illustrating a screen view in which the West Coast 656 stack has been added to the stacks of ITEM 10. The West Coast 656 stack has been formatted so that the user has created a new category “West Coast.” Immediately after creation, the new West Coast 656 stack would be empty and have zero items. In the performance of ITEM 20, two items were added to the stack West Coast 656. One method of adding items to the stack is to select a specific item, and either change or add additional categories to the category metadata for that item, such as adding a category "West Coast" of two items, which was done in the implementation of ITEM 20. This process illustrates the fact that the category data is a metadata property for the item, which is a type of ad-hoc property. In other words, a property of this type has no implicit meaning and can be given an arbitrary value by the user. For example, the “category” property can have any value while the “author” property should be a person's name. As will be described in more detail later with respect to PARAGRAPH 21, items can also be clicked and dragged to be copied from other stacks to the West Coast 656 stack (in which case the categories of those items are automatically refreshed to include “West Coast"). In this sense, PARAGRAPH 20 shows that the SB selection box is around ABC Corp. therefore 651, as a preparation for withdrawing its contents.

FIGURE 21 is a diagram illustrating a screen display in which direct control was used to copy files from ABC Corp. therefore 651 in West Coast stack 656. In other words, as shown in ITEM 20, the user selected ABC Corp. item 651, and then, as shown in ITEM 21, the user clicked and dragged the stack to copy it to the West Coast stack 656. Thus, the West Coast stack 656, which had two items in ITEM 20, is now shown to include a total of ten cases, including an additional eight cases from ABC Corp. therefore 651. When cases from ABC Corp. therefore 651 were copied into West Coast stack 656, this was done by changing the category descriptions for the eight items to also include the “West Coast” category in addition to the “ABC Corp.” category. which they originally included. This illustrates one type of direct management that can be done.

Another example of direct control is right-clicking on an item and selecting delete. In one embodiment, when the user selects the delete function, the user is asked if the item should be completely deleted, or if it should simply be removed from the current virtual folder. If the item just needs to be removed from the current stack of virtual folder categories as noted above, this can be done by removing the desired category from the metadata for the item. In other words, if one of the items that were copied from ABC Corp. therefore 651 in the West Coast stack 656 should then be removed from the West Coast 656 stack, this can be done by changing the category data for that particular file to no longer include the category “West Coast”.

FIGURE 22 is a flow diagram illustrating routine 900 for a system that dynamically creates new filtering conditions. Filtering conditions are used to manage virtual folders. Filtering conditions are basically used as a set of tools to narrow down the set of items. In one embodiment, the filters consist of metadata categories and their values (displayed to the user in the user interface as selectable links or drop-down menus). The user selects a filter condition by clicking to filter the current set of subject results on the screen.

PARAGRAPH 22 illustrates how filters can be dynamically created. As shown in ITEM 22, at block 902, the properties (from metadata) of the items in the set on the current screen are considered. In block 904, suggested filtering conditions are dynamically created based on shared object properties. At block 906, suggested filter conditions are displayed to the user for possible filter condition selection. As an example of this process, the system can inspect the properties of a set of items, and if the items generally have "Authors" as a property, the filter can provide a list of filterable authors. Then, by clicking on a certain author, items that do not have that author are removed from the set on the screen. This filtering process provides the user with a mechanism to narrow down the set of items on the screen.

NUMBER 23 is a flow diagram illustrating a routine 920 by which the system filters items based on a selection of filter conditions. At block 922, the user either enters a new filter condition or otherwise selects one of the filter conditions displayed by the system. As noted earlier, filtering conditions can be dynamically created by the system, or they can be predetermined. At block 924, items from the set on the screen are evaluated with respect to whether their selected properties match the filtering condition. For example, if the filtering condition is for items authored by "Bob", then the items are evaluated according to whether their author property includes "Bob". At block 926, items for which the selected properties do not match the filtering condition are removed from the display set.

POINTS 24-29 generally illustrate what the filtering process looks like on screen. As will be described later with respect to CLAUSES 24-29, in one embodiment, filtering may generally be performed in accordance with the following procedure. After the user selects the filter value by clicking, objects out of reach are removed from the screen by animation. The animation is generally designed to make it obvious that objects are being removed and that no new objects are being added. The user can select the back button 643 to undo the filtering operations. In one embodiment, a navigation stack containing successive filter actions is created, which is used to cancel each of the filter actions when the back button 643 is selected. Each time a value is selected, the information areas 640 and 641 are refreshed to show the current value filter. In one embodiment, after a filter value is selected, the user is provided with the option to save a new quick link for the current filter navigation, as will be described in more detail later with respect to SECTION 30. When the filter values are selected, the filter controls may be refreshed to be appropriate for items remaining in view.

ITEM 24 is a diagram illustrating a screen display in which the stacks from ITEM 10 are filtered by condition “AB”. As shown, in the filter area 621 the user typed the condition “AB”. Information lines 640 and 641 indicate that the items on the screen are now those that were filtered by condition “AB”. As shown, ABC Corp. stack 651 still contains eight items, while Backups stack 652 now contains three items, and the XYZ Corp. stack. 654 also contains three items. Information line 644 therefore shows that there are a total of 14 objects, occupying a total of 35 MB of memory.

ITEM 25 is a diagram illustrating a display screen in which the stacks from ITEM 10 are filtered by the condition “ABC”. Given the filter condition “AB” from ITEM 24, the user simply typed an additional letter “C” to make the overall filter condition “ABC”. As shown in ITEM 25, information lines 640 and 641 now indicate that the items on the screen are those containing the condition “ABC”. Stock ABC Corp. 651 is still shown as containing eight items, while Backup 652's stack now contains all items. Stack XYZ Corp. 654 has disappeared because none of its contents match the filter “ABC”. Information line 644 now shows that there are a total of 10 items in the stacks on the screen, taking up a total of 25 MB of memory. POINTS 24 and 25 thus provide examples of how the user can enter new filter conditions and how those filter conditions are then used to filter the items that are displayed on the screen.

The user can use the back button 643 to go back through the filtering process. As previously described with respect to PARAGRAPH 10, the back button 643 allows the user to return through the navigation. Referring to the examples of paragraphs 24 and 25, after filtering by the filter condition “ABC” in paragraph 25, the user may select the back button 643 to go back one step in the filtering process, which would return the state of paragraph 24. Alternatively, in in another embodiment, the back button 643 may clear the entire filtering condition and may thus restore the state before that filtering occurred. In this case, by pressing the return button 643 in ITEM 25, the user would return to the state of ITEM 10.

In one embodiment, in addition to the back button, additional means are provided to allow the user to back through or otherwise modify the navigation by filtering. These additional means include allowing the user to directly access and change the information line 641, which changes the filtering navigation accordingly. In other words, by directly accessing and changing the information line 641, the user can terminate one or more applied filters, or change the values for any of the applied filters. This feature is described in much greater detail in US Patent Application No. 10/420,040, filed Apr. 17, 2003, which is generally set forth and hereby incorporated by reference in its entirety.

The timer may also be used in conjunction with user typing filtering conditions such as those shown in CLAUSES 24 and 25. The timer is used to monitor a pause in user typing. After the selected non-typing interval, the filter is applied. For example, in the condition of ITEM 24, the user typed the filtering condition “AB”, with no significant time delay between “A” and “B”. After typing the condition "AB", the user pauses, thereby creating the state shown in ITEM 24, in which the filtering condition "AB" is applied. A little later, the user adds the letter “C” to complete the “ABC” filtering condition, and then pauses again, at which point the “ABC” condition is applied as illustrated in ITEM 25.

In one embodiment, after the user has typed a filter condition into the filter area 621, and then selects another filter or navigation, the navigation state is refreshed, and the filter condition in the filter area 621 appears empty again. Additionally, as will be described in more detail later with respect to CLAUSES 26-29, other filtering controls may be refreshed depending on the selection of certain filtering conditions.

PARAGRAPH 26 is a diagram illustrating a display of the screen in which the filter condition “year 2002” offered by the system is selected. As noted earlier, under the date indicator 622, the year selections include the years 2000, 2001, or 2002. The SB selection box is shown to be around the year 2002, indicating that the user is selecting that as the desired filtering condition.

PARAGRAPH 27 is a diagram illustrating the display of the screen in which the filtering condition "2002" is applied. A further “select month” menu selection 623A is also shown. As shown in ITEM 27, after applying the filtering condition “2002”, the item numbers in the stacks decreased. More precisely, ABC Corp. stack 651 now contains six items, Backups stack 652 now contains eight items, Business Plans stack 653 now contains three items, and the XYZ corp. 654 now contains five items. Information line 644 now shows a total of 22 items, occupying a total of 50 MB of memory. Information lines 640 and 641 now indicate that the items displayed on the screen are those that have been filtered to contain the filter condition “2002”.

NUMBER 28 is a diagram illustrating a display of a screen displaying a month selection list for filtering. Frame 950 is provided which includes a list of months. Frame 950 is displayed on the screen because the user has selected the “select month” menu 623A. The SB selection box is displayed around the month of January.

ITEM 29 is a diagram illustrating the display of the screen where the stacks from ITEM 28 are further filtered by the month of January, and further shows the filtering condition "day". As shown in ITEM 29, information lines 640 and 641 now indicate that the items displayed on the screen are those filtered by the term "January". The Backup stack 652 is now shown as containing two items, while the Business Plans stack 653 is also shown as containing two items. Information line 644 indicates that there are a total of four objects on the screen, occupying a total of 10 MB of memory. A "select by day" menu 623B is provided in case the user wants to filter results by a specific day.

As described earlier with respect to ITEM 24-29, the filtering conditions may be provided by the system, or may be entered by the user. Once a filter condition is selected, the remaining filter conditions that are displayed may be refreshed (eg, after the year “2002” is selected in ITEM 26, the year selection options are no longer displayed in ITEM 27 and are instead provided with the option “select month"). As noted above, the user can select the back button 643 to go back through the filtering process. For example, after the month “January” is selected in ITEM 29, the user may select the back button 643 to return through the filtering process to the year “2002”, as illustrated in ITEM 27. The filter menu may also include a function “stack by”, which would work similarly to the “stack by” function described earlier with respect to ITEM 15 and 16. For example, a “file type” filter could have choices for “Excel”, “PowerPoint”, “ Word” and also “Stack by File Type”. Selecting the “stack by” function changes the view to show stacks for various file fips.

In general, filters can be set to apply to various properties of files or objects. In one embodiment, the filters may be classified according to different types, such as: alphabetical index; discrete values; dates; and numerical ranges. Example properties for an alphabetical index might include file name, author, artist, contact name, owner, document author, document title, document subject, and description. Example properties for discrete values might include location, file type (application name), genre, track, decade (for music), rating (for music), bit rate, whether protected, document category, document page count, document comments, camera model, dimensions, product name, product version, X images, Y images and time of document creation. Example properties for dates might include last accessed, last modified, created, captured (for images). An example of a property for a numeric scope might be file size.

It should be noted that the filters described earlier with respect to ITEM 24-29 allow users to narrow down the list of items to find a specific item of interest. As a specific example, according to the procedure described earlier, the user can narrow down the current list of documents to show only Microsoft Word files, whose auto is a specific person and which have been changed in the last week. This functionality allows the user to find a specific item in a list of many, and helps the user avoid having to manually search for each item in the list.

FIGURE 30 is a flow diagram illustrating routine 940 for creating a new fast link. As will be discussed in more detail later, quick links are predefined links that a user can click to create user-selected views of sets of objects. In one embodiment, a quick link can be considered a type of pivot. Quick links provide a mechanism for retrieving a virtual folder. Clicking on a quick link can take the user to the desired folder (in the same way that clicking on "favorites" can take the user to a Web page). Quick links can be predetermined by the system, or they can be set by the user. For example, clicking on “all authors” might return a view arranged in stacks by author. Clicking on “all documents” can return a flat view for all documents from all storage spaces. Users can also create their own quick links.

As shown in ITEM 30, at block 942, the user makes a selection on the screen to indicate that a new quick link should be created from the current filtering or navigation condition. At block 944, the user provides a new name for the new quick link. At block 946, the new quick link is stored and the new quick link name is provided in the quick link dialog on the screen.

ITEM 31 is a diagram illustrating a screen display for creating a new quick link called “January Job” based on the filtering of ITEM 29. As described earlier, in ITEM 29, the stacks were filtered by the month of January. In item 31, the user marked that the filtering from ITEM 29 should be saved as a new quick link, and named the new quick link "January Job". In this way, the new quick link January poaso 612 is displayed in the quick links section of the screen. With regard to the design of new quick links, the user is generally provided with options such as "save this collection as a quick link".

PARAGRAPH 32 is a diagram illustrating the display of the screen in which the "All Authors" quick link is selected. As shown in ITEM 32, the SB selection box is displayed around the All Authors selection 611. Other examples of collections that can be accessed via quick links include “all authors”, “recent documents”, “all documents I have shared”, all documents of which I am the author", "all documents of which I am not the author", "desktop", and "all types".

ITEM 33 is a diagram illustrating a screen display showing a list of all item authors from ITEM 32. As shown in ITEM 33, information line 950 is provided, indicating columns for displaying item name, author, date modified, type, size and the location of the item. Author lists 951-954 corresponding to Authors 1-4 are shown, respectively.

ITEM 34 is a diagram illustrating a screen display in which “Author 1” is selected from the list in ITEM 33. Author 1's documents include documents 951A and 951B, which correspond to documents 1 and 2, respectively. Document 1 is shown as authored by Author 1, modified on July 11, 2001, a Microsoft Excel file, occupying 282 Kb of memory, and retrieved from the location \\server1\folder2 (\\server1\ map2). Document 951B is shown as being authored by Author 1, modified on December 22, 2002, being a Microsoft Word file, occupying 206 kilobytes of memory, and physically stored at My Documents\folder1. The locations of documents 951A and 951B also illustrate the fact that the virtual folders of the present invention may contain items from different physical locations, as will be described in more detail later.

FIGURE 35 is a flow diagram illustrating routine 960 for creating a new library. One example of a library is the document library described earlier with respect to PARAGRAPH 10. In general, libraries consist of large groups of usable file types that can be linked together. For example, photos can be one library, music can be another, and documents can be a third. Libraries provide tools and activities related to specific subject types. For example, in a photo library, there may be tools and filters related to photo management, such as those for creating image slideshows or sharing images. As shown in ITEM 35, at block 962, a new library is created to include items with the selected characteristics. At block 964, the selected items are grouped into a library. At block 966, tools and/or activities related to selected object characteristics or other desired functions are provided.

ITEM 36 is a diagram illustrating a display of a screen showing a collection of available libraries. As shown in ITEM 36, the libraries include a document library 971, a photo and video library 972, a music library 973, a message library 974, a contact library 975, and a TV and movie library 976, as well as an all-subject library 977. item 977 is shown to include 275 items, which is the total number of items from all other libraries when added together. Information line 644 shows a total of 275 items, which occupy a total of 700 Mb of memory. It should be noted that document library 971 is the library previously described with respect to PARAGRAPH 10.

ITEM 37 is a flow diagram illustrating a routine 990 for determining the extent of a collection of virtual folders. As will be described in more detail later, the virtual folder system is capable of displaying items from multiple physical locations (eg, different hard drives, different computers, different network locations, etc.) so that all of those items are readily available to the user. For example, a user can be shown music files from multiple physical locations on one screen, and can manage all files from one.

As shown in ITEM 37, at block 992, the scope is determined for the physical locations from which the objects are to be displayed. At block 994, in response to the query, objects are drawn from the physical locations as defined by the scope. At block 996, all objects drawn by the query are displayed on one screen.

FIGURE 38 is a block diagram illustrating the various sources that can shape the scope of a collection of virtual folders. As shown in FIGURE 38, system 1000 may include the current computer 1010, additional computer 1020, external and removable storage 1030, and network locations 1040. The overall scope 1001 is described to include all physical locations from which users objects are plotted to create collections. The user can set and change the scope. As mentioned above, other items illustrated the fact that items can come from different physical locations, such as ITEM 34 shows various documents coming from the server and My Documents folders on the current computer, and ITEM 18 shows physical folders that are physically stored on multiple locations.

NUMBER 39 is a flow diagram illustrating a routine 1080 for including non-file objects in a collection of virtual folders. Non-file objects are contrasted with file objects that typically reside in physical file storage space. Examples of non-file items would be things like e-mail messages, or contacts. As shown in ITEM 39, at block 1082 a database is used to include non-file objects along with queryable file objects. At block 1084, in response to the query, both non-file objects and file objects are drawn to match the query. At block 1086, both non-file objects and file objects matching the query are displayed on the screen.

ITEM 40 is a diagram illustrating a display of a screen displaying various non-file items. As shown in ITEM 40, the items are filtered to only those that include “John”. Subjects are shown to include contact subject 1101, e-mail subject 1102, and document subjects 1103 and 1104. Contact subject 1101 and e-mail subject 1102 are non-file subjects. The present system allows such non-file items to be included with ordinary items, so that they can be organized and managed as the user wishes. As previously described with respect to PARAGRAPH 2, such non-file objects may be contained entirely within the relational database 230, which otherwise includes information about file properties.

ITEM 41-50 are diagrams relating to a virtual address bar corresponding to information line 641 of ITEM 10 and which is formed in accordance with the present invention. As will be described in more detail later, the virtual address bar consists of a number of segments, and each segment corresponds to a content selection filter. Collectively, the corresponding filters of each segment represent a virtual address for selecting content.

FIGURE 41 is a block diagram of an exemplary networked computing environment 1200 suitable for implementing a virtual address bar, or any of the other aspects of the invention described herein. An exemplary networked computing environment 1200 includes a computing device 1202, such as a personal computer described with respect to PARAGRAPH 1, for interaction with a user, and on which the user can view files stored either locally or at a remote location relative to the computing device. Although the following discussion describes the present invention in relation to a personal computer, it should be noted that computing device 1202 includes many types of physical devices including, but not limited to, minicomputers and mainframe computers, PDAs, tablet computers, and other devices capable of to interact with the user and display files and content stored on the computing device and elsewhere.

An exemplary networked computing environment 1200 may also include one or more remote servers, such as a server 1204, that stores files accessible to a computing device 1202, and that is connected to the computing device via a communications network, such as the Internet 1206, as shown in SECTION 41. Additionally, computing device 1202 may also be connected to other information sources that store files or other content, such as a remote database 1208. Those skilled in the art will recognize that files and information stored on both remote server 1204 and on the remote database 1208, as well as on local storage devices such as a hard disk drive (PARAGRAPH 1), may be accessible to, and viewable on, the computing device 1202 as part of the embedded file system on the computing device. Additionally, although a particular setting of remote server 1204 and remote database 1208 is shown in ITEM 41, those skilled in the art will readily recognize that this setting is for illustrative purposes only, and should not be considered limiting of the present invention.

FIGURE 42 illustrates an exemplary file browser 1300 having a conventional address bar 1302 associated with displaying files in a computer file system, as may be found in the prior art. For purposes of this discussion, a file viewer is a view or window on a display device, such as a display device (PARAGRAPH 1), for displaying files or other content to a user. A file viewer can be a window that corresponds to an executable program specifically for displaying files to the user. Alternatively, a file browser can be a view within an open or close dialog box on an executable program that needs to save or retrieve data from a storage device connected locally or remotely to the computer system. It should be noted that the above file browser examples are illustrative, and should not be considered limiting of the present invention.

An address in the normal address bar 1302 corresponds to a specific location within the file system. As described earlier, to change the address displayed in the normal address bar 1302, the user must change the address according to specific knowledge of the file system. Alternatively, the user can select an entry in tree view 1304 to navigate to an alternate location. Those skilled in the art will recognize that other controls outside of the address bar 1302 may also be available that are not displayed in the exemplary file view 1300. Although the address displayed in the normal address bar corresponds to a specific location within the file system, related files spread across multiple folders in the file system to the system they cannot be displayed in conjunction with the usual 1302 address bar.

FIGURE 43 illustrates an exemplary file browser 1400 having a virtual address bar 1402 associated with displaying files in a computer file system. Virtual address bar 1402 corresponds to information line 641 of ITEM 10. Virtual address bar 1402, having virtual address 1404, is set up to display similar information to that displayed by conventional address 1304 of the file browser 1300 heretofore known in the art from ITEM 42. Virtual an address, also called a virtual path, references files stored in a computer file system according to selection criteria.

Similar to a normal address, such as address 1304 of SECTION 42, the virtual address selection criteria may reference files stored at a specific location within the file system hierarchy. However, unlike a regular address, virtual address selection criteria can also reference files independent of their specific location within the file system. In this way, a virtual address can reference files stored in multiple locations within the computer's file system. As shown in ITEM 43, the file browser 1400 is capable, according to the virtual address 1404 in the virtual address bar 1402, of displaying additional files, such as files 1406 and 1408, which cannot be found in the file browser 1300 of ITEM 42. Additionally, virtual address bar 1402 may also be used to display content other than files in a computer file system. For example, virtual address bar 1402 may be used to reference content that includes system devices, system services, or Internet locations.

SECTION 44A illustrates the management of virtual address segment 1404 in virtual address bar 1402 for the purpose of navigating a computer file system. Each virtual address bar, such as virtual address bar 1402, consists of one or more interactive segments, such as segments 1502, 1504, 1506, and 1508. Each segment in the virtual address bar corresponds to a predetermined filter, or selection criterion, on all available content or files accessible to the computer file system. Collectively, the filters of all segments in the virtual address bar 1402 represent the virtual address of the virtual address bar.

The first segment in the virtual address bar, such as segment 1502, is called the root segment, or root filter. The root segment represents the broadest category of content available for selection by the virtual address bar 1402. For example, the “Files” segment 1502 would likely represent a filter that references all files accessible to the computer's file system. Alternatively, the root segment may represent a filter that references all system services available to the user on the computer system, or a filter that references all hardware devices embedded in the computer system. Those skilled in the art will recognize that numerous other root filters may be employed by the present invention. Thus, the previously described examples are provided for purposes of illustration and should not be considered limiting of the present invention. Additionally, the names shown for each segment, such as “Files” on the root segment 1502, are illustrative and should not be considered limiting of the present invention. According to one embodiment, the user can customize the name displayed on the segment.

Each additional segment in the virtual address bar 1402, such as segments 1504, 1506, and 1508, represents additional filters to be applied when selecting and displaying files or content in the file browser 1400. For example, the root segment 1502 “Files” references all files available computer system. The “Document Library” segment 1504 filters the files selected by the root segment 1502 , selecting those that have been created as documents by the user, such as with a word processor, spreadsheet, or other application that creates documents. Segment 1506 “Word Documents” filters the files selected by segment 1504 to those documents that were created using a word processing program, such as the Word application from Microsoft Corporation. Finally, segment 1508 “Author A” filters the word processor documents selected by segment 1506 according to whether they are authored by “Author A”. Thus, the content selected according to the virtual address represented in the virtual address bar 1402 must satisfy filters that match all segments in the virtual address bar.

The segments in the virtual address bar 1402 are generally ordered from those filters that include the most content to those that include the least. For example, as discussed earlier, segment 1502 “Files” is the broadest and includes the most content. Segments 1506 “Word documents” and segment 1508 “Author A” are less inclusive. Virtual address bar 1402 illustrates a left-to-right segment order and, for purposes of this discussion, segments 1504, 1506, and 1508 are followers of the root segment 1502. However, it should be noted that other orientations are possible, such as top-to-bottom ordering. , without departing from the scope of this invention. Thus, the left-to-right orientation should be viewed as illustrative and not as limiting of this invention.

As mentioned earlier, segments in virtual address bar 1402, such as segments 1502, 1504, 1506, and 1508, do not necessarily correspond to specific locations in the computer file system, such as folders, drives, and directories. Thus, segment 1504 “Document Library” may reference files or content distributed across multiple servers, drives, or folders/directories. However, certain segments in the virtual address bar 1402 may reference certain locations within the computer file system hierarchy. Further discussion of virtual address segments referencing specific file system locations will be given later with respect to SECTIONS 48A and 48B.

Unlike a regular address bar, each segment in the virtual address bar 1402 represents an interactive, actionable user interface element. For example, a segment in the virtual address bar 1402 is responsive to a user's selection, observes whether the cursor is over the segment for a specified period of time, and can be removed from the virtual address bar by a user's swipe interaction. Therefore, as shown in ITEM 44A, the user can hover over a segment in the virtual address bar 1402, such as the “Document Library” segment 1504, to select, or click, that segment to navigate to that level, ie ., truncation of the virtual address at that segment, as described with respect to PARAGRAPH 44B.

SECTION 44B illustrates the results of selecting segment 1504 in virtual address bar 1402. By clicking on segment 1504 in virtual address bar 1402, the user indicates a desire to navigate to that level in the virtual address. As an effect, the user cut off those filters that followed the selected segment. For example, by clicking segment 1504 “Document Library” (PARAGRAPH 44A), the resulting virtual address 1404 no longer contains segments 1506 “Word Documents” and 1508 “Author A” (PARAGRAPH 44A). Additionally, because the user has navigated to a less restrictive set of filters, the resulting virtual address 1404 in the virtual address bar 1402 includes more content. This is indicated by the addition of documents in the document viewer 1400 of ITEM 44B that were not previously in the document viewer 1400 of ITEM 44A, including document 1512 , document 1514 , and document 1516 , and the presence of a scroll button 1518 indicating that additional files can be viewed which cannot be displayed in the file viewer 1400 (PARAGRAPH 44B) due to space limitations.

In addition to selecting segments in the virtual address bar to navigate to a less restrictive segment, the user may also wish to navigate to, or select, equal-level filters of the current segments in the virtual address. An equal level filter is an alternative filter that can be selected and applied to a given segment in the virtual address bar. For example, with reference to PARAGRAPH 44A, equal-level filters for segment 1506 “Word Documents” may include filters such as “Excel Documents”, “Logs” and the like. Other types of filters, including specific file system locations, hardware devices, or computer services, may also be applied to a given segment in the virtual address bar. Filters of the same level may or may not be logically connected to the current filter of the given segment. Any segment in the virtual address bar can have filters of the same level. Selecting equal-level filters for a segment in the virtual address bar is sometimes called cross-navigation. Selecting an equal level filter for a segment in a virtual address bar will be described later with respect to CLAUSES 45A-45D and also with respect to CLAUSE 49.

ITEM 45A-45D are pictorial diagrams illustrating the selection of an equal level filter associated with a virtual address segment in a virtual address bar 1600. As shown in ITEM 45A, the virtual address bar 1600 has a virtual address consisting of multiple segments, segments 1602- 1608 To select an equal level filter for a given interactive segment in virtual address bar 1600, the user must make an alternate selection, or alternate management, with that interactive segment. One way to make an alternative selection is to right-click on a given segment. Right-click is a term known in this field and refers to the use of a secondary button on a mouse or other input device, where the secondary button is typically on the right side of the mouse. Alternatively, because the interactive segment can observe when the cursor is positioned over it, an alternate selection can be made by placing the cursor over the interactive segment and leaving the cursor in place for a predetermined period of time, sometimes called hovering. However, while this discussion describes alternatives for causing equal level filters to be displayed, they are illustrative, and should not be considered limiting of the present invention. Those skilled in the art will recognize that there are numerous alternatives for creating an alternative selection.

To illustrate alternative segment selection, with respect to SECTION 45A, the user first positions the cursor 1610 over the “Document Library” segment 1604 for a predetermined period of time, i.e., hovers over the segment, to select that segment. ITEM 45B shows the results of the alternative selection of the “Document Library” segment 1604 in the virtual address bar 1600. As shown in ITEM 45B, after the alternative selection of the “Document Library” segment 1604, an equal level filter view 1612 is displayed that includes filters that match the selected segment. It should be noted that equal level filters are presented with respect to equal level filter 1612 for purposes of illustration only and should not be considered limiting of the present invention.

To select an alternative equal-level filter, as shown in ITEM 45C, the user positions the cursor 1610 over one of the filters presented in the equal-level filter view 1612 , such as equal-level filter 1614 , and selects the equal-level filter. As also shown in ITEM 45D, after selecting the alternative equal level filter 1614, the previously selected segment 1604 (ITEM 45A) is replaced by a new segment 1616 representing the selected alternative equal level filter 1614. Additionally, those segments that followed the alternatively selected segment 1604 in virtual address bar 1600 from ITEM 45A, more specifically, segments 1606 “Diaries” and 1608 “All documents in 2002”, are removed from virtual address bar 1600 in ITEM 45D. Although not shown, it follows that any files or content previously selected in accordance with segments 1604 "Document Library", 1606 "Logs" and 1608 "All Documents in 2002." they will no longer be displayed in the corresponding file browser, and only those files or content selected according to segments 1602 “Files” and 1616 “Image Library” will be displayed.

Segments can be added to a virtual address in the virtual address bar through various user interactions at the end of existing segments. To add a filter to a virtual address in the virtual address bar, the user can manage the control associated with the specific filter found in the window, or file browser with the virtual address bar. For example, with reference to the file browser 1400 of ITEM 43, the user may click on the manageable control 1412 “2003.” to add the appropriate filter to the virtual address 1404 in the virtual address bar 1402. Alternatively (not shown), the user can manually enter a known filter at the end of the virtual address by typing the name of the filter. There are numerous other ways of adding a filter to a virtual address, all of which are considered to be within the scope of this invention. Thus, it should be understood that the above examples are for illustrative purposes only and should not be considered limiting of the present invention.

When a filter is added to a virtual address in the virtual address bar, a process is performed to ensure that the newly added filter does not conflict with any of the filters that currently exist as part of the virtual address. If the newly added filter conflicts with the existing filter, the existing filter is removed. A newly added filter conflicts with an existing filter in the virtual address if the newly added filter differs from the scope of the existing filter, so that it is more or less wide than the existing filter. Additionally, a newly added filter conflicts with an existing filter if the newly added filter is mutually exclusive with the existing filter. However, a newly added filter that is identical to an existing filter is not added because it has no effect. It should be noted that the above description of conflicts is provided for purposes of illustration only and should not be considered limiting of the present invention. Those skilled in the art will recognize that there may be other conflicts between filters, all of which are considered to be within the scope of this invention.

NUMBERS 46A-46D are pictorial diagrams illustrating adding a filter to virtual address 1702 in virtual address bar 1700, and removing conflicting existing filters. ITEM 46A illustrates an exemplary virtual address 1702 displayed in virtual address bar 1700. As shown in ITEM 46B, a new filter, represented by segment 1706 “2002,” is added to virtual address 1702. As previously described, the new filters appended to the end of the virtual address, as shown by the placement of segment 1706 "2002." at the end of the segments in the virtual address bar 1700 from ITEM 46B. From then on, the process undertaken to add segment 1706 "2002." determines that the added filter does not conflict with any existing filters in virtual address 1702. Thus, no existing filters are removed from virtual address 1702.

As shown in ITEM 46C, another filter is added to virtual address 1702, represented by segment 1708 “Author A”. The process undertaken to add this new filter determines that the new filter, “Author A”, would conflict with the filter represented by segment 1704 “Author A-F” because the new filter, “Author A”, is narrower than the existing filter. Accordingly, the segment 1704 “Author A-F” is removed from the virtual address bar 1700 and the segment 1708 “Author A” is added to the end of the segments in the virtual address bar.

PARAGRAPH 46D illustrates the result of adding segment 1710 “2003.” into virtual address bar 1700 from ITEM 46C. Filters in virtual address 1702 are restrictive, not additive. Each filter further limits the selected content. Thus, mutually exclusive filters would prevent virtual address 1702 from selecting any files or content, and therefore create a conflict. As illustrated in ITEM 46D, segment 1706 “2002.” (PARAGRAPH 46C) is removed from the virtual address bar 1700 due to a conflict because it is mutually exclusive with the newly added segment 1710 “2003”.

When the virtual address bar, such as the virtual address bar 1800 (PARAGRAPH 47A), cannot fully display the virtual address due to the size limitation of the virtual address bar, a portion of the virtual address is displayed according to the size of the virtual address bar. However, the user can still access the undisplayed parts of the virtual address. More specifically, the virtual address bar displays usable visual indicators for navigating the virtual path within the virtual address bar. NUMBERS 47A and 47B illustrate an exemplary virtual address bar 1800 displaying a virtual address where the virtual address exceeds the display capacity of the virtual address bar. As shown in ITEM 47A and 47B, the scroll icons 1802 and 1804 indicate the direction in which the virtual address bar 1800 can be scrolled to display previously undisplayed portions of the virtual address. However, although the illustrative diagrams show the use of scrolling icons, this is for illustrative purposes only and should not be considered limiting of the present invention. Those skilled in the art will recognize that there are numerous other ways of moving the virtual address in the virtual address bar, all of which are considered to be within the scope of the present invention.

FIGURE 48A is a block diagram illustrating a virtual address bar 1900 having segments that reference both virtual and physical locations within the file system. As discussed earlier, a virtual address in a virtual address bar may contain segments that reference specific locations within the computer file system hierarchy, and also contain segments that reference virtual, or logical, locations within the computer file system. The files or content referenced by a virtual segment can be spread across many physical locations. Virtual address bar 1900 may contain segments that reference physical locations and segments that reference virtual locations. For example, the virtual address bar includes a segment 1902 “Local Disk (C:)” that refers to files or content contained in a specific area in the computer's file system, specifically, drive “C.” Alternatively, segment 1904 “Case files” per se refers to files or content stored in multiple folders within a computer file system hierarchy associated with case files. However, in combination with segment 1902 “Local Drive (C:)”, segment 1904 “Case Files references only those case files located on local drive “C.” Additionally, segment 1904 “Contains ‘Fax’” further filters files on local drive C: associated with case files for whether they contain the word “Fax.”

As shown in ITEM 48B, the virtual address bar 1900 can be adapted to function like a normal address bar. For example, with reference to SECTION 48A, by placing the cursor 1908 in an empty space of the virtual address bar 1900 and clicking there, the virtual address bar is switched from displaying segments representing the virtual address to functioning as a normal address bar displaying a normal address 1910, as which is shown in ITEM 48B. The common address 1910 in the virtual address bar 1900 of ITEM 48B approximates the virtual address shown in the virtual address bar 1900 of ITEM 48A. However, those filters from the virtual address bar 1900 of ITEM 48A that do not correspond to physical locations in the computer file system cannot be displayed and are removed from the normal address 1910. More specifically, segment 1904 “Case Files” and segment 1906 “Contains 'Fax'” are not part of the usual address 1910 (PARAGRAPH 48B).

In order to readjust the virtual address bar 1900, which functions as a normal address bar, to normal operation as a virtual address bar, the user must indicate this intention in some way other than clicking on an empty space of the bar. When set to function like a regular address bar, the virtual address bar must allow the user to click in an empty area to change the address. Clicking in an empty area of the normal address bar places the edit cursor at the end of the address/path for editing purposes. Accordingly, to re-adjust the virtual address bar for normal mode as described earlier, the user must press a predetermined key or key sequence, such as the Esc or Tab keys, or must place the focus on another area of the window or view by clicking on another area of the window or view. Those skilled in the art will recognize that other user actions may also be used to readjust the virtual address bar 1900 to function again in its normal manner as previously described, and all such actions are considered to be within the scope of the present invention. .

NUMBER 49 is a flow diagram illustrating a peer filter selection routine 2000 for selecting a peer filter for the indicated segment in the virtual address lane. Beginning at block 2002, routine 2000 detects initiation of equal level filter selection. The initiation of the equal level filter selection process is described earlier with respect to ITEM 45A-45D. At block 2004, the segment for which equal level filter selection is requested is detected. At block 2006, equal level filters are determined for the detected segment from a predetermined list of equal level filters. With block 2008, equal level filters are displayed to the user. At block 2010, the user's selection of an equal level filter among the displayed equal level filters is obtained. At block 2012, the virtual address is trimmed by removing the indicated segment from the virtual address bar and any additional segments that follow the indicated segment. At block 2014, the segment representing the selected equal search filter is added to the remaining segments in the virtual address bar. After that, routine 2000 ends its work.

ITEM 50 is a flow diagram illustrating an exemplary add filter routine 2100 for adding a filter to a virtual address in a virtual address bar. Beginning at block 2102, the exemplary routine 2100 obtains a filter to be added to the virtual address. For example, as discussed earlier with respect to PARAGRAPH 43, filters may be added to the virtual address in accordance with user actions outside the virtual address bar, or alternatively, may be directly added to the virtual address bar by typing the name of a predetermined filter.

At block 2104, a determination is made as to whether the new filter conflicts with an existing filter already in the virtual address. As discussed earlier with respect to PARAGRAPHS 46A-46D, a new filter may conflict with an existing filter if it significantly narrows or expands the scope of the existing filter. Alternatively, the new filter may conflict with the existing filter because the new filter is mutually exclusive with the existing filter. If, at decision block 2104, the new filter conflicts with an existing filter, at block 2106, the existing filter is removed from the virtual address. Alternatively, at 2104, if the new filter does not conflict with the existing filter or, after removing the existing conflicting filter in block 2106, at block 2108, the new filter is added to the end of the virtual address. After that, the example routine 2100 ends.

NUMBERS 51-57 are diagrams relating to a system and method in accordance with another aspect of the present invention that provides an improved user experience within a shell browser. More precisely, a system and method are provided by which users can more readily recognize an object based on the metadata associated with that object.

Turning to SECTION 51A, window 2200 represents a screen-sized display area for the shell browser's graphical user interface. Window 2200 includes space for a preview page 2202 and a view area 2204. The preview page 2202 may include a preview control 2206, a user interface (UI) or change control 2208, and a task control 2210. Typically, a preview control will 2206 provide the user with an image or other visual representation of the item being previewed (ie, the selected file). The preview control 2206 may also present the user with controls such as scroll buttons that allow the user to move the focus from one object to another with the click of a mouse button. Metadata corresponding to one or more items and/or metadata corresponding to an item container may be displayed in various locations within the window 2200. For example, the change control and metadata may be co-located within the change control space 2208 so that the change control not only includes displaying key properties of the pre-browsed item, but also gives the user the ability to change the metadata. Task control 2210 contains tasks relevant to the namespace and/or selection.

For purposes of this invention, the terms “metadata” and “user variable metadata” exclude the name of the shell object. The term “shell object name” refers to a property used for sorting and displaying objects within the shell browser. As mentioned earlier, one unique aspect of the present invention is the ability for the user to change metadata within the shell browser.

Those skilled in the art will appreciate that this invention contemplates the presence of additional capabilities within window 2200. For example, preview control 2206 and task control 2210 are not necessary capabilities for purposes of this invention. Moreover, other optional features not shown in ITEM 51A, such as a toolbar that includes scroll buttons or show/hide buttons so that the user can open/close the preview page, are also within the scope of this invention. . However, these and other additional features can help the user readily find specific items within the shell browser.

View space 2204 provides a list view of one or more objects 2212 , such as file system files or folders. The term "list view" refers to an enumeration or list of items within a container. The terms "object" and "shell object" are used interchangeably herein to refer to files, folders, and other such containers, and to other non-file objects that may be represented in a list view. Examples of non-file objects may include, but are not limited to, contacts, favorites, and e-mail messages. The terms "shell browser" and "file system browser" are used interchangeably here to refer to a browser that allows the user to navigate through various namespaces including files and other non-file objects.

Those skilled in the art will appreciate the fact that the present invention contemplates many possible design and layout solutions for window 2200. For example, a preview page 2202 is shown above viewport 2204 in ITEM 51A. However, other layouts, such as placing the preview page 2202 and view area 2204 side by side, are clearly within the scope of the present invention. The location of the toggle control 2208 is also independent of the location of the displayed metadata and independent of the location of any of the other controls. There are also many possible view types for items displayed in list view space 2204 , such as details, slide show, moviestrip, thumbnails, tiled, icons, etc.

ITEM 51B is similar to ITEM 51A, except that viewspace 2204 is replaced by viewspace 2214 that displays objects 2212 in detail mode. As is common for shell objects displayed in details mode, the objects 2212 are aligned in a column to the left of the viewport 2214 , and one or more column headings 2216 from the first row of a set of columns containing metadata 2218 relating to the corresponding object are placed are in the same line. Importantly, the present invention contemplates the ability for the user to explicitly change the metadata value to some other value through the use of one or more change controls 2208 anywhere within the window 2200. For example, the change control may be provided within the preview page 2202 and/or within viewspace 2214. For example, editing control that is not initially visible to the user may be provided within viewspace 2214. Such control may be provided, for example, when the user hovers over metadata 2218 and then clicks on it to enter editing mode .

Referring further to ITEM 52, a schematic illustration of a shell browser welcome screen 2300 is provided. The welcome screen is sometimes called the "empty selection" screen because it represents a namespace or container rather than a selection. If the user has not yet made a selection, the preview page 2302 displays metadata 2304 and key tasks related to the folder or shell library. If desired, tasks can be separated into top tasks 2306 and other relevant tasks 2308. Welcome screen 2300 also includes a view area 2310, in which multiple files or other objects can be viewed 2312. Welcome screen metadata 2304 can include information such as container properties (eg, My Pictures), in which case the metadata display may be static. Alternatively, the welcome screen metadata 2304 may include information such as sample metadata from each item within the container, in which case the metadata display may change frequently. For example, the metadata display may be limited to displaying the properties of one object after another, cycling from one object to another every 30 seconds.

FIGURE 53 is a schematic illustration of a selection page 2400 in a shell browser. Unlike the welcome screen, the selection page represents the user's selection. If the user selects a container or folder, the selection page does not have to be the same as the welcome screen for that container or folder. In ITEM 53, the selection page 2400 includes a preview page 2402 that includes a preview control 2404, a metadata view 2406, and a task view 2408. Like the welcome screen 2300 (in ITEM 52), the selection page 2400 also includes a view space 2410 in which the multiple files or other objects be viewed 2412. In ITEM 53, however, the user has selected one of the files. Consequently, preview control 2404 displays a preview image of the selected file, metadata view 2406 displays properties of the selected file, and task view 2408 provides a menu of relevant tasks to perform on the selected file.

ITEM 54 is a schematic representation of the selection page of ITEM 53 but which also includes a context menu 2500 to allow a user to modify metadata in a shell browser in accordance with an embodiment of the present invention. The context menu 2500 in ITEM 54 presents the user with several options for changing the selected metadata. The original text shown in menu 2500 is of course only one example of the type of options that can be presented to the user to change the displayed metadata. A context menu can be provided in any window, including the welcome screen, to improve the user experience. As those skilled in the art will appreciate, any number and variety of context menus may be supported by the present invention. For purposes of the present invention, one means of enabling the user to modify the displayed metadata within the shell browser is to provide context menus such as the variable metadata context menu 2500. The user may invoke the context menu, for example, by clicking on the corresponding text or object in the preview page. .

Those skilled in the art will appreciate that the present invention contemplates means other than context menus to allow the user to modify the displayed metadata within the shell browser. Another such means is for the user to click on the metadata to enter edit mode. In contrast, the user could enter edit mode by hovering over the relevant text or object in the preview page. A number of alternative means are available and fall within the scope of this invention.

ITEM 55 is a flow diagram illustrating a method 2600 for allowing a user to modify metadata displayed in a welcome screen within a shell browser in accordance with an embodiment of the present invention. The method 2600 includes displaying a welcome screen and metadata associated with the welcome screen at 2602. Thereafter, at 2604, the method provides control for the user's modification of the displayed metadata. When the user operates the control to modify the displayed metadata at 2606 , the method then associates the modified metadata with the welcome screen at 2608 so that the modified metadata will be displayed the next time the welcome screen is displayed.

ITEM 56 is a flow diagram illustrating a method 2700 for allowing a user to modify metadata displayed in a selection page within a shell browser in accordance with an embodiment of the present invention. At 2702 , method 2700 first displays a number of items, such as items in a welcome screen or items in a selected container. When the user selects one or more items at 2704 , the method displays metadata associated with the selected item(s) at 2706 . At 2708 , the method provides control for the user's modification of the displayed metadata. When the user operates the control to modify the displayed metadata at 2710 , the method then associates the modified metadata with the selected object(s) at 2712 so that the modified metadata would be displayed the next time the selected object(s) is displayed.

In the event that the user selects multiple objects at 2704 , the displayed metadata may include overlapping properties of the selected objects, a union of properties, or perhaps a new property relevant to the selected objects. Alternatively, the displayed metadata may include a rotating sample of the metadata from each selected item (eg, cycling from the metadata of one selected item to the metadata of the next selected item every 30 seconds). It is possible that the metadata display that would result from selecting all subjects would be identical to the metadata display that would result from an empty selection.

ITEM 57 is a block diagram of a data structure 2800 that contains user-modifiable metadata associated with an object displayed in a shell browser. Data structure 2800 includes a title field 2802 that indicates the name of the item. In the case of non-file items, the title field 2802 may contain a name or any other property used to alphabetically sort that item in a list view. Data structure 2800 includes a user-modifiable property field 2804 containing one or more properties associated with the displayed object, wherein the user-modifiable properties are displayed in the shell browser along with the displayed object. The data structure 2800 may further include a read-only properties field 2806 that contains read-only properties associated with the rendered object and worthy of display in the shell browser. Due to the size limitations of the shell browser's metadata display, the number of properties in fields 2804 and 2806 may be limited. As a consequence, data structure 2800 may additionally include an all properties field 2808 , which contains a link or pointer to a location (eg, a property page) that contains all properties or metadata associated with the displayed object. Of course, the all-properties field 2808 would not be necessary if the fields 2804 and 2806 contained all the properties associated with the displayed object. Data structure 2800 is stored on one or more computer-readable media, such as a file system or shell, to provide rich storage views, and thus an enhanced user experience, within the shell browser.

This invention enables several scenarios that were not possible with conventional shell browsers. As a first example, a student can manage her projects using the preview page. When she acquires new documents as part of a project she's working on, she can select those documents in her document library and enter the document author's name and project name in the keyword fields using the edit control. Now the new documents will appear in her favorites view: "Documents Grouped by Keyword and Ordered by Author." Another example of a novel scenario enabled by the present invention involves an employee seeking materials for an upcoming advertising campaign. While looking through his employer's stock of photos using the shell browser, he selects a few images and, from the preview page, adds the new keyword "Summer 2003 Campaign." After refreshing the multi-select metadata, the employee then pivots by keyword and can see all the “Summer 2003 Campaign” files grouped together. Many other scenarios that take advantage of the present invention will be apparent to those skilled in the art.

NUMBERS 58-66 are diagrams relating to a system and method for extending the functionality of an object previewer in a shell browser configured to display a plurality of objects representing multiple types of objects. As will be described in more detail later, a shell browser is provided that includes a default pre-browser and extensibility mechanism. The default previewer provides a standard level of functionality for multiple item types. The extensibility mechanism provides functionality beyond the standard level provided by the default previewer for one or more item types.

FIGURE 58 is a schematic diagram of a prior art graphical user interface for viewing images stored in a folder within a shell browser environment used to view other non-image files or folders. As previously established, the need for ready recognition of objects stored in a computing environment such as a PC is increasing dramatically. With digital images, users have traditionally had to run a third-party software program to view a particular file on a PC. SECTION 58 illustrates an earlier solution, a filmstrip view, which allows the user to more readily see and recognize the image associated with a given file within a graphical operating environment. The goal of Filmstrip View was to remove the need for other software programs when browsing image folders by providing a fast iterative process that allows the user to preview a resizable image of one or more image files within a folder.

CLAUSE 58 relates to a system for viewing images stored in a folder, wherein a sequence of images of the folder is displayed as a single line of fingernail-sized thumbnails within an environment used to view other non-image files and folders (ie, a shell browser). The user is further allowed to selectively navigate the cursor through the thumbnails, which displays an enlarged preview image of the thumbnail the user has selected. ITEM 58 is a diagram of the representative window on the user's screen. As shown, the window 3200 is divided into several areas including a header area, a task options area 3206, a preview control area 3202, an image description or comment area, and a moviestrip area 3204. The task options area 3206 contains a list of tasks that the user can select to perform a wide variety of operations related to file and folder management, as well as other system choices. Some of these operations are specific to the images in the filmstrip area 3204 and in the preview control area 3202. The preview control area 3202 is an area in which an enlarged preview image of the image selected by the user will be displayed. This space may also contain navigation icons to help the user iterate through a series of images. Immediately below the preview control area is an image description or comment area that can be used to display various textual information. Filmstrip area 3204 provides space to display one row of thumbnails P1, P2, P3, P4 of the image files contained within a given folder. Additionally, the filmstrip area 3204 also contains cursors to allow the user to search through the folder for image files. It should be noted that the filmstrip area 3204 may contain and display small thumbnails in mixed orientation. For example, as shown in ITEM 58, P1, P2 and P4 are in landscape orientation while P3 is in portrait orientation.

The user can select any of the thumbnails, which will cause a larger preview image of the user-selected thumbnail to be displayed within the preview control area. Additionally, the user's selection of the thumbnail will also allow the user to select and perform any of the tasks listed in the task options area 3206 , with respect to the selected image. The first control button allows the user to quickly and sequentially preview an enlarged image of each thumbnail within a given folder, by iterating in one direction. In other words, the user should not have to separately "click" on each individual thumbnail in the sequence to preview the image. Instead the user will simply repeatedly click the first control button to move through the folder. The second control knob performs a similar iteration but only in the opposite direction.

Referring to ITEM 59, window 3300 represents a screen size display area for a general purpose shell browser graphical user interface. Window 3300 includes a preview page area 3302 and a view area 3304. The preview page 3302 may include a preview control 3306, a change or metadata control 3308, and a task control 3310. Typically, the preview control 3306 will provide the user with an image or some another visual representation of the item being previewed (eg, selected files). The preview control 3306 may also provide the user with controls such as iteration buttons that allow the user to move the focus from one object to the next by clicking a mouse button. Editing control 3308 not only includes the display of key properties of the pre-viewed item, but it also gives the user control to make changes to the metadata. Task control 3310 contains tasks relevant to the namespace and/or selection.

Those skilled in the art will appreciate that this invention contemplates the presence of additional capabilities within window 3300. For example, metadata control 3208 and task control 3210 are not necessary capabilities for purposes of this invention. Moreover, other optional features not shown in ITEM 59, such as a toolbar that includes iteration buttons or buttons to show/hide the preview page to allow the user to open/close the preview page, also fall within within the scope of this invention. Regardless, these and other additional features can help the user more readily find a specific item in the shell browser.

View area 3304 provides a list view of one or more objects 3312 , such as files or file system folders. The term "list view" refers to an enumeration or list of items within a container. The terms "object" and "shell object" are used interchangeably here to refer to files, folders, and other such containers, and to other non-file objects that may be represented in a list view. Similarly, “shell object” refers to an object in the shell library. Examples of non-file objects may include, but are not limited to, contacts, favorites, and e-mail messages. The terms "shell browser" and "file system browser" are used interchangeably here to refer to a browser that allows the user to navigate through various namespaces including files and other non-file objects.

Those skilled in the art will appreciate that the present invention contemplates many possible design and layout solutions for window 3300. For example, a preview page 3302 is shown above viewport 3304 in FIGURE 59. However, other layouts, such as placing side-by-side preview pages 3302 and view area 3304 are clearly within the scope of the present invention. There are also many possible view types for items displayed in list view space 3304 , such as details, slide show, moviestrip, thumbnails, tiled, icons, etc.

Referring further to ITEM 60, a schematic illustration of a welcome screen 3400 in a shell browser is provided. The welcome screen is sometimes called the "empty selection" screen because it represents a namespace or container rather than a selection. If the user has not yet made a selection, the preview page 3402 displays metadata 3404 and key tasks related to the folder or shell library. If desired, tasks can be separated into top tasks 3406 and other relevant tasks 3408. Welcome screen 3400 also includes a view area 3410, in which multiple files or other objects can be viewed 3412. Welcome screen metadata 3404 can include information such as container properties (eg, My Pictures), in which case the metadata display may be static. Alternatively, the welcome screen metadata 3404 may include information such as sample metadata from each item within the container, in which case the metadata display may change frequently. For example, the metadata display may be limited to displaying the properties of one object after another, cycling from one object to another every 30 seconds.

FIGURE 61 is a schematic illustration of a selection page 3500 in a shell browser. Unlike the welcome screen, the selection page represents the user's selection. If the user selects a container or folder, the selection page does not have to be the same as the welcome screen for that container or folder. In ITEM 61, the selection page 3500 includes a preview page 3502 containing a preview control 3504, a metadata view 3506, and a task view 3508. Like the welcome screen 3400 (in ITEM 60), the selection page 3500 also includes a view space 3510 in which the multiple files or other objects be viewed 3512. In ITEM 61, however, the user has selected one of the files. Consequently, preview control 3504 displays a preview image of the selected file, metadata view 3506 displays properties of the selected file, and task view 3508 provides a menu of relevant tasks to perform on the selected file.

ITEM 62 is a schematic diagram of a selection page similar to the selection page 3500 of ITEM 61 but with expanded controls in accordance with an embodiment of this invention. The selection page 3600 includes a preview page 3602 that contains a preview control 3604 that has extended controls 3614, a metadata view 3606, and a task view 3608. The selection page 3600 also includes a view area 3610, in which multiple files or other objects 3612 can be viewed. .The user has selected one of the files 3612, so the preview control 3604 displays a preview image of the selected file, the metadata view 3606 shows the properties of the selected file, and the task view 3608 provides a menu of relevant tasks to perform on the selected file.

Extended controls 3614 represent a level of functionality beyond that normally available in shell browsers. For example, a default preview page or preview control, such as those shown in paragraphs 58 and 61, may simply display a preview image of a selected item. If the subject is a word processing program document or an image presentation, the default preview image can be the first page of the document or a group of images in the presentation. However, by extending the functionality of the preview image to make it more interactive, the user can very easily operate the extended controls 3614 to scroll through the document or image presentation. This enhanced level of functionality improves the user experience by allowing the user to more extensively review a previewed item without opening it, which is particularly useful for files that cannot be readily recognized based on their first page alone.

Extended controls 3614 may be made available to the user as part of an alternative preview in the shell browser. The term "preview" can refer to a preview control or a preview page that includes a preview control. The present invention contemplates a shell viewer that provides the user with a default preview viewer that offers a standard level of functionality for multiple item types and one or more alternate preview viewers that offer a different level of functionality for a specific item type to enhance the user experience. Opening the development of alternative previewers to independent software vendors (ISVs) and other third-party developers adds value to the file browsing experience by showing relevant aspects of the file in an easily recognizable way. The present invention contemplates specially adapted previewers for a number of file types and non-file object types including, but not limited to, image files, video files, contacts, games, scanners, video cameras, document files, spreadsheet files, image presentations , drawing files and tablet ink files.

This invention enables a number of scenarios that were not possible with conventional shell browsers, some of which have been described earlier. Third parties are allowed to describe and represent their file types by providing code that can look inside the file type and provide a meaningful picture that the user will understand. For example, Apple could implement a QuickTime™ preview control, which would be displayed when the user selects a QuickTime™ file in the shell browser. This preview control could provide an alternative or extended level of functionality beyond the default previewer in the operating system shell, including functionality such as displaying the first five seconds of a QuickTime™ movie and/or providing buttons and controls for the user to launch a playback program QuickTime™ file. An alternative previewer for music files could provide similar extended functionality. As those skilled in the art will appreciate, the possibilities for extended functionality in an alternative previewer are limitless.

ITEM 63 is a schematic representation of a selection page similar to that of ITEM 61 but also including a context menu 3714 to allow a user to modify metadata in a shell browser in accordance with an embodiment of the present invention. The selection page 3700 includes a preview page 3702 that contains a preview control 3704, a metadata display 3706, and a task control 3708. The selection page 3700 also includes a view area 3710, in which multiple files or other objects 3712 may be displayed. Those skilled in the art those in the art will appreciate that, for purposes of this invention, metadata control 3706 and task control 3708 are not necessary capabilities. The present invention contemplates the presence of these and/or other additional capabilities that may assist the user in readily finding a curated item in the shell browser or otherwise enhance the user experience.

The context menu 3714 in ITEM 63 presents the user with several options, including the choice of selecting either the default previewer or an alternative previewer for the selected item. The source text shown in menu 3714 is of course only one example of the type of options that may be presented to the user for selecting a previewer. A context menu can be provided in any window, including the welcome screen, to improve the user experience. As will be appreciated by those skilled in the art, any number and variety of context menus may be supported by the present invention. For purposes of the present invention, one means of allowing users to select a preview within the shell browser is to provide a context menu such as context menu 3714. The user may invoke the context menu, for example, by clicking on the appropriate text or object in the preview page.

Those skilled in the art will appreciate that the present invention, in addition to context menus, contemplates other means of selecting a previewer for displayed objects from among the multitude of available previewers within the shell browser. Another such means is for the user to click on the preview control to enter selection mode. Similarly, the user may be prompted to select a preview by right-clicking within the preview page. In contrast, the user could enter selection mode by hovering over relevant text or over a relevant object in the preview page. A number of alternative means are available and fall within the scope of this invention.

ITEM 64A is a flow diagram illustrating a method 3800 for allowing a user to select a preview in a shell browser that supports multiple item types in accordance with an embodiment of the present invention. Method 3800 provides a plurality of previewers in the shell viewer at 3802. The plurality of previewers may include a default previewer for multiple data types and one or more alternative previewers for a particular data type. These alternative previewers may include installed applications developed by third parties. Cor 3804 , method 3800 presents the user with a choice of two or more previews for a particular item type. A preview selection request can be initiated by the shell browser (eg, when displaying a new object type) and/or by the user (eg, by clicking on an object to display a context menu). After receiving input from the user at 3806 indicating the selection of one of the previewers for the particular item type, method 3800 then associates the selected previewer with the particular item type at 3808. The selected previewer will remain in use until the user selects another . However, if the selected previewer is an installed application, removing the application will also stop using the selected previewer.

ITEM 64B is a flow diagram illustrating a method 3810 for automatically selecting a pre-viewer in a shell browser that supports multiple object types in accordance with an embodiment of the present invention. Method 3810 provides a plurality of previewers in the shell viewer at 3812. The plurality of previewers may include a default previewer for multiple item types and one or more alternative previewers for a particular item type. These alternative previewers may include installed applications developed by third parties.

At 3814, the system (as opposed to the user) automatically and invisibly selects a default previewer from among two or more previewers for a given item type. The system may select a previewer in response to an event such as the rendering of a new item type or the presence of an alternative previewer. The system is configured to select a default previewer based on logical rules. Under exceptional circumstances, the system may 3816 decide to skip the rule and select a pre-browser that would not be selected under the applicable rules. For example, if the rule is to select a newer available previewer over the current default previewer, the installed application may generally have the power to change the default previewer to the previewer now available from the installed application. However, the shell browser, for example, may reserve the right to skip a change proposed by a newly installed application. For example, skipping may be appropriate when newly installed applications cannot be authenticated as the true owner of the item type in question.

In each case, method 3810 then associates the selected previewer with the specified object type at 3818. The selected previewer will remain in use until another is selected. However, if the selected previewer is an installed application, removing the application will also stop using the selected previewer.

Referring further to ITEM 65, a flow diagram illustrates a method 3900 for enabling the use of third-party previewers in a shell browser that supports multiple item types in accordance with an embodiment of the present invention. Method 3900 includes providing a shell viewer that has a default preview viewer for the multiple object types at 3902. It further includes providing an extensibility mechanism for developing an alternative third-party preview viewer for at least one of the multiple object types at 3904. The alternative preview viewer may be registered in the shell browser code 3906. In the case of an installed application, the registration can actually happen at the time of installation. For example, if the application is installed by an OEM, an alternative previewer can be registered before the user even gets the computer. Alternatively, the user can install the application locally or remotely.

There are many possible approaches to the extensibility mechanism mentioned earlier in 3904. One such approach involves exposing a set of application program interfaces (APIs) so that independent software vendors (ISVs) and other third-party developers can develop alternative previewers. With API access, there is a registration mechanism that allows third-party software vendors to associate their preview control with an object type owned by that vendor. When an object or file of that type is selected in the shell browser, third-party preview control is achieved through that registration mechanism and extensibility API. The API provides data to the preview control: data representing the selected item(s) in the view and data representing the parent container of the view. The preview control processes this data and provides a user interface through an API that is displayed in the shell browser. The user can provide input with keystrokes and mouse events that the shell browser passes to a preview control that can process these user input events.

Those skilled in the art will appreciate the fact that many approaches are possible in the context of the extensibility mechanism of the present invention. In addition to API access, similar functionality can be achieved via user customization, HTML pointers, or flash placement. Moreover, the extensibility model may require that only one application owning the selected item type can provide only one alternative previewer. In other words, the number of available previewers can be limited to the default previewer and one alternate previewer to avoid a bad user experience where multiple registered, extended previewers compete with each other. However, another model would be to allow any application that can handle the selected object type to provide an alternate previewer. An alternative model would allow any code being executed to provide one additional previewer for any object type. Under certain circumstances it may also be desirable to allow the default previewer to be replaced or removed. Many other models are possible and contemplated by the present invention.

FIGURE 66 is a block diagram of a data structure 4000 that is stored on one or more computer-readable media and that contains information indicative of a plurality of previewers in a shell browser. Data structure 4000 includes a default previewer field 4002 that contains information about a default previewer that supports multiple subject types. The alternate previewer field 4004 contains information about the alternate previewer for the first item type. Another alternative previewer field 4006 may contain information about another alternative previewer for the first item type, or may contain information about an alternative previewer for the second item type. Those skilled in the art will appreciate that in some cases there may be only one alternate preview field and in other cases there may be two or more alternate preview fields. The selected previewer field 4008 contains information about whether the default previewer or an alternate previewer should be invoked when items of a particular item type are displayed in the shell viewer. In the event that field 4006 contains information about an alternate previewer for another item type, selected previewer field 4010 may include information about whether the default previewer or an alternate previewer should be invoked when one or more items of the other item type are displayed in the shell browser. The information contained in fields 4002, 4004 and/or 4006 may constitute preview code that is configured to be executed when the user selects an object of that type.

Although a preferred embodiment of the present invention has been illustrated and described, it should be appreciated that various changes may be made therein without departing from the spirit and scope of the invention. For example, it should be appreciated that the locations of the various UI features shown herein are illustrative only and may be changed, and that the various placements of the UI features will still fall within the spirit and scope of the invention. Furthermore, the various aspects of the invention described herein may be embodied in various combinations, also without departing from the spirit and scope of the invention.

Inventions in which exclusive ownership or privilege is claimed are defined as follows:

Claims (124)

1. In a computer system with a display and memory for storing items, a method for representing sets of items characterized by comprising: creating a library that will contain objects with one or more special metadata properties; automatic grouping of items with one or more special metadata properties into a library; and providing one or more tools for managing items in the library. 2. The method of claim 1, further comprising a shell browser method for enabling a user to modify metadata within the shell browser, wherein the shell browser method comprises: showing a plurality of subjects; receiving the first input from the user that represents the selection of at least one of the displayed items; displaying metadata associated with at least one selected item; and providing control for user modification of displayed metadata. 3. The method of claim 1, further comprising providing a shell browser, wherein the shell browser comprises: a window displaying a group of items, wherein the window also displays metadata values associated with one or more displayed items; and change control that allows the user to change at least one part of the metadata values displayed in the window. 4. The method of claim 1, further comprising a preview-browser method for enabling the use of third-party preview-browsers in a shell browser that supports multiple object types, wherein the preview-browser method comprises: providing a shell browser that has a default pre-browser for multiple item types; and providing an extensibility mechanism that allows third parties to develop alternative previewers for at least one of the multiple object types. 5. The method of claim 1, further comprising providing a shell browser configured to display a plurality of objects representing multiple object types, wherein the shell browser comprises: default previewer that provides a standard level of functionality for multiple item types; and an extensibility mechanism that provides functionality beyond the standard level provided by the default previewer for one or more of multiple object types. 6. The method of claim 1, further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system using a virtual address bar, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive segments to the virtual address bar, each additional interactive segment further restricting the objects referenced by the preceding interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 7. The method of claim 1, characterized in that it further comprises providing user interface control of a virtual address bar for selecting items available to the computer system for display, wherein the virtual address bar contains: a plurality of interactive segments, where each interactive segment corresponds to a filter for selecting items to display. 8. The method from claim 1, characterized in that it further contains a method of object filtering, wherein the object filtering method contains: providing a plurality of screen objects on the screen each representing one or more objects; filtering of objects represented by screen objects depending on the filtering condition; and changing the screen objects provided on the screen to represent the objects remaining after filtering the objects. 9. The method from claim 1, characterized by the fact that it further contains a method for displaying objects, wherein the method for displaying objects contains: determining a range of physical memory locations from which to retrieve items, wherein the range includes the memory of the present computer and at least one other physical location; receiving queries and, in response to the query, retrieving items from physical locations as determined by the scope; and displaying the items taken from the query in the view on the screen. 10. The method from claim 1, characterized in that it further contains a method for presenting the object to the user, wherein the method for presenting the object to the user contains: providing a database that allows both non-file items and file items to be searched by query; receiving queries and, in response to the query, retrieving both non-file objects and file objects that satisfy the query; and displaying both non-file items and file items that satisfy the query on the screen. 11. System for revealing objects stored in memory to the user, characterized by the fact that it contains: a map processing unit that receives queries from users; relational database for storing information about subjects; and thereby: the map processing unit obtains a query from the user and forwards the query to the relational database; the relational database provides results back to the map processing unit; and depending on the results from the relational database, the map processing unit provides the results to the user as virtual maps. 12. The system of claim 11 further comprising a shell browser method for enabling the user to change metadata within the shell browser, wherein the shell browser method comprises: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed item; and providing control for user modification of displayed metadata. 13. The system of claim 11 further comprising a shell browser, wherein the shell browser comprises: a window displaying a group of items, wherein the window also displays metadata values associated with one or more displayed items; and a change control that allows the user to change at least part of the metadata values displayed in the window. 14. The system of claim 11 further comprising a preview viewer for enabling the use of third-party preview viewers in a shell browser that supports multiple object types, wherein the preview viewer comprises: a shell viewer that has a default previewer for multiple item types; and an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple object types. 15. The system of claim 11 further comprising a shell browser configured to display a plurality of objects representing multiple types of objects, wherein the shell browser comprises: a default previewer that provides a standard level of functionality for multiple item types; and an extensibility mechanism that provides functionality beyond the standard level provided by the default previewer for one or more of multiple object types. 16. The system of claim 11 further comprising a virtual address bar for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and one or more additional interactive segments of the virtual address bar, each additional interactive segment further restricting the objects referenced by the previous interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 17. The system of claim 11 characterized in that it further contains control of the user interface of the virtual address bar for selecting items available to the computer system for display, wherein the virtual address bar contains: a plurality of segments, where each interactive segment corresponds to a filter for selecting items to display. 18. The system of claim 11 characterized in that it further contains a method for filtering objects, wherein the method for filtering objects contains: providing a plurality of screen objects on the screen each representing one or more objects; filtering items represented by screen objects based on a filtering condition; and changing the screen objects that are rendered on the screen to represent the objects that remain after filtering the objects. 19. The system from claim 11 characterized in that it further contains a method for presenting subject collections, wherein the method for presenting subject collections contains: creating a library that will contain objects with one or more specific metadata properties; automatic grouping of items with one or more specific metadata properties into a library; and providing one or more tools for managing items in the library. 20. The system from claim 11 characterized in that it further contains a method for displaying objects, wherein the method for displaying objects contains: determining a range of physical memory locations from which to retrieve objects, wherein the range contains the memory of the present computer and at least one other physical location; receiving queries and, in response to the query, retrieving items from physical locations as determined by the scope; and presenting the items retrieved from the query in the view on the screen. 21. In a computer system having a screen and memory for storing items, wherein the items have associated metadata properties, a method for disclosing the item to a user characterized by comprising: selecting the first metadata property; searching for items that have the first metadata property selected; and providing a first virtual folder display object representing a collection of objects possessing the first metadata property. 22. The method of claim 21 further comprising a shell browser method for enabling a user to modify metadata within the shell browser, wherein the shell browser comprises: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed object; and providing control for user modification of displayed metadata. 23. The method of claim 21 further comprising providing a shell viewer, wherein the shell viewer comprises: a window displaying a group of items, wherein the window also displays metadata values associated with one or more displayed items; and a change control that allows the user to change at least part of the metadata values displayed in the window. 24. The method of claim 21 further comprising a preview viewer method for enabling the use of third-party preview viewers in a shell browser that supports multiple object types, wherein the preview viewer comprises: providing a shell browser that has a default pre-browser for multiple item types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple object types. 25. The method of claim 21 further comprising providing a shell viewer configured to display a plurality of objects representing multiple object types, wherein the shell viewer comprises: a default previewer that provides a standard level of functionality for multiple item types; and an extensibility mechanism that provides functionality beyond the standard level provided by the default previewer for one or more of multiple object types. 26. The method of claim 21 further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive virtual address bar segments, wherein each additional interactive segment further constrains the objects referenced by the preceding interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 27. The method of claim 21 further comprising providing control of a virtual address bar user interface for selecting items available to the computer system for display, wherein the virtual address bar comprises: a plurality of segments, where each interactive segment corresponds to a filter for selecting items to display. 28. The method of claim 21 characterized in that it further contains a method for filtering objects, wherein the method for filtering objects contains: providing a plurality of screen objects on the screen each representing one or more objects; filtering items represented by screen objects based on a filtering condition; and changing the screen objects that are rendered on the screen to represent the objects that remain after filtering the objects. 29. The method from claim 21 characterized in that it further contains a method for presenting subject collections, wherein the method for presenting subject collections contains: creating a library that will contain objects with one or more specific metadata properties; automatic grouping of items with one or more specific metadata properties into a library; and providing one or more tools for managing items in the library. 30. The method from claim 21 characterized by the fact that it further contains a method for displaying objects, wherein the method for displaying objects contains: determining a range of physical memory locations from which to retrieve objects, wherein the range contains the memory of the present computer and at least one other physical location; receiving queries and, in response to the query, retrieving items from physical locations as determined by the scope; and presenting the items retrieved from the query in the view on the screen. 31. In a computer system having a screen and memory for storing items, a method for managing items characterized by comprising: presentation of subject groups as a virtual folder; and providing at least a first specific action that can be performed to directly manage the virtual folders, wherein, when the first specific action is performed, the virtual folder is managed as determined by the performed action. 32. The method of claim 31 further comprising a shell browser method for enabling a user to modify metadata within the shell browser, wherein the shell browser method comprises: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed item; and providing control for user modification of displayed metadata. 33. The method of claim 31 further comprising providing a shell viewer, wherein the shell viewer comprises: a window displaying a group of items, wherein the window also displays metadata values associated with one or more displayed items; and a change control that allows the user to change at least part of the metadata values displayed in the window. 34. The method of claim 31 further comprising a preview-browser method for enabling the use of third-party preview-browsers in a shell browser that supports multiple object types, wherein the preview-browser method comprises: providing a shell browser that has a default pre-browser for multiple object types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple object types. 35. The method of claim 31 further comprising providing a shell viewer configured to display a plurality of objects representing multiple object types, wherein the shell viewer comprises: a default previewer that provides a standard level of functionality for multiple item types; and an extensibility mechanism that provides functionality beyond the standard level provided by the default previewer for one or more of multiple object types. 36. The method of claim 31 further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive virtual address bar segments, wherein each additional interactive segment further constrains the objects referenced by the preceding interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 37. The method of claim 31 further comprising providing control of a virtual address bar user interface for selecting items available to the computer system for display, wherein the virtual address bar comprises: a plurality of segments, where each interactive segment corresponds to a filter for selecting items to display. 38. The method from claim 31 characterized in that it further contains a method for filtering objects, wherein the method for filtering objects contains: providing a plurality of screen objects on the screen each representing one or more objects; filtering items represented by screen objects based on a filtering condition; and changing the screen objects that are rendered on the screen to represent the objects that remain after filtering the objects. 39. The method from claim 31 characterized in that it further contains a method for presenting subject collections, wherein the method for presenting subject collections contains: creating a library that will contain objects with one or more specific metadata properties; automatic grouping of items with one or more specific metadata properties into a library; and providing one or more tools for managing items in the library. 40. The method from claim 31 characterized in that it further contains a method for displaying objects, wherein the method for displaying objects contains: determining a range of physical memory locations from which to retrieve objects, wherein the range contains the memory of the present computer and at least one other physical location; receiving queries and, in response to the query, retrieving items from physical locations as determined by the scope; and presenting the items retrieved from the query in the view on the screen. 41. In a computer system having a screen and memory for storing items, a method for filtering items characterized by comprising: providing a plurality of screen objects on the screen each representing one or more objects; filtering items represented by screen objects based on a filtering condition; and changing the screen objects rendered on the screen to represent the objects remaining after filtering the objects. 42. The method of claim 41 further comprising a shell browser method for enabling a user to modify metadata within the shell browser, wherein the shell browser method comprises: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed item; and providing control for user modification of displayed metadata. 43. The method of claim 41 further comprising providing a shell viewer, wherein the shell viewer comprises: a window displaying a group of items, wherein the window also displays metadata values associated with one or more displayed items; and a change control that allows the user to change at least part of the metadata values displayed in the window. 44. The method of claim 41 further comprising a preview-browser method for enabling the use of third-party preview-browsers in a shell browser that supports multiple object types, wherein the preview-browser method comprises: providing a shell browser that has a default pre-browser for multiple item types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple item types. 45. The method of claim 41 further comprising providing a shell viewer configured to display a plurality of objects representing multiple object types, wherein the shell viewer comprises: a default previewer that provides a standard level of functionality for multiple item types; and an extensibility mechanism that provides functionality beyond the standard level provided by the default previewer for one or more of multiple object types. 46. The method of claim 41 further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive virtual address bar segments, wherein each additional interactive segment further constrains the objects referenced by the preceding interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 47. The method of claim 41 further comprising providing user interface control of a virtual address bar for selecting items available to the computer system for display, wherein the virtual address bar comprises: a plurality of segments, where each interactive segment corresponds to a filter for selecting items to display. 48. The method from claim 41 characterized in that it further contains a method for filtering objects, wherein the method for filtering objects contains: providing a plurality of screen objects on the screen each representing one or more objects; filtering items represented by screen objects based on a filtering condition; and changing the screen objects that are rendered on the screen to represent the objects that remain after filtering the objects. 49. The method from claim 41 characterized by the fact that it further contains a method for presenting subject collections, wherein the method for presenting subject collections contains: creating a library that will contain objects with one or more specific metadata properties; automatic grouping of items with one or more specific metadata properties into a library; and providing one or more tools for managing items in the library. 50. The method from claim 41 characterized in that it further contains a method for displaying objects, wherein the method for displaying objects contains: determining a range of physical memory locations from which to retrieve objects, wherein the range contains the memory of the present computer and at least one other physical location; receiving queries and, in response to the query, retrieving items from physical locations as determined by the scope; and presenting the items retrieved from the query in the view on the screen. 51. In a computer system having a screen and memory for storing objects, a method for viewing selected objects characterized by comprising: storing a link to the desired collection of items to which the user navigated; displaying the link on the screen so that by clicking on the link the user can return to the view of the desired collection of items. 52. The method of claim 51 further comprising a shell browser method for enabling a user to modify metadata within the shell browser, wherein the shell browser method comprises: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed item; and providing control for user modification of displayed metadata. 53. The method of claim 51 further comprising providing a shell viewer, wherein the shell viewer comprises: a window displaying a group of items, wherein the window also displays metadata values associated with one or more displayed items; and a change control that allows the user to change at least part of the metadata values displayed in the window. 54. The method of claim 51 further comprising a preview-browser method for enabling the use of third-party preview-browsers in a shell browser that supports multiple object types, wherein the preview-browser method comprises: providing a shell browser that has a default pre-browser for multiple object types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple item types. 55. The method of claim 51 further comprising providing a shell viewer configured to display a plurality of objects representing multiple object types, wherein the shell viewer comprises: a default previewer that provides a standard level of functionality for multiple item types; and an extensibility mechanism that provides functionality beyond the standard level provided by the default previewer for one or more of multiple object types. 56. The method of claim 51 further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive virtual address bar segments, wherein each additional interactive segment further constrains the objects referenced by the preceding interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 57. The method of claim 51 further comprising providing user interface control of a virtual address bar for selecting items available to the computer system for display, wherein the virtual address bar comprises: a plurality of segments, where each interactive segment corresponds to a filter for selecting items to display. 58. The method from claim 51 characterized in that it further contains a method for filtering objects, wherein the method for filtering objects contains: providing a plurality of screen objects on the screen each representing one or more objects; filtering items represented by screen objects based on a filtering condition; and changing the screen objects that are rendered on the screen to represent the objects that remain after filtering the objects. 59. The method from claim 51 characterized in that it further contains a method for presenting subject collections, wherein the method for presenting subject collections contains: creating a library that will contain objects with one or more specific metadata properties; automatic grouping of items with one or more specific metadata properties into a library; and providing one or more tools for managing items in the library. 60. The method from claim 51 characterized in that it further contains a method for displaying objects, wherein the method for displaying objects contains: determining a range of physical memory locations from which to retrieve objects, wherein the range contains the memory of the present computer and at least one other physical location; receiving queries and, in response to the query, retrieving items from physical locations as determined by the scope; and presenting the items retrieved from the query in the view on the screen. 61. In a computer system having a screen and memory for storing objects, a method for presenting objects to a user characterized by containing: providing a database that allows both non-file objects and file objects to be searched by query; receiving queries and, in response to the query, retrieving both non-file objects and file objects that satisfy the query; and displaying both non-file items and file items that satisfy the query on the screen. 62. The method of claim 61 further comprising a shell browser method for enabling a user to modify metadata within the shell browser, wherein the shell browser method comprises: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed object; and providing control for user modification of displayed metadata. 63. The method of claim 61 further comprising providing a shell viewer, wherein the shell viewer comprises: a window displaying a group of items, wherein the window also displays metadata values associated with one or more displayed items; and a change control that allows the user to change at least part of the metadata values displayed in the window. 64. The method of claim 61 further comprising a preview-browser method for enabling the use of third-party preview-browsers in a shell browser that supports multiple object types, wherein the preview-browser method comprises: providing a shell browser that has a default pre-browser for multiple object types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple item types. 65. The method of claim 61 further comprising providing a shell viewer configured to display a plurality of objects representing multiple object types, wherein the shell viewer comprises: a default previewer that provides a standard level of functionality for multiple item types; and an extensibility mechanism that provides functionality beyond the standard level provided by the default previewer for one or more of multiple object types. 66. The method of claim 61 further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive virtual address bar segments, wherein each additional interactive segment further constrains the objects referenced by the preceding interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 67. The method of claim 61 further comprising providing user interface control of a virtual address bar for selecting items available to the computer system for display, wherein the virtual address bar comprises: a plurality of segments, where each interactive segment corresponds to a filter for selecting items to display. 68. The method of claim 61 characterized in that it further contains a method for filtering objects, wherein the method for filtering objects contains: providing a plurality of screen objects on the screen each representing one or more objects; filtering items represented by screen objects based on a filtering condition; and changing the screen objects that are rendered on the screen to represent the objects that remain after filtering the objects. 69. The method from claim 61 characterized by the fact that it further contains a method for presenting subject collections, wherein the method for presenting subject collections contains: creating a library that will contain objects with one or more specific metadata properties; automatic grouping of items with one or more specific metadata properties into a library; and providing one or more tools for managing items in the library. 70. The method from claim 61 characterized in that it further contains a method for displaying objects, wherein the method for displaying objects contains: determining a range of physical memory locations from which to retrieve objects, wherein the range contains the memory of the present computer and at least one other physical location; receiving queries and, in response to the query, retrieving items from physical locations as determined by the scope; and presenting the items retrieved from the query in the view on the screen. 71. A method for providing a virtual path to objects stored in a computer file system using a virtual address bar, comprising: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive virtual address bar segments, wherein each additional interactive segment further constrains the objects referenced by the preceding interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 72. The method of claim 71 wherein a user selectable filter is provided on the screen to filter items based on the metadata property specified by the filter. 73. The method of claim 71 characterized in that a quick link is provided on the screen that the user can select to view a specific collection of items. 74. The method of claim 71 wherein a library is provided that includes a collection of items and a set of tools for managing items in the library. 75. The method of claim 71 characterized in that the objects in the virtual map can be physically stored in memories at different physical locations. 76. The method of claim 75 wherein the different physical locations comprise the present computer and at least one of the different computer, network location, and external storage device. 77. The method of claim 71 characterized in that the objects contain both file objects and non-file objects. 78. The method of claim 77 characterized in that the non-file items contain at least one of the contacts or e-mail messages. 79. The method of claim 71 further comprising a shell browser method for enabling a user to modify metadata within the shell browser, wherein the shell browser method comprises: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed object; and providing control for user modification of displayed metadata. 80. The method of claim 71 further comprising a preview-browser method for enabling the use of third-party preview-browsers in a shell browser that supports multiple object types, wherein the preview-browser method comprises: providing a shell browser that has a default pre-browser for multiple object types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple item types. 81. A computer-implemented method for enabling a user to modify metadata within a shell browser, comprising: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed object; and providing control for user modification of displayed metadata. 82. The method of claim 81, wherein a user-selectable filter is provided on the screen to filter items based on the metadata property specified by the filter. 83. The method of claim 81 characterized in that a quick link is provided on the screen that the user can select to view a specific collection of items. 84. The method of claim 81 wherein a library is provided that includes a collection of items and a set of tools for managing items in the library. 85. The method of claim 81 characterized in that the objects in the virtual map can be physically stored in memories at different physical locations. 86. The method of claim 85 wherein the different physical locations comprise the present computer and at least one of the different computer, network location, and external storage device. 87. The method of claim 81 characterized in that the objects contain both file objects and non-file objects. 88. The method of claim 87 characterized in that the non-file objects contain at least one of the contacts or e-mail messages. 89. The method of claim 81 further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive virtual address bar segments, wherein each additional interactive segment further constrains the objects referenced by the preceding interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 90. The method of claim 81 further comprising providing user interface control of a virtual address bar for selecting items available to the computer system for display, wherein the virtual address bar comprises: a plurality of segments, where each interactive segment corresponds to a filter for selecting items to display. 91. A computer-implemented method for enabling the use of third-party previewers in a shell browser that supports multiple object types, comprising: providing a shell browser that has a default pre-browser for multiple item types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple item types. 92. The method of claim 91 wherein a user selectable filter is provided on the screen to filter items based on the metadata property specified by the filter. 93. The method of claim 91 characterized in that a quick link is provided on the screen that the user can select to view a specific collection of items. 94. The method of claim 91 wherein a library is provided that includes a collection of items and a set of tools for managing items in the library. 95. The method of claim 91 characterized in that the objects in the virtual map can be physically stored in memories at different physical locations. 96. The method of claim 95 wherein the different physical locations comprise the present computer and at least one of the different computer, network location, and external storage device. 97. The method of claim 91 characterized in that the objects contain both file objects and non-file objects. 98. The method of claim 97 characterized in that the non-file objects contain at least one of the contacts or e-mail messages. 99. The method of claim 91 further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive segments of the virtual address bar, each additional interactive segment further restricting the objects referenced by the previous interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 100. The method of claim 91 further comprising providing user interface control of a virtual address bar for selecting items available to the computer system for display, wherein the virtual address bar comprises: a plurality of interactive segments, where each interactive segment corresponds to a filter for selecting items to display. 101. In a computer system having a screen and memory for storing items, wherein the items are a plurality of different types, a method for displaying item libraries is characterized in that it contains: providing libraries that will contain items of similar types; and providing a similar set of UI capabilities for each of the libraries. 102. The method of claim 101 wherein the different types contain at least two of documents, images and music. 103. The method of claim 101 wherein the similar set of UI capabilities includes the ability to change. 104. The method of claim 101, wherein a similar set of UI capabilities includes the ability to create new categories. 105. The method of claim 101 characterized in that a similar set of UI capabilities includes the ability to change item metadata. 106. The method of claim 101 wherein the similar set of UI capabilities includes the ability to change the pivot. 107. The method of claim 101, characterized in that, in addition to containing objects of similar types, the libraries may also contain objects of different types. 108. The method of claim 101 further comprising a shell browser method for enabling a user to modify metadata within the shell browser, wherein the shell browser method comprises: showing plural subjects; receiving a first input from the user representing a selection of at least one displayed item; displaying metadata associated with at least one displayed item; and providing control for user modification of displayed metadata. 109. The method of claim 101 further comprising providing a shell viewer, wherein the shell viewer comprises: a window displaying a group of items, wherein the window also displays metadata values associated with one or more displayed items; and a change control that allows the user to change at least part of the metadata values displayed in the window. 110. The method of claim 101 further comprising a preview-browser method for enabling the use of third-party preview-browsers in a shell browser that supports multiple object types, wherein the preview-browser method comprises: providing a shell browser that has a default pre-browser for multiple item types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple object types. 111. The method of claim 101 further comprising providing a shell viewer configured to display a plurality of objects representing multiple object types, wherein the shell viewer comprises: a default previewer that provides a standard level of functionality for multiple item types; and an extensibility mechanism that provides functionality beyond the standard level provided by the default previewer for one or more of multiple object types. 112. The method of claim 101 further comprising a virtual address bar method for providing a virtual path to objects stored in a computer file system, wherein the virtual address bar comprises: displaying a virtual address bar capable of including a first interactive segment, wherein the first interactive segment references items on the computer file system according to an appropriate item selection filter; and adding one or more additional interactive segments of the virtual address bar, each additional interactive segment further restricting the objects referenced by the previous interactive segments; the first interactive segment and one or more additional interactive segments constitute a virtual path. 113. The method of claim 101 further comprising providing user interface control of a virtual address bar for selecting items available to the computer system for display, wherein the virtual address bar comprises: a plurality of interactive segments, where each interactive segment corresponds to a filter for selecting items to display. 114. The method from claim 101 characterized in that it further contains a method for filtering objects, wherein the method for filtering objects contains: providing a plurality of screen objects on the screen each representing one or more objects; filtering items represented by screen objects based on a filtering condition; and changing the screen objects that are rendered on the screen to represent the objects that remain after filtering the objects. 115. The method from claim 101 characterized in that it further contains a method for displaying objects, wherein the method for displaying objects contains: determining a range of physical memory locations from which to retrieve objects, wherein the range contains the memory of the present computer and at least one other physical location; receiving queries and, in response to the query, retrieving items from physical locations as determined by the scope; and presenting the items retrieved from the query in the view on the screen. 116. The method from claim 101 characterized in that it further contains a method for presenting the object to the user, wherein the method for presenting the object to the user contains: providing a database that allows both non-file objects and file objects to be searched by query; receiving queries and, in response to the query, retrieving both non-file objects and file objects that satisfy the query; and displaying both non-file items and file items that satisfy the query on the screen. 117. A computer-implemented method for enabling the use of third-party previewers in a shell browser that supports multiple object types, comprising: providing a shell browser that has a default pre-browser for multiple item types; and providing an extensibility mechanism that allows third parties to develop an alternative previewer for at least one of the multiple item types. 118. The method of claim 101, wherein a user-selectable filter is provided on the screen to filter items based on a metadata property determined by the filter. 119. The method of claim 101 wherein a quick link is provided on the screen that the user can select to view a specific collection of items. 120. The method of claim 101 wherein a library is provided that includes a collection of items and a set of tools for managing items in the library. 121. The method of claim 101 characterized in that the objects in the virtual map can be physically stored in memories at different physical locations. 122. The method of claim 121 wherein the different physical locations comprise the present computer and at least one of the different computer, network location, and external storage device. 123. The method of claim 101 characterized in that the objects contain both file objects and non-file objects. 124. The method of claim 123 characterized in that the non-file items contain at least one of the contacts or e-mail messages.