# Patent

## Title
Trusted index structure in a network environment

## Abstract

Methods and apparatuses of a trusted index structure in a network environment. In one embodiment, a data processing system includes a master device and at least one slave device to communicate with each other through a network; and a master lock status of a shared storage device to determine the master device.

## Background
PRIORITY
This application is a continuation-in-part of co-pending U.S. patent application Ser. No. 10/877,584, filed on Jun. 25, 2004. This application also claims priority to co-pending U.S. Provisional Patent Application No. 60/643,087 filed on Jan. 7, 2005, which provisional application is incorporated herein by reference in its entirety; this application claims the benefit of the provisional's filing date under 35 U.S.C. §119(e). This present application hereby claims the benefit of these earlier filing dates under 35 U.S.C. §120.


COPYRIGHT NOTICE
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
FIELD
Various embodiments relate to devices communicating within a network. More particularly, embodiments relate to methods and apparatuses of an index structure in a network environment.
BACKGROUND
A modern data processing system such as a general purpose computer system, often includes a file management system (e.g., as part of an operating system) which allows a user to place a file (e.g., a word processing program file, and/or an image processing program file, etc.) in various directories or subdirectories (e.g. folders) and allows the user to give the file a name. Further, the file management system often allows the user to find the file by searching within a published data (e.g., announced by an application to the file management system) about a file (e.g., a file's name, and/or a date of creation, and/or a date of modification, and/or a type of file). An example of the file management system is a Finder program which operates on Macintosh computers from Apple Computer, Inc. of Cupertino, Calif. Another example of the file management system program is a Windows Explorer program which operates on the Windows operating system from Microsoft Corporation of Redmond, Wash.
Both the Finder program and the Windows Explorer program include a find command that allows the user to search for files by querying the published data. However, this search capability searches through the published data which is the same for each file, regardless of the type of file. Thus, for example, the published data for a Microsoft Word file is the same as the published data for an Adobe PhotoShop file, and the published data often includes the file name, the type of file, the date of creation, the date of last modification, the size of the file, and certain other parameters which may be maintained for the file by the file management system.
Certain application programs internally maintain data about a particular file (e.g., an internally maintained meta-data). The internally maintained meta-data may be considered meta-data because it is data about other data. The internally maintained meta-data for a particular file may include information that is used when a particular application program is executed. For example, the user may add and/or edit meta-data (e.g., through a “properties” tab, such as whether an image shows a person's likeness, etc.).
However, in existing systems, a user is not able to search for the internally maintained meta-data across a variety of different applications using one search request from the user because the internally maintained meta-data is not published to the file management system. In addition, when a shared storage system is used (e.g., a network based file system), a file management system of each of the nodes (e.g., the data processing systems) is unable to search the internally maintained meta-data of files associated with other nodes because of numerous technical challenges. These technical challenges include how to ensure that an index within each file management system is up to date when different computers connected to the shared file system access, modify, and create data (e.g., the published data and/or the internally maintained meta-data) within the shared storage system, how to prevent bottlenecking because of large data transfers of new indexes, and which node manages a master list of changes, etc.
SUMMARY OF THE DESCRIPTION
Apparatuses and methods of a trusted index structure in a network environment are described in various aspects. In one aspect, a data processing system includes a master device and at least one slave device to communicate with each other through a network; and a master lock status of a shared storage device to determine the master device based on an algorithm. The algorithm may be at least one of a heartbeat messaging, a first-in-time assertion, and/or a preferred client analysis. In addition, the master lock status may be claimed by a slave device if the current master device is disabled or relinquishes the master lock.
A shared storage volume of the shared storage device may also have a content structure, a trusted index structure, and a master list of changes generated by the master device. The master device may intermittently update the trusted index structure of the shared storage volume with entries in the master list of changes. The master list of changes may be generated by scanning the at least one slave list of changes intermittently for published change list entries. The trusted index structure may reference both a meta-data library and a content library of the content structure. The meta-data library may include internally maintained meta-data and published meta-data. The meta-data library may also include a new meta-data generated based on business rules. The master list of changes may include changes made to various content files by different slave devices.
The various content files may be created by different application programs and may include different internally maintained meta-data. The content structure may be searched for particular ones of the internally maintained meta-data, the content, the published meta-data, and the new meta-data. A first notification module of each of the at least one slave device may notify the master device when a change-list entry is published by any of the at least one slave device. A second notification module of the master device may notify each of the at least one slave devices when the master list of changes is published by the master device. Each of the at least one slave devices may include a search module, a local index data structure, a meta extractor module, a change-list management module, a change-list structure, a notification module, and a prioritization module. A change-list generator of the change-list management module of a particular slave device of the at least one slave device may create a change-list entry in the change-list structure of the particular slave device based on an operation to a content file by the particular slave device.
A change-list updater of the change-list management module may update the local index structure when a particular slave device of the at least one slave device receives the master list of changes from the master device. The prioritization module may separate, within the change-list structure, change-list entries of at least two sessions of the master device based on physical station addresses associated with each of the at least two sessions. The meta-data extractor module may update the local index data structure with internally maintained meta-data, content, and published meta-data of a particular content file modified by at least a particular slave device.
In another aspect, a method of a slave device includes performing an operation on a content file associated with the slave device; receiving notification of changes to the content file; generating a change-list packet of the received notification; and writing the change-list packet to a shared storage device. The method of the slave device may also include transforming into a master device when the slave device transmits a signal to a master lock status of the shared storage device before other slave devices and when the master lock status is unlocked. The master lock status may use an algorithm chosen from a group including at least one of a heartbeat messaging, a first-in-time assertion, and a preferred client analysis to determine whether the slave device becomes the master device.
The master device may intermittently transmit a master list of changes to replace a trusted index structure of the shared storage device. The content file may be stored on the shared storage device, along with other content files modifiable by other slave devices. The method of the slave device may also automatically generate a new meta-data based on at least one business rule. The notification may include changes to the new meta-data as well as changes to internally maintained meta-data and published meta-data. In addition, the shared storage device may be searched for particular ones of the new meta-data, the internally maintained meta-data, and the published meta-data. Notifications from the master device may be received when a master list of changes is published.
In a further aspect, a method of a master device includes processing at least one change list entry generated by at least one slave device, updating a master list of changes based upon the at least one change list entry, optionally prioritizing entries in the master list of changes based upon an algorithm, and updating a trusted index structure intermittently.
In yet a further aspect, a method includes updating, by a slave device, a change list; publishing, by the slave device, the change list into at least one slave list of changes; intermittently scanning, by a master device, the at least one slave list of changes to find published change lists; publishing, by the master device, a master list of changes by collecting each of the published change lists; updating, by the master device, a trusted index structure with the master list of changes; periodically scanning, by the slave device, the master list of changes to see if there are any changes to the master list of changes; and retrieving, by the slave device, the master list of changes when there are changes to the master list of changes and updating a local meta database and a local index database of the slave device.
The method may include transforming the slave device into a new master device when the slave device transmits a signal to a master lock status of a shared storage device before other slave devices and when the master device is disabled. The master device may intermittently transmit a master list of changes to replace a trusted index structure of a shared storage device. The trusted index structure may be provided to new slave devices associated with the master device. The shared storage device may have no search management capability within its operating system and may be merely a network storage device. The slave device may receive notifications from the master device when a master list of changes is published. The publishing by the slave device and the publishing by the master device may be performed by removing a prefix in front of a file name or by otherwise modifying a file's name.
In yet another aspect, a method determines that there are multiple sessions associated with a profile of a master device; and segregates each session of the multiple sessions in a master list of changes by identifying each session based on unique identifiers associated with each of the multiple sessions. The master device may intermittently transmit a master list of changes to the shared storage device to replace a trusted index of the shared storage device.
The present invention describes systems, methods, and machine-readable media of varying scope. In addition to the aspects of the present invention described in this summary, further aspects of the invention will become apparent by reference to the drawings and by reading the detailed description that follows.



BRIEF DESCRIPTION OF THE DRAWINGS
The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.
FIG. 1 shows an exemplary embodiment of a data processing system, which may be a general purpose computer system and which may operate in any of the various methods described herein.
FIG. 2 shows a general example of one exemplary method of one aspect of the invention.
FIG. 3A shows an example of the content of the particular type of meta-data for a particular type of file.
FIG. 3B shows another example of a particular type of meta-data for another particular type of file.
FIG. 4 shows an example of an architecture for managing meta-data according to one exemplary embodiment of the invention.
FIG. 5 is a flowchart showing another exemplary method according to one embodiment of the invention.
FIG. 6 shows an example of a storage format which utilizes a flat file format for meta-data according to one exemplary embodiment of the invention.
FIGS. 7A-7E show a sequence of graphical user interfaces provided by one exemplary embodiment in order to allow searching of meta-data and/or other data in a data processing system.
FIGS. 8A and 8B show two examples of formats for displaying search results according to one exemplary embodiment of the invention.
FIG. 9 shows another exemplary user interface of the present invention.
FIG. 10 shows another exemplary user interface of the present invention.
FIGS. 11A-11D show, in sequence, another exemplary user interface according to the present invention.
FIGS. 12A-12D show alternative embodiments of user interfaces according to the present invention.
FIGS. 13A and 13B show further alternative embodiments of user interfaces according to the present invention.
FIGS. 14A-14D show further alternative embodiments of user interfaces according to the present invention.
FIGS. 15A-15D show another alternative embodiment of user interfaces according to the present invention.
FIGS. 16A and 16B show certain aspects of embodiments of user interfaces according to the present invention.
FIG. 17 shows an aspect of certain embodiments of user interfaces according to the present invention.
FIGS. 18A and 18B show further aspects of certain embodiments of user interfaces according to the present invention.
FIGS. 19A-19E show further illustrative embodiments of user interfaces according to the present invention.
FIG. 20 is a flow chart which illustrates another exemplary method of the present invention.
FIG. 21 is a flow chart showing another exemplary method of the present invention.
FIGS. 22A-22D illustrate the display of a display device on which an embodiment of the method of FIG. 21 is performed.
FIG. 23 is a block diagram of a network environment in which a number of client devices are communicating with a shared storage device having a master lock status, and a shared storage volume having a content structure, a trusted index structure, a master list of changes and at least one slave list of changes, according to one embodiment.
FIG. 24 is a process flow of a one of the slave device(s) of FIG. 23 transforming into a master device through assertion of the master lock status of FIG. 23, according to one embodiment.
FIG. 25 is a process flow of a slave device generating a change-list entry based on an operation to a data of the slave device, according to one embodiment.
FIG. 26 is a process flow of the master device updating a trusted index structure intermittently (e.g., twice a day), according to one embodiment.
FIG. 27A is a process follow of a slave device publishing a change list, according to one embodiment.
FIG. 27B is a process flow of a master device updating a trusted index structure with a master list of changes generated from published slave change lists as described in FIG. 27A, according to one embodiment.
FIG. 27C is a process flow of a slave device updating a local meta-data database and a local index database from the master list of changes of FIG. 27B, according to one embodiment.
FIG. 28 is a process flow of the shared storage device managing at least two active sessions of the master device by generating separate change-list entries based on a physical station address, according to one embodiment.
FIG. 29 is a data structure view of a change-list entry, according to one embodiment.



DETAILED DESCRIPTION
Methods and apparatuses for processing meta-data are described herein. In the following description, numerous details are set forth to provide a more thorough explanation of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form, rather than in detail, in order to avoid obscuring the present invention.
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification do not necessarily all refer to the same embodiment.
FIG. 1 shows one example of a typical computer system which may be used with the present invention. Note that while FIG. 1 illustrates various components of a computer system, it is not intended to represent any particular architecture or manner of interconnecting the components as such details are not germane to the present invention. It will also be appreciated that network computers and other data processing systems which have fewer components or perhaps more components may also be used with the present invention. The computer system of FIG. 1 may, for example, be a Macintosh computer from Apple Computer, Inc.
As shown in FIG. 1, the computer system 101, which is a form of a data processing system, includes a bus 102 which is coupled to a microprocessor(s) 103 and a ROM (Read Only Memory) 107 and volatile RAM 105 and a non-volatile memory 106. The microprocessor 103 may be a G3 or G4 microprocessor from Motorola, Inc. or one or more G5 microprocessors from IBM. The bus 102 interconnects these various components together and also interconnects these components 103, 107, 105, and 106 to a display controller and display device 104 and to peripheral devices such as input/output (I/O) devices which may be mice, keyboards, moderns, network interfaces, printers and other devices which are well known in the art. Typically, the input/output devices 109 are coupled to the system through input/output controllers 108. The volatile RAM (Random Access Memory) 105 is typically implemented as dynamic RAM (DRAM) which requires power continually in order to refresh or maintain the data in the memory. The mass storage 106 is typically a magnetic hard drive or a magnetic optical drive or an optical drive or a DVD RAM or other types of memory systems which maintain data (e.g. large amounts of data) even after power is removed from the system. Typically, the mass storage 106 will also be a random access memory although this is not required. While FIG. 1 shows that the mass storage 106 is a local device coupled directly to the rest of the components in the data processing system, it will be appreciated that the present invention may utilize a non-volatile memory which is remote from the system, such as a network storage device which is coupled to the data processing system through a network interface such as a modern or Ethernet interface. The bus 102 may include one or more buses connected to each other through various bridges, controllers and/or adapters as is well known in the art. In one embodiment the I/O controller 108 includes a USB (Universal Serial Bus) adapter for controlling USB peripherals and an IEEE 1394 controller for IEEE 1394 compliant peripherals.
It will be apparent from this description that aspects of the present invention may be embodied, at least in part, in software. That is, the techniques may be carried out in a computer system or other data processing system in response to its processor, such as a microprocessor, executing sequences of instructions contained in a memory, such as ROM 107, RAM 105, mass storage 106 or a remote storage device. In various embodiments, hardwired circuitry may be used in combination with software instructions to implement the present invention. Thus, the techniques are not limited to any specific combination of hardware circuitry and software nor to any particular source for the instructions executed by the data processing system. In addition, throughout this description, various functions and operations are described as being performed by or caused by software code to simplify description. However, those skilled in the art will recognize what is meant by such expressions is that the functions result from execution of the code by a processor, such as the microprocessor 103.
Capturing and Use of Meta-Data Across a Variety of Application Programs
FIG. 2 shows a generalized example of one embodiment of the present invention. In this example, captured meta-data is made available to a searching facility, such as a component of the operating system which allows concurrent searching of all meta-data for all applications having captured meta-data (and optionally for all non-meta-data of the data files). The method of FIG. 2 may begin in operation 201 in which meta-data is captured from a variety of different application programs. This captured meta-data is then made available in operation 203 to a searching facility, such as a file management system software for searching. This searching facility allows, in operation 205, the searching of meta-data across all applications having captured meta-data. The method also provides, in operation 207, a user interface of a search engine and the search results which are obtained by the search engine. There are numerous possible implementations of the method of FIG. 2. For example, FIG. 5 shows a specific implementation of one exemplary embodiment of the method of FIG. 2. Alternative implementations may also be used. For example, in an alternative implementation, the meta-data may be provided by each application program to a central source which stores the meta-data for use by searching facilities and which is managed by an operating system component, which may be, for example, the meta-data processing software. The user interface provided in operation 207 may take a variety of different formats, including some of the examples described below as well as user interfaces which are conventional, prior art user interfaces. The meta-data may be stored in a database which may be any of a variety of formats including a B tree format or, as described below, in a flat file format according to one embodiment of the invention.
The method of FIG. 2 may be implemented for programs which do not store or provide meta-data. In this circumstance, a portion of the operating system provides for the capture of the meta-data from the variety of different programs even though the programs have not been designed to provide or capture meta-data. For those programs which do allow a user to create meta-data for a particular document, certain embodiments of the present invention may allow the exporting back of captured meta-data back into data files for applications which maintain meta-data about their data files.
The method of FIG. 2 allows information about a variety of different files created by a variety of different application programs to be accessible by a system wide searching facility, which is similar to the way in which prior art versions of the Finder or Windows Explorer can search for file names, dates of creation, etc. across a variety of different application programs. Thus, the meta-data for a variety of different files created by a variety of different application programs can be accessed through an extension of an operating system, and an example of such an extension is shown in FIG. 4 as a meta-data processing software which interacts with other components of the system and will be described further below.
FIGS. 3A and 3B show two different meta-data formats for two different types of data files. Note that there may be no overlap in any of the fields; in other words, no field in one type of meta-data is the same as any field in the other type of meta-data. Meta-data format 301 may be used for an image file such as a JPEG image file. This meta-data may include information such as the image's width, the image's height, the image's color space, the number of bits per pixel, the ISO setting, the flash setting, the F/stop of the camera, the brand name of the camera which took the image, user-added keywords and other fields, such as a field which uniquely identifies the particular file, which identification is persistent through modifications of the file. Meta-data format 331 shown in FIG. 3B may be used for a music file such as an MP3 music file. The data in this meta-data format may include an identification of the artist, the genre of the music, the name of the album, song names in the album or the song name of the particular file, song play times or the song play time of a particular song and other fields, such as a persistent file ID number which identifies the particular MP3 file from which the meta-data was captured. Other types of fields may also be used. The following chart shows examples of the various fields which may be used in meta-data for various types of files.





























Copied



Item
Parent in



Multi-

User

with
App


name
hierarchy
Attribute name
Description/Notes
CFType
value
Localized
settable
Gettable
copy
viewable







Item
n/a
Authors
Who created or
CFString
Yes
No
Yes
Yes
Yes
Address





contributed to the






Book





contents of this item




Comment
A free form text
CFString
No
No
Yes
Yes
Yes





comment




ContentType
This is the type that is
CFString
No
?
No
Yes
Yes





determined by UTI




ContentTypes
This is the inheritance of
CFString
Yes
?
No
Yes
Yes





the UTI system




CreatedDate
When was this item
CFDate
No
No
No
Yes
Yes





created




DisplayName
The name of the item as
CFString
No
Yes
Yes
Yes
Yes
Finder (or





the user would like to






Launch





read it. Very well may






Services)





be the file name, but it





may also be the subject





of an e-mail message or





the full name of a





person, for example.




Keywords
This is a list words set
CFString
Yes
System-
Yes
Yes
Ask





by the user to identify


provided





arbitrary sets of


keywords





organization. The scope


(if any)





is determined by the





user and can be flexibly





used for any kind of





organization. For





example, Family,





Hawaii, Project X, etc.




Contact
A list of contacts that
CFString
Yes
No
Yes
Yes
Ask
Address




Keywords
are associated with this






Book





document, beyond what





is captured as Author.





This may be a person





who's in the picture or a





document about a





person or contact





(performance review,





contract)




ModifiedDate
When this item was last
CFDate
No
No
No
Yes





modified




Rating
A relative rating (0 to 5
CFNumber
No
n/a
Yes
Yes





value) on how important a





particular item is to you,





whether it's a person, file





or message




RelatedTos
A list of other items that
CFString
Yes
No
Yes
Yes





are arbitrarily grouped





together.




TextContent
An indexed version of any
CFString
No
No
No
Yes





content text




UsedDates
Which days was the
CFDate
Yes
No
No
Yes





document





opened/viewed/played


Content/
Item
Copyright
Specifies the owner of this
CFString
No
No
Yes
Yes


Data


content, i.e. Copyright





Apple Computer, Inc.




CreatorApp
Keeps track of the
CFString
No
?
No
Yes





application that was used





to create this document (if





it's known).




Languages
The languages that this
CFString
Yes
Yes
Yes
Yes





document is composed in





(for either text or audio-





based media)




ParentalControl
A field that is used to
CFString
No
?
Yes
Yes





determine whether this is





kid-friendly content or not




Publishers
The name or a person or
CFString
Yes
No
Yes
Yes

Address





organization that






Book





published this content.




PublishedDate
The original date that this
CFDate
No
No
Yes
Yes





content was published (if





it was), independent of





created date.




Reviewers
A list of contacts who
CFString
Yes
No
Yes
Yes

Address





have reviewed the contents






Book





of this file. This would





have to be set explicitly by





an application.




ReviewStatus
Free form text that used to
CFString
No
?
Yes
Yes





specify where the





document is in any





arbitrary review process




TimeEdited
Total time spent editing
CFDate
No
No
No
Yes





document




WhereTos
Where did this go to, eg.
CFString
Yes
System-
?
Yes





CD, printed, backedup


provided








words








only








(if any)




WhereFroms
Where did this come from,
CFString
Yes
System-
?
Yes





e.g. camera, email, web


provided





download, CD


words








only








(if any)


Image
Data
BitsPerSample
What is the bit depth of
CFNumber
No


Yes





the image (8-bit, 16-bit,





etc.)




ColorSpace
What color space model is
CFString
No


Yes

ColorSync





this document following






Utility?




ImageHeight
The height of the image in
CFNumber
No


Yes





pixels




ImageWidth
The width of the image in
CFNumber
No


Yes





pixels




ProfileName
The name of the color
CFString
No


Yes

ColorSync





profile used with for






Utility?





image




Resolution-
Resolution width of this
CFNumber
No


Yes




Width
image (i.e. dpi from a





scanner)




Resolution-
Resolution height of this
CFNumber
No


Yes




Height
image (i.e. dpi from a





scanner)




LayerNames
For image formats that
CFString
Yes


Yes





contain “named” layers





(e.g. Photoshop files)




Aperture
The f-stop rating of the
CFNumber
No


Yes





camera when the image





was taken




CameraMake
The make of the camera
CFString
No
Yes

Yes





that was used to acquire





this image (e.g. Nikon)




CameraModel
The model of the camera
CFString
No
Yes

Yes





used to acquire this image





(Coolpix 5700)




DateTime-
Date/time the picture was
CFDate
No


Yes




Original
taken




ExposureMode
Mode that was used for
CFString
No


Yes





the exposure




ExposureTime
Time that the lens was
CFDate
No


Yes





exposed while taking the





picture




Flash
This attribute is
CFNumber
No


Yes





overloaded with





information about red-eye





reduction. This is not a





binary value




GPS
Raw value received from
CFString
No


Yes





GPS device associated





with photo acquisition. It





hasn't necessarily been





translated to a user-





understandable location.




ISOSpeed
The ISO speed the camera
CFNumber
No


Yes





was set to when the image





was acquired




Orientation
The orientation of the
CFString
No


Yes





camera when the image





was acquired




WhiteBalance
The white balance setting
CFNumber
No


Yes





of the camera when the





picture was taken




EXIFversion
The version of EXIF that
CFString
No


Yes





was used to generate the





meta-data for the image


Time-
Data
Acquisition-
The name or type of
CFString
Yes


Yes


based

Sources
device that used to acquire





the media




Codecs
The codecs used to
CFString
Yes


Yes





encode/decode the media




DeliveryType
FastStart or RTSP
CFString
No


Yes




Duration
The length of time that the
CFNumber
No


Yes





media lasts




Streamable
Whether the content is
CFBoolean
No


Yes





prepared for purposes of





streaming




TotalBitRate
The total bit rate (audio &
CFNumber
No


Yes





video combined) of the





media.




AudioBitRate
The audio bit rate of the
CFNumber
No


Yes





media




AspectRatio
The aspect ratio of the
CFString
No


Yes





video of the media




ColorSpace
The color space model
CFString
No


Yes





used for the video aspect





of the media




FrameHeight
The frame height in pixels
CFNumber
No


Yes





of the video in the media




FrameWidth
The frame width in pixels
CFNumber
No


Yes





of the video in the media




ProfileName
The name of the color
CFString
No


Yes





profile used on the video





portion of the media




VideoBitRate
The bit rate of the video
CFNumber
No


Yes





aspect of the media


Text
Data
Subject
The subject of the text.
CFString
No


Yes





This could be meta-data





that's supplied with the





text or something





automatically generated





with technologies like





VTWIN




PageCount
The number of printable
CFNumber
No


Yes





pages of the document




LineCount
The number of lines in the
CFNumber
No


Yes





document




WordCount
The number of words in
CFNumber
No


Yes





the document




URL
The URL that will get you
CFString
No


Yes





to this document (or at





least did at one time).





Relevant for saved HTML





documents, bookmarks,





RSS feeds, etc.




PageTitle
The title of a web page.
CFString
No


Yes





Relevant to HTML or





bookmark documents




Google
Structure of where this
CFString
No


Yes




Hierarchy
page can be found in the





Google hierarchy.





Relevant to HTML or





bookmark documents


Compound
Data
<Abstract>
There are no specific
n/a
n/a
n/a
n/a
n/a
n/a
n/a


document


attributes assigned to this





item. This is to catch all





app-specific file formats





that fall within Data, but





don't fit into any of the





other types. Typically





these documents have





multiple types of media





embedded within them.





(e.g. P


PDF
Compound
NumberOf-
The number of printable
CFNumber
No


Yes



document
Pages
pages in the document




PageSize
The size of the page stored
CFNumber
No

No
Yes





as points




PDFTitle
PDF-specific title meta-
CFString
No

?
Yes





data for the document




PDFAuthor
PDF-specific author meta-
CFString
No

?
Yes

Address





data for the document






Book




PDFSubject
PDF-specific subject
CFString
No

?
Yes





meta-data for the





document




PDFKeywords
PDF-specific keywords
CFString
Yes

?
Yes





meta-data for the





document




PDFCreated
PDF-specific created
CFDate
No

?
Yes





meta-data for the





document




PDFModified
PDF-specific modified
CFDate
No

?
Yes





meta-data for the





document




PDFVersion
PDF-specific version
CFString
No

?
Yes





meta-data for the





document




Security-
Method by which this
CFString
No


Yes




Method
document is kept secure


Presentation
Compound
SlideTitles
A collection of the titles
CFString
Yes


Yes


(Keynote)
document

on slides




SlideCount
The number of slides
CFString
No


Yes




SpeakerNotes-
The content of all the
CFString
?


Yes




Content
speaker notes from all of





the slides together


Application
Item
Categories
The kind of application
CFString
Yes


Yes





this is: productivity,





games, utility, graphics,





etc. A set list that


Message
Item
Recipients
Maps to To and Cc:
CFString
Yes


Yes

Address





addresses in a mail






Book





message.




Priority
The priority of the
CFString
No


Yes





message as set by the





sender




Attachment-
The list of filenames that
CFString
Yes


Yes




Names
represent attachments in a





particular message (should





be actionable within the





Finder)




Authors
maps to From address in
CFString
Yes
No
Yes
Yes
Yes
Address





mail message






Book




Comment
Not applicable to Mail
CFString
No
No
Yes
Yes
Yes





right now (should we





consider?)




ContentType

CFString
No

No
Yes
Yes




ContentTypes

CFString
Yes

No
Yes
Yes




CreatedDate
When was this message
CFDate
No
No
No
Yes
Yes





was sent or received




DisplayName
Subject of the message
CFString
No
Yes
Yes
Yes
Yes




Keywords
There will be a way to set
CFString
Yes
System-
Yes
Yes
Ask





keywords within Mail


provided








keywords








(if any)




Contact
Could be where recipients
CFString
Yes
No
Yes
Yes
Ask
Address




Keywords
are held






Book




ModifiedDate
Not applicable
CFDate
No
No
No
Yes




Rating
A relative rating (0 to 5
CFNumber
No
n/a
Yes
Yes





stars) on how important a





particular message is to





you (separate from a





message's Priority)




RelatedTos
Potentially threaded
CFString
Yes
No
Yes
Yes





messages could be put into





this category




TextContent
An indexed version of the
CFString
No
No
No
Yes





mail message




UsedDates
The day/time in which the
CFDate
Yes
No
No
Yes





mail message was





viewed/read


Contact
Item
Company
The company that this
CFString
No


Yes

Address





contact is an employee of






Book




E-mails
A list of e-mail addresses
CFString
Yes


Yes

Mail





that this contact has




IMs
A list of instant message
CFString
Yes


Yes

iChat





handles this contact has




Phones
A list of phone numbers
CFString
Yes





that relate to this contact




Addresses
A list of physical
CFString
Yes





addresses that relate to this





person




Authors
the name of the owner of
CFString
Yes
No
Yes
Yes
Yes
Address





the Address Book (current






Book





user name)




Comment

CFString
No
No
Yes
Yes
Yes




ContentType

CFString
No

No
Yes
Yes




ContentTypes

CFString
Yes

No
Yes
Yes




CreatedDate
date the user entered this
CFDate
No
No
No
Yes
Yes





into his AddressBook





(either through import or





direct entry)




DisplayName
Composite name of
CFString
No
Yes
Yes
Yes
Yes





contact (First Name, Last





Name)




Keywords
There will be a way to set
CFString
Yes
System-
Yes
Yes
Ask





keywords within Address


provided





Book


keywords








(if any)




Contact

CFString
Yes
No
Yes
Yes
Ask
Address




Keywords







Book




ModifiedDate
Last time this contact
CFDate
No
No
No
Yes





entry was modified




Rating
A relative rating (0 to 5
CFNumber
No
n/a
Yes
Yes





stars) on how important a





particular contact is to you





(separate from a message's





Priority)




RelatedTos
(potentially could be used
CFString
Yes
No
Yes
Yes





to associate people from





the same company or





family)




TextContent
An indexed version of the
CFString
No
No
No
Yes





Notes section




UsedDates
The day/time in which the
CFDate
Yes
No
No
Yes





contact entry was viewed





in Address Book


Meeting
Item
Body
text, rich text or document
CFString
No


Yes


(TBD)


that represents the full





content of the event




Description
text describing the event
CFString
No


Yes




EventTimes
time/date the event starts
CFDate
Yes


Yes




Duration
The length of time that the
CFNumber
No


Yes





meeting lasts




Invitees
The list of people who are
CFString
Yes


Yes

Address





invited to the meeting






Book




Location
The name of the location
CFString
No


Yes





where the meeting is





taking place









One particular field which may be useful in the various meta-data formats would be a field which includes an identifier of a plug in or other software element which may be used to capture meta-data from a data file and/or export meta-data back to the creator application.
Various different software architectures may be used to implement the functions and operations described herein. The following discussion provides one example of such an architecture, but it will be understood that alternative architectures may also be employed to achieve the same or similar results. The software architecture shown in FIG. 4 is an example which is based upon the Macintosh operating system. The architecture 400 includes a meta-data processing software 401 and an operating system (OS) kernel 403 which is operatively coupled to the meta-data processing software 401 for a notification mechanism which is described below. The meta-data processing software 401 is also coupled to other software programs such as a file system graphical user interface software 405 (which may be the Finder), an email software 407, and other applications 409. These applications are coupled to the meta-data processing software 401 through client application program interface 411 which provide a method for transferring data and commands between the meta-data processing software 401 and the software 405, 407, and 409. These commands and data may include search parameters specified by a user as well as commands to perform searches from the user, which parameters and commands are passed to the meta-data processing software 401 through the interface 411. The meta-data processing software 401 is also coupled to a collection of importers 413 which extract data from various applications. In particular, in one exemplary embodiment, a text importer is used to extract text and other information from word processing or text processing files created by word processing programs such as Microsoft Word, etc. This extracted information is the meta-data for a particular file. Other types of importers extract meta-data from other types of files, such as image files or music files. In this particular embodiment, a particular importer is selected based upon the type of file which has been created and modified by an application program. For example, if the data file was created by PhotoShop, then an image importer for PhotoShop may be used to input the meta-data from a PhotoShop data file into the meta-data database 415 through the meta-data processing software 401. On the other hand, if the data file is a word processing document, then an importer designed to extract meta-data from a word processing document is called upon to extract the meta-data from the word processing data file and place it into the meta-data database 415 through the meta-data processing software 401. Typically, a plurality of different importers may be required in order to handle the plurality of different application programs which are used in a typical computer system. The importers 413 may optionally include a plurality of exporters which are capable of exporting the extracted meta-data for particular types of data files back to property sheets or other data components maintained by certain application programs. For example, certain application programs may maintain some meta-data for each data file created by the program, but this meta-data is only a subset of the meta-data extracted by an importer from this type of data file. In this instance, the exporter may export back additional meta-data or may simply insert meta-data into blank fields of meta-data maintained by the application program.
The software architecture 400 also includes a file system directory 417 for the meta-data. This file system directory keeps track of the relationship between the data files and their meta-data and keeps track of the location of the meta-data object (e.g. a meta-data file which corresponds to the data file from which it was extracted) created by each importer. In one exemplary embodiment, the meta-data database is maintained as a flat file format as described below, and the file system directory 417 maintains this flat file format. One advantage of a flat file format is that the data is laid out on a storage device as a string of data without references between fields from one meta-data file (corresponding to a particular data file) to another meta-data file (corresponding to another data file). This arrangement of data will often result in faster retrieval of information from the meta-data database 415.
The software architecture 400 of FIG. 4 also includes find by content software 419 which is operatively coupled to a database 421 which includes an index of files. The index of files represents at least a subset of the data files in a storage device and may include all of the data files in a particular storage device (or several storage devices), such as the main hard drive of a computer system. The index of files may be a conventional indexed representation of the content of each document. The find by content software 419 searches for words in that content by searching through the database 421 to see if a particular word exists in any of the data files which have been indexed. The find by content software functionality is available through the meta-data processing software 401 which provides the advantage to the user that the user can search concurrently both the index of files in the database 421 (for the content within a file) as well as the meta-data for the various data files being searched. The software architecture shown in FIG. 4 may be used to perform the method shown in FIG. 5 or alternative architectures may be used to perform the method of FIG. 5.
The method of FIG. 5 may begin in operation 501 in which a notification of a change for a file is received. This notification may come from the OS kernel 403 which notifies the meta-data processing software 401 that a file has been changed. This notification may come from sniffer software elements which detect new or modified files and deletion of files. This change may be the creation of a new file or the modification of an existing file or the deletion of an existing file. The deletion of an existing file causes a special case of the processing method of FIG. 5 and is not shown in FIG. 5. In the case of a deletion, the meta-data processing software 401, through the use of the file system directory 417, deletes the meta-data file in the meta-data database 415 which corresponds to the deleted file. The other types of operations, such as the creation of a new file or the modification of an existing file, causes the processing to proceed from operation 501 to operation 503 in which the type of file which is the subject of the notification is determined. The file may be an Acrobat PDF file or an RTF word processing file or a JPEG image file, etc. In any case, the type of the file is determined in operation 503. This may be performed by receiving from the OS kernel 403 the type of file along with the notification or the meta-data processing software 401 may request an identification of the type of file from the file system graphical user interface software 405 or similar software which maintains information about the data file, such as the creator application or parent application of the data file. It will be understood that in one exemplary embodiment, the file system graphical user interface software 405 is the Finder program which operates on the Macintosh operating system. In alternative embodiments, the file system graphical user interface system may be Windows Explorer which operates on Microsoft's Windows operating system. After the type of file has been determined in operation 503, the appropriate capture software (e.g. one of the importers 413) is activated for the determined file type. The importers may be a plug-in for the particular application which created the type of file about which notification is received in operation 501. Once activated, the importer or capture software imports the appropriate meta-data (for the particular file type) into the meta-data database, such as meta-data database 415 as shown in operation 507. Then in operation 509, the meta-data is stored in the database. In one exemplary embodiment, it may be stored in a flat file format. Then in operation 511, the meta-data processing software 401 receives search parameter inputs and performs a search of the meta-data database (and optionally also causes a search of non-meta-data sources such as the index of files 421) and causes the results of the search to be displayed in a user interface. This may be performed by exchanging information between one of the applications, such as the software 405 or the software 407 or the other applications 409 and the meta-data processing software 401 through the interface 411. For example, the file system software 405 may present a graphical user interface, allowing a user to input search parameters and allowing the user to cause a search to be performed. This information is conveyed through the interface 411 to the meta-data processing software 401 which causes a search through the meta-data database 415 and also may cause a search through the database 421 of the indexed files in order to search for content within each data file which has been indexed. The results from these searches are provided by the meta-data processing software 401 to the requesting application which, in the example given here, was the software 405, but it will be appreciated that other components of software, such as the email software 407, may be used to receive the search inputs and to provide a display of the search results. Various examples of the user interface for inputting search requests and for displaying search results are described herein and shown in the accompanying drawings.
It will be appreciated that the notification, if done through the OS kernel, is a global, system wide notification process such that changes to any file will cause a notification to be sent to the meta-data processing software. It will also be appreciated that in alternative embodiments, each application program may itself generate the necessary meta-data and provide the meta-data directly to a meta-data database without the requirement of a notification from an operating system kernel or from the intervention of importers, such as the importers 413. Alternatively, rather than using OS kernel notifications, an embodiment may use software calls from each application to a meta-data processing software which receives these calls and then imports the meta-data from each file in response to the call.
As noted above, the meta-data database 415 may be stored in a flat file format in order to improve the speed of retrieval of information in most circumstances. The flat file format may be considered to be a non-B tree, non-hash tree format in which data is not attempted to be organized but is rather stored as a stream of data. Each meta-data object or meta-data file will itself contain fields, such as the fields shown in the examples of FIGS. 3A and 3B. However, there will typically be no relationship or reference or pointer from one field in one meta-data file to the corresponding field (or another field) in the next meta-data file or in another meta-data file of the same file type. FIG. 6 shows an example of the layout in a flat file format of meta-data. The format 601 includes a plurality of meta-data files for a corresponding plurality of data files. As shown in FIG. 6, meta-data file 603 is meta-data from file 1 of application A and may be referred to as meta-data file A1. Similarly, meta-data file 605 is meta-data from file 1 of application B and may be referred to as meta-data file B1. Each of these meta-data files typically would include fields which are not linked to other fields and which do not contain references or pointers to other fields in other meta-data files. It can be seen from FIG. 6 that the meta-data database of FIG. 6 includes meta-data files from a plurality of different applications (applications A, B, and C) and different files created by each of those applications. Meta-data files 607, 609, 611, and 617 are additional meta-data files created by applications A, B, and C as shown in FIG. 6.
A flexible query language may be used to search the meta-data database in the same way that such query languages are used to search other databases. The data within each meta-data file may be packed or even compressed if desirable. As noted above, each meta-data file, in certain embodiments, will include a persistent identifier which uniquely identifies its corresponding data file. This identifier remains the same even if the name of the file is changed or the file is modified. This allows for the persistent association between the particular data file and its meta-data.
User Interface Aspects
Various different examples of user interfaces for inputting search parameters and for displaying search results are provided herein. It will be understood that some features from certain embodiments may be mixed with other embodiments such that hybrid embodiments may result from these combinations. It will be appreciated that certain features may be removed from each of these embodiments and still provide adequate functionality in many instances.
FIG. 7A shows a graphical user interface which is a window which may be displayed on a display device which is coupled to a data processing system such as a computer system. The window 701 includes a side bar having two regions 703A, which is a user-configurable region, and 703B, which is a region which is specified by the data processing system. Further details in connection with these side bar regions may be found in co-pending U.S. patent application Ser. No. 10/873,661 filed Jun. 22, 2004, and entitled “Methods and Apparatuses for Operating a Data Processing System,” by inventors Donald Lindsay and Bas Ording. The window 701 also includes a display region 705 which in this case displays the results of searches requested by the user. The window 701 also includes a search parameter menu bar 707 which includes configurable pull down menus 713, 715, and 717. The window 701 also includes a text entry region 709 which allows a user to enter text as part of the search query or search parameters. The button 711 may be a start search button which a user activates in order to start a search based upon the selected search parameters. Alternatively, the system may perform a search as soon as it receives any search parameter inputs or search queries from the user rather than waiting for a command to begin the search. The window 701 also includes a title bar 729 which may be used in conjunction with a cursor control device to move, in a conventional manner, the window around a desktop which is displayed on a display device. The window 701 also includes a close button 734, a minimize button 735, and a resize button 736 which may be used to close or minimize or resize, respectively, the window. The window 701 also includes a resizing control 731 which allows a user to modify the size of the window on a display device. The window 701 further includes a back button 732 and a forward button 733 which function in a manner which is similar to the back and forward buttons on a web browser, such as Internet Explorer or Safari. The window 701 also includes view controls which include three buttons for selecting three different types of views of the content within the display region 705. When the contents found in a search exceed the available display area of a display region 705, scroll controls, such as scroll controls 721, 722, and 723, appear within the window 701. These may be used in a conventional manner, for example, by dragging the scroll bar 721 within the scroll region 721A using conventional graphical user interface techniques.
The combination of text entry region 709 and the search parameter menu bar allow a user to specify a search query or search parameters. Each of the configurable pull down menus presents a user with a list of options to select from when the user activates the pull down menu. As shown in FIG. 7A, the user has already made a selection from the configurable pull down menu 713 to specify the location of the search, which in this case specifies that the search will occur on the local disks of the computer systems. Configurable pull down menu 715 has also been used by the user to specify the kind of document which is to be searched for, which in this case is an image document as indicated by the configurable pull down menu 715 which indicates “images” as the selected configuration of this menu and hence the search parameter which it specifies. The configurable pull down menu 717, as shown in FIG. 7A, represents an add search parameter pull down menu. This add search parameter pull down menu allows the user to add additional criteria to the search query to further limit the search results. In the embodiment shown in FIG. 7A, each of the search parameters is logically ANDed in a Boolean manner. Thus the current search parameter specified by the user in the state shown in FIG. 7A searches all local disks for all images, and the user is in the middle of the process of selecting another search criteria by having selected the add search criteria pull down menu 717, resulting in the display of the pull down menu 719, which has a plurality of options which may be selected by the user.
FIG. 7B shows the window 701 after the user has caused the selection of the time option within pull down menu 719, thereby causing the display of a submenu 719A which includes a list of possible times which the user may select from. Thus it appears that the user wants to limit the search to all images on all local disks within a certain period of time which is to be specified by making a selection within the submenu 719A.
FIG. 7C shows the window 701 on the display of a data processing system after the user has selected a particular option (in this case “past week”) from the submenu 719A. If the user accepts this selection, then the display shown in FIG. 7D results in which the configurable pull down menu 718 is displayed showing that the user has selected as part of the search criteria files that have been created or modified in the past week. It can be seen from FIG. 7D that the user can change the particular time selected from this pull down menu 718 by selecting another time period within the pull down menu 718A shown in FIG. 7D. Note that the configurable pull down menu 717, which represents an add search parameter menu, has now moved to the right of the configurable pull down menu 718. The user may add further search parameters by pressing or otherwise activating the configurable pull down menu 717 from the search parameter menu bar 707. If the user decides that the past week is the proper search criteria in the time category, then the user may release the pull down menu 718A from being displayed in a variety of different ways (e.g. the user may release the mouse button which was being depressed to keep the pull down menu 718A on the display). Upon releasing or otherwise dismissing the pull down menu 718A, the resulting window 701 shown in FIG. 7E then appears. There are several aspects of this user interface shown in FIG. 7A-7E which are worthy of being noted. The search parameters or search query is specified within the same window as the display of the search results. This allows the user to look at a single location or window to understand the search parameters and how they affected the displayed search results, and may make it easier for a user to alter or improve the search parameters in order to find one or more files. The configurable pull down menus, such as the add search parameter pull down menu, includes hierarchical pull down menus. An example of this is shown in FIG. 7B in which the selection of the time criteria from the pull down menu 717 results in the display of another menu, in this case a submenu 719A which may be selected from by the user. This allows for a compact presentation of the various search parameters while keeping the initial complexity (e.g. without submenus being displayed) at a lower level. Another useful aspect of the user interface shown in FIG. 7A-7E is the ability to reconfigure pull down menus which have previously been configured. Thus, for example, the configurable pull down menu 713 currently specifies the location of the search (in this case, all local disks), however, this may be modified by selecting the pull down region associated with the configurable pull down menu 713, causing the display of a menu of options indicating alternative locations which may be selected by the user. This can also be seen in FIG. 7D in which the past week option has been selected by the user (as indicated by “past week” being in the search parameter menu bar 707), but a menu of options shown in the pull down menu 718A allows the user to change the selected time from the “past week” to some other time criteria. Another useful aspect of this user interface is the ability to continue adding various search criteria by using the add search criteria pull down menu 717 and selecting a new criteria.
It will also be appreciated that the various options in the pull down menus may depend upon the fields within a particular type of meta-data file. For example, the selection of “images” to be searched may cause the various fields present in the meta-data for an image type file to appear in one or more pull down menus, allowing the user to search within one or more of those fields for that particular type of file. Other fields which do not apply to “images” types of files may not appear in these menus in order reduce the complexity of the menus and to prevent user confusion.
Another feature of the present invention is shown in FIGS. 7A-7E. In particular, the side bar region 703A, which is the user-configurable portion of the side bar, includes a representation of a folder 725 which represents the search results obtained from a particular search, which search results may be static or they may be dynamic in that, in certain instances, the search can be performed again to obtain results based on the current files in the system. The folder 725 in the example shown in FIGS. 7A-7E represents a search on a local disk for all images done on December 10th. By selecting this folder in the side bar region 703A, the user may cause the display in the display region 705 of the results of that search. In this way, a user may retrieve a search result automatically by saving the search result into the side bar region 703A. One mechanism for causing a search result or a search query to be saved into the side bar region 703A is to select the add folder button 727 which appears in the bottom portion of the window 701. By selecting this button, the current search result or search query is saved as a list of files and other objects retrieved in the current search result. In the case where the search query is saved for later use rather than the saving of a search result, then the current search query is saved for re-use at a later time in order to find files which match the search query at that later time. The user may select between these two functionalities (saving a search result or saving a search query) by the selection of a command which is not shown.
FIGS. 8A and 8B show another aspect of a user interface feature which may be used with certain embodiments of the present invention. The window 801 of FIG. 8A represents a display of the search results which may be obtained as a result of using one of the various different embodiments of the present invention. The search results are separated into categories which are separated by headers 805, 807, 809, and 811 which in this case represent periods of time. This particular segmentation with headers was selected by the user's selecting the heading “date modified” using the date modified button 803 at the top of the window 801. An alternative selection of the kind category by selecting the button 802 at the top of the window 801 A shown in FIG. 8B results in a different formatting of the search results which are now categorized by headers which indicate the types of files which were retrieved in the search and are separated by the headings 815, 817, 819, and 821 as shown in FIG. 8B. The use of these headings in the search results display allows the user to quickly scan through the search results in order to find the file.
FIG. 9 shows another aspect of the present invention that is illustrated as part of the window 901 shown in FIG. 9. This window includes a display region 905 which shows the results of the search and the window also includes two side bar regions 903A and 903B, where the side bar region 903A is the user-configurable portion and the side bar region 903B is the system controlled portion. A folder add button 927 may be selected by the user to cause the addition of a search result or a search query to be added to the user-configurable portion of the side bar. The window 901 also includes conventional window controls such as a title bar or region 929 which may be used to move the window around a display and view select buttons 937 and maximize, minimize and resize buttons 934, 935, and 936 respectively. The window 901 shows a particular manner in which the results of a text-based search may be displayed. A text entry region 909 is used to enter text for searching. This text may be used to search through the meta-data files or the indexed files or a combination of both. The display region 905 shows the results of a search for text and includes at least two columns, 917 and 919, which provide the name of the file that was found and the basis for the match. As shown in column 919, the basis for the match may be the author field or a file name or a key word or comments or other data fields contained in meta-data that was searched. The column 921 shows the text that was found which matches the search parameter typed into the text entry field 909. Another column 911 provides additional information with respect to the search results. In particular, this column includes the number of matches for each particular type of category or field as well as the total number of matches indicated in the entry 913. Thus, for example, the total number of matches found for the comments field is only 1, while other fields have a higher number of matches.
FIG. 10 shows certain other aspects of some embodiments of the present invention. Window 1001 is another search result window which includes various fields and menus for a user to select various search parameters or form a search query. The window 1001 includes a display region 1005 which may be used to display the results of a search and a user-configurable side bar portion 1003A and a system specified side bar portion 1003B. In addition, the window 1001 includes conventional scrolling controls such as controls 1021 and 1022 and 1021A. The window further includes conventional controls such as a title bar 1029 which may be used to move the window and view control buttons 1037 and maximize, minimize, and resize buttons 1034, 1035, and 1036. A start search button 1015 is near a text entry region 1009. A first search parameter menu bar 1007 is displayed adjacent to a second search parameter bar 1011. The first search parameter search bar 1007 allows a user to specify the location for a particular search while two menu pull down controls in the second search parameter menu bar 1011 allow the user to specify the type of file using the pull down menu 1012 and the time the file was created or last modified using the menu 1013.
The window 1001 includes an additional feature which may be very useful while analyzing a search result. A user may select individual files from within the display region 1005 and associate them together as one collection. Each file may be individually marked using a specific command (e.g. pressing the right button on a mouse and selecting a command from a menu which appears on the screen, which command may be “add selection to current group”) or similar such commands. By individually selecting such files or by selecting a group of files at once, the user may associate this group of files into a selected group or a “marked” group and this association may be used to perform a common action on all of the files in the group (e.g. print each file or view each file in a viewer window or move each file to a new or existing folder, etc.). A representation of this marked group appears as a folder in the user-configurable portion 1003A. An example of such a folder is the folder 1020 shown in the user-configurable portion 1003A. By selecting this folder (e.g. by positioning a cursor over the folder 1020 and pressing and releasing a mouse button or by pressing another button) the user, as a result of this selection, will cause the display within the display region 1005 of the files which have been grouped together or marked. Alternatively, a separate window may appear showing only the items which have been marked or grouped. This association or grouping may be merely temporary or it may be made permanent by retaining a list of all the files which have been grouped and by keeping a folder 1020 or other representations of the grouping within the user-configurable side bar, such as the side bar 1003A. Certain embodiments may allow multiple, different groupings to exist at the same time, and each of these groupings or associations may be merely temporary (e.g. they exist only while the search results window is displayed), or they may be made permanent by retaining a list of all the files which have been grouped within each separate group. It will be appreciated that the files within each group may have been created from different applications. As noted above, one of the groupings may be selected and then a user may select a command which performs a common action (e.g. print or view or move or delete) on all of the files within the selected group.
FIGS. 11A, 11B, 11C, and 11D show an alternative user interface for allowing a user to input search queries or search parameters. The user interface shown in these figures appears within the window 1101 which includes a user-configurable side bar region 1103A and a system specified side bar region 1103B. The window 1101 also includes traditional window controls such as a window resizing control 1131 which may be dragged in a conventional graphical user interface manner to resize the window, and the window further includes scrolling controls such as controls 1121, 1122, and 1123. The scrolling control 1121 may, for example, be dragged within the scrolling region 1121A or a scroll wheel on a mouse or other input device may be used to cause scrolling within a display region 1105. Further, traditional window controls include the title bar 1129 which may be used to move the window around a desktop which is displayed on a display device of a computer system and the window also includes view buttons 1137 as well as close, minimize, and resize buttons 1134, 1135 and 1136. A back and forward button, such as the back button 1132, are also provided to allow the user to move back and forth in a manner which is similar to the back and forth commands in a web browser. The window 1101 includes a search parameter menu bar 1111 which includes a “search by” pull down menu 1112 and a “sort by” pull down menu 1114. The “search by” pull down menu 1112 allows a user to specify the particular search parameter by selecting from the options which appear in the pull down menu once it is activated as shown in FIG. 11B. In particular, the pull down menu 1113 shows one example of a pull down menu when the “search by” pull down menu 1112 has been activated. The “sort by” pull down menu 1114 allows a user to specify how the search results are displayed within a display region 1105. In the example shown in FIGS. 11A-11D a user has used the “sort by” pull down menu 1114 to select the “date viewed” criteria to sort the search results by. It should also be noted that the user may change the type of view of the search results by selecting one of the three view buttons 1137. For example, a user may select an icon view which is the currently selected button among the view buttons 1137, or the user may select a list view or a column view.
FIG. 11B shows the result of the user's activation of a “search by” pull down menu 1112 which causes the display of the menu 1113 which includes a plurality of options from which the user may choose to perform a search by. It will be appreciated that there are a number of different ways for a user to activate the “search by” pull down menu 1112. One way includes the use of a cursor, such as a pointer on a display which is controlled by a cursor control device, such as a mouse. The cursor is positioned over the region associated with the “search by” menu title (which is the portion within the search parameter menu bar 1111 which contains the words “search by”) and then the user indicates the selection of the menu title by pressing a button, such as a mouse's button, to cause the pull down menu to appear, which in this case is the menu 1113 shown in FIG. 11B. At this point, the user may continue to move the cursor to point to a particular option within the menu, such as the “time” option. This may result in the display of a submenu to the left or to the right of the menu 1113. This submenu may be similar to the submenu 719A or to the menu 1214 shown in FIG. 12A. If the “kind” option is selected in the menu 1113, the submenu may include a generic list of the different kinds of documents, such as images, photos, movies, text, music, PDF documents, email documents, etc. or the list may include references to specific program names such as PhotoShop, Director, Excel, Word, etc. or it may include a combination of generic names and specific names. FIG. 11C shows the result of the user having selected PhotoShop type of documents from a submenu of the “kind” option shown in menu 1113. This results in the display of the search parameter menu bar 1111A shown in FIG. 11C which includes a highlighted selection 1111B which indicates that the PhotoShop type of documents will be searched for. The search parameter menu bar 1111 appears below the search parameter menu bar 1111A as shown in FIG. 11C. The user may then specify additional search parameters by again using the “search by” pull down menu 1112 or by typing text into the text entry field 1109. For example, from the state of the window 1101 shown in FIG. 11C, the user may select the “search by” pull down menu 1112 causing the display of a menu containing a plurality of options, such as the options shown within the menu 1113 or alternative options such as those which relate to PhotoShop documents (e.g. the various fields in the meta-data for PhotoShop type of documents). A combination of such fields contained within meta-data for PhotoShop type documents and other generic fields (e.g. time, file size, and other parameters) may appear in a menu, such as the menu 1113 which is activated by selecting the “search by” pull down menu. The user may then select another criteria such as the time criteria. In this case, the window 1101 displays a new search parameter menu bar 1115 which allows a user to specify a particular time. The user may select one of the times on the menu bar 1115 or may activate a pull down menu by selecting the menu title “time,” which is shown as the menu title 1116. The state of the window 1101 shown in FIG. 11D would then search for all PhotoShop documents created in the last 30 days or 7 days or 2 days or today or at any time, depending on the particular time period selected by the user.
FIGS. 12A, 12B, 12C and 12D show another example of a user interface for allowing the creation of search queries for searching meta-data and other data and for displaying the results of the search performed using a search query. The different implementation shown in FIGS. 12A-12D shows a user interface presentation in a column mode; this can be seen by noting the selection of the column button, which is the rightmost button in the view buttons 1237 shown in FIG. 12A. The window 1201 has two columns 1211 and the display region 1205, while the window 1251 of FIG. 12C has three columns which are columns 1257, 1259, and the display region 1255, and the window 1271 has three columns which are columns 1277, 1279, and the display region 1275.
The window 1201 shown in FIGS. 12A and 12B includes a display region 1205 which shows the results of a search; these results may be shown dynamically as the user enters search parameters or the results may be shown only after the user has instructed the system to perform the search (e.g. by selecting a “perform search” command). The window 1201 includes conventional window controls, such as a resizing control 1231, a scrolling control 1221, a title bar 1229 which may be used to move the window, a window close button, a window minimize button, and a window resize button 1234, 1235, and 1236, respectively. The window 1201 also includes a user-configurable side bar region 1203A and a system specified side bar region 1203B. It can be seen from FIG. 12A that a browse mode has been selected as indicated by the highlighted “browse” icon 1203C in the system specified side bar region 1203B. The window 1201 also includes a text entry region 1209, which a user may use to enter text for a search, and the window 1201 also includes view selector buttons 1237.
A column 1211 of window 1201 allows a user to select various search parameters by selecting one of the options which in turn causes the display of a submenu that corresponds to the selected option. In the case of FIG. 12A, the user has selected the “kind” option 1212 and then has used the submenu 1214 to select the “photos” option from the submenu, resulting in an indicator 1213 (photos) to appear in the column 1211 under the “kind” option as shown in FIG. 12A. It can also be seen that the user has previously selected the “time” option in the column 1211 and has selected from a submenu brought up when the “time” option was selected the “past week” search parameter. When the user has finished making selections of the various options and suboptions from both the column 1112 and any of the corresponding submenus which appear, then the display showed in FIG. 12B appears. Note that the submenus are no longer present and that the user has completed the selection of the various options and suboptions which specify the search parameters. Column 1211 in FIG. 12B provides feedback to the user indicating the exact nature of the search query (in this case a search for all photos dated in the past week), and the results which match the search query are shown in the display region 1205.
FIGS. 12C and 12D show an alternative embodiment in which the submenus which appear on a temporary basis in the embodiment of FIGS. 12A and 12B are replaced by an additional column which does not disappear after a selection is made. In particular, the column 1259 of the window 1251 functions in the same manner as the submenu 1214 except that it remains within the window 1251 after a selection is made (wherein the submenu 1214 is removed from the window after the user makes the selection from the submenu). The column 1279 of window 1271 of FIG. 12D is similar to the column 1259. The window 1251 includes a side bar which has a user-configurable side bar region 1253A and a system defined side bar region 1253B. The system specified side bar region 1253B includes a “browse” selection region 1254 which has a clear button 1258 which the user may select to clear the current search query. The window 1271 of FIG. 12D provides an alternative interface for clearing the search query. The window 1271 also includes a user configurable side bar region 1273A and a system specified side bar region 1273B, but the clear button, rather than being with the “search” region 1274 is at the top of the column 1277. The user may clear the current search parameter by selecting the button 1283 as shown in FIG. 12D.
FIG. 13A shows another embodiment of a window 1301 which displays search results within a display region 1302. The window 1301 may be a closeable, minimizeable, resizeable, and moveable window having a resizing control 1310, a title bar 1305 which may be used to move the window, a text entry region 1306 and a user configurable portion 1303, and a system specified portion 1304. The window 1301 further includes buttons for selecting various views, including an icon view, a list view, and a column view. Currently, the list view button 1316 has been selected, causing the display of the search results in a list view manner within the display region 1302. It can be seen that the text (“button”) has been entered into the text entry region 1306 and this has caused the system to respond with the search results shown in the display region 1302. The user has specified a search in every location by selecting “everywhere” button 1317. Further, the user has searched for any kind of document by selecting the “kind” option from the pull down menu 1315 and by selecting the “any” option in the pull down menu 1319. The where or location slice 1307 includes a “+” button which may be used to add further search parameters, and similarly, the slice 1308 includes a “+” and a “−” button for adding or deleting search parameters, respectively. The slice 1307 further includes a “save” button 1309 which causes the current search query to be saved in the form of a folder which is added to the user configurable portion 1303 for use later. This is described further below and may be referred to as a “smart folder.” The search input user interface shown in FIGS. 13A and 13B is available within, in certain embodiments, each and every window controlled by a graphical user interface file management system, such as a Finder program which runs on the Macintosh or Windows Explorer which runs on Microsoft Windows. This interface includes the text entry region 1306 as well as the slices 1307 and 1308.
The window 1301 shown in FIG. 13B shows the activation of a menu by selecting the search button 1323A, causing a display of a menu having two entries 1323 and 1325. Entry 1323 displays recently performed searches so that a user may merely recall a prior search by selecting the prior search and cause the prior search to be run again. The menu selection 1325 allows the user to clear the list of recent searches in the menu.
FIGS. 14A, 14B, and 14C show examples of another window in a graphical user interface file system, such as the Finder which runs on the Macintosh operating system. These windows show the results of a particular search and also the ability to save and use a smart folder which saves a prior search. The window 1401 shown in FIG. 14A includes a display region 1403, a user configurable region 1405, a smart folder 1406, a system specified region 1407, an icon view button 1409, a list view button 1410, and a column view button 1411. The window 1401 also includes a text entry region 1415 and a location slice 1416 which may be used to specify the location for the search, which slice also includes a save button 1417. Additional slices below the slice 1416 allow the user to specify further details with respect to the search, in this case specifying types of documents which are images which were last viewed this week. The user has set the search parameters in this manner by selecting the “kind” option from the pull down menu 1419 and by selecting the “images” type from the pull down menu 1420 and by selecting the “last viewed” option from pull down menu 1418 and by selecting “this week” from the pull down menu 1422. The user has also selected “everywhere” by selecting the button 1421 so that the search will be performed on all disks and storage devices connected to this system. The results are shown within the display region 1403. The user can then save the search query by selecting the “save” button 1417 and may name the saved search query as “this week's images” to produce the smart folder 1406 as shown in the user configurable portion 1405. This allows the user to repeat this search at a later time by merely selecting the smart folder 1406 which causes the system to perform a new search again, and all data which matches the search criteria will be displayed within the display region 1403. Thus, after several weeks, a repeating of this search by selecting the smart folder 1406 will produce an entirely different list if none of the files displayed in the display region 1403 of FIG. 14A are viewed in the last week from the time in which the next search is performed by selecting the smart folder 1406.
FIG. 14B shows a way in which a user may sort or further search within the search results specified by a saved search, such as a smart folder. In the case of FIG. 14B, the user has selected the smart folder 1406 and has then entered text “jpg” 1425 in the text entry region 1415. This has caused the system to filter or further limit the search results obtained from the search query saved as the smart folder 1406. Thus, PhotoShop files and other files such as TIF files and GIF files are excluded from the search results displayed within the display region 1403 of FIG. 14B because the user has excluded those files by adding an additional search criteria specified by the text 1425 in the text entry region 1415. It can be seen that the “jpg” text entry is ANDed logically with the other search parameters to achieve the search results displayed in the display region 1403. It can also be seen that the user has selected the icon view by selecting the icon view button 1409. Thus, it is possible for a user to save a search query and use it later and to further limit the results of the search query by performing a search on the results of the search query to further limit the search results.
FIG. 14C shows the window 1401 and shows the search results displayed within the display region 1403, where the results are based upon the saved search specified by the smart folder 1406. The user has caused a pull down menu 1427 to appear by selecting the pull down region 1427 A. The pull down region 1427 includes several options which a user may select. These options include hiding the search criteria or saving the search (which is similar to selecting the button 1417) or showing view options or opening the selected file. This allows the user, for example, to hide the search criteria, thereby causing the slice 1416 and the other search parameters to be removed from the window 1401 which is a moveable, resizeable, minimizeable, and closeable window.
FIG. 14D shows an example of a user interface which allows the user to specify the appearance of a smart folder, such as the smart folder 1406.
FIGS. 15A, 15B, 15C, and 15D show an example of a system wide search input user interface and search result user interface. In one particular exemplary embodiment, these user interfaces are available on the entire system for all applications which run on the system and all files and meta-data, and even address book entries within an address book program, such as a personal information manager, and calendar entries within a calendar program, and emails within an email program, etc. In one exemplary embodiment, the system begins performing the search and begins displaying the results of the search as the user types text into a text entry field, such as the text entry field 1507. The search results are organized by categories and are displayed as a short list which is intentionally abbreviated in order to present only a selected number of the most relevant (scored) matches or hits to the search query. The user can ask for the display of all the hits by selecting a command, such as the “show all” command 1509. FIG. 15A shows a portion of a display controlled by a data processing system. This portion includes a menu bar 1502 which has at its far end a search menu command 1505. The user can select the search menu command by positioning a cursor, using a mouse, for example, over the search menu command 1505 and by pressing a button or by otherwise activating or selecting a command. This causes a display of a text entry region 1507 into which a user can enter text. In the example shown in FIG. 15A, which is a portion of the display, the user has entered the text “shakeit” causing the display of a search result region immediately below a “show all” command region 1509 which is itself immediately below the text entry region 1507. It can be seen that the hits or matches are grouped into categories (“documents” and “PDF documents”) shown by categories 1511 and 1513 within the search result region 1503. FIG. 15B shows another example of a search. In this case, a large number of hits was obtained (392 hits), only a few of which are shown in the search result region 1503. Again, the hits are organized by categories 1511 and 1513. Each category may be restricted in terms of the number of items displayed within the search result region 1503 in order to permit the display of multiple categories at the same time within the search result region. For example, the number of hits in the documents category may greatly exceed the available display space within the search result region 1503, but the hits for this category are limited to a predetermined or dynamically determinable number of entries within the search result region 1503 for the category 1511. An additional category, “top hit” is selected based on a scoring or relevancy using techniques which are known in the art. The user may select the “show all” command 1509 causing the display of a window, such as window 1601 shown in FIG. 16A. FIG. 15C shows a display of a graphical user interface of one embodiment of the invention which includes the menu bar 1502 and the search menu command 1505 on the menu bar 1502. FIG. 15D shows another example of the search result region 1503 which appeared after a search of the term “safari” was entered into the text entry region 1507. It can be seen from the search result region 1503 of FIG. 15D that the search results are again grouped into categories. Another search result window 1520 is also shown in the user interface of FIG. 15D. It can be seen that application programs are retrieved as part of the search results, and a user may launch any one of these application programs by selecting it from the search result region, thereby causing the program to be launched.
FIGS. 16A and 16B show examples of search result windows which may be caused to appear by selecting the “show all” command 1509 in FIG. 15A or 15B. Alternatively, these windows may appear as a result of the user having selected a “find” command or a some other command indicating that a search is desired. Moreover, the window 1601 shown in FIGS. 16A and 16B may appear in response to either of the selection of a show all command or the selection of a find command. The window 1601 includes a text entry region 1603, a group by menu selection region 1605, a sort by menu selection region 1607, and a where menu selection region 1609. The group by selection region 1605 allows a user to specify the manner in which the items in the search results are grouped according to. In the example shown in FIG. 16A, the user has selected the “kind” option from the group by menu selection region 1605, causing the search results to be grouped or sorted according to the kind or type of document or file. It can be seen that the type of file includes “html” files, image files, PDF files, source code files, and other types of files as shown in FIG. 16A. Each type or kind of document is separated from the other documents by being grouped within a section and separated by headers from the other sections. Thus, headers 1611, 1613, 1615, 1617, 1619, 1621, and 1623 designate each of the groups and separate one group from the other groups. This allows a user to focus on evaluating the search results according to certain types of documents. Within each group, such as the document groups or the folder groups, the user has specified that the items are to be sorted by date, because the user has selected the date option within the sort by menu region 1607. The user has also specified that all storage locations are to be searched by selecting “everywhere” from the where menu selection region 1609. Each item in the search result list includes an information button 1627 which may be selected to produce the display of additional information which may be available from the system. An example of such additional information is shown in FIG. 17 in which a user has selected the information button 1627 for item 1635, resulting in the display of an image 1636 corresponding to the item as well as additional information 1637. Similarly, the user has selected the information button for another item 1630 to produce the display of an image of the item 1631 as well as additional information 1632. The user may remove this additional information from the display by selecting the close button 1628 which causes the display of the information for item 1635 to revert to the appearance for that item shown in FIG. 16A. The user may collapse an entire group to hide the entries or search results from that group by selecting the collapse button 1614 shown in FIG. 16A, thereby causing the disappearance of the entries in this group as shown in FIG. 16B. The user may cause these items to reappear by selecting the expand button 1614A as shown in FIG. 16B to thereby revert to the display of the items as shown in FIG. 16A.
The search results user interface shown in FIGS. 16A and 16B presents only a limited number of matches or hits within each category. In the particular example of these figures, only the five top (most relevant or most highly sorted) hits are displayed. This can be seen by noticing the entry at the bottom of each list within a group which specifies how many more hits are within that group; these hits can be examined by selecting this indicator, such as indicator 1612, which causes the display of all of the items in the documents category or kind for the search for “button” which was entered into the text entry region 1603. Further examples of this behavior are described below and are shown in conjunction with FIGS. 18A and 18B. It will be appreciated that window 1601 is a closeable and resizable and moveable window and includes a close button and a resizing control 1625A.
FIGS. 18A and 18B illustrate another window 1801 which is very similar to the window 1601. The window 1801 includes a text entry region 1803, a group by menu selection region 1805, a sort by menu selection region 1807, and a where menu selection region 1809, each of which function in a manner which is similar to the regions 1605, 1607, and 1609 respectively of FIG. 16A. Each item in a list view within the window 1801 includes an information button 1827, allowing a user to obtain additional information beyond that listed for each item shown in the window 1801. The window 1801 further includes headers 1811, 1813, 1815, 1817, 1819, 1821, and 1823 which separate each group of items, grouped by the type or kind of document, and sorted within each group by date, from the other groups. A collapse button 1814 is available for each of the headers. The embodiment shown in FIGS. 18A and 18B shows the ability to switch between several modes of viewing the information. For example, the user may display all of the hits within a particular group by selecting the indicator 1812 shown in FIG. 18A which results in the display of all of the images files within the window 1801 within the region 1818A. The window is scrollable, thereby allowing the user to scroll through all the images. The user can revert back to the listing of only five of the most relevant images by selecting the “show top 5” button 1832 shown in FIG. 18B. Further, the user can select between a list view or an icon view for the images portion shown in FIGS. 18A and 18B. The user may select the list view by selecting the list view button 1830 or may select the icon view by selecting the icon view button 1831. The list view for the images group is shown in FIG. 16A and the icon view for the images group is shown in FIGS. 18A and 18B. It can be seen that within a single, moveable, resizable, closeable search result window, that there are two different views (e.g. a list view and an icon view) which are concurrently shown within the window. For example, the PDF documents under the header 1819 are displayed in a list view while the images under the header 1817 are displayed in an icon view in FIGS. 18A and 18B. It can also be seen from FIGS. 18A and 18B that each image is shown with a preview which may be capable of live resizing as described in a patent application entitled “Live Content Resizing” by inventors Steve Jobs, Steve Lemay, Jessica Kahn, Sarah Wilkin, David Hyatt, Jens Alfke, Wayne Loofbourrow, and Bertrand Serlet, filed on the same date as this application, and being assigned to the assignee of the present inventions described herein, and which is hereby incorporated herein by reference.
FIG. 19A shows another example of a search result window which is similar to the window 1601. The window 1901 shown in FIG. 19A includes a text entry region 1903 and a group by menu selection region 1905 and a sort by menu selection region 1907 and a where menu selection region 1908. Further, the window includes a close button 1925 and a resizing control 1925A. Text has been entered into the text entry region 1903 to produce the search results shown in the window 1901. The search results again are grouped by a category selected by a user which in this case is the people options 1906. This causes the headers 1911, 1913, 1915, and 1917 to show the separation of the groups according to names of people. Within each group, the user has selected to sort by the date of the particular file or document. The user interface shown in FIG. 19A allows a user to specify an individual's name and to group by people to look for communications between two people, for example. FIG. 19B shows another way in which a user can group a text search (“imran”) in a manner which is different from that shown in FIG. 19A. In the case of FIG. 19B, the user has selected a flat list from the group by menu selection region 1905 and has selected “people” from the sort by menu region 1907. The resulting display in window 1901A is without headers and thus it appears as a flat list.
FIG. 19C shows the user interface of another search result window 1930 which includes a text entry region 1903 and the selection regions 1905, 1907, and 1908 along with a scrolling control 1926. The results shown in the window 1930 have been grouped by date and sorted within each group by date. Thus, the headers 1932, 1934, 1936, 1938, and 1940 specify time periods such as when the document was last modified (e.g. last modified today, or yesterday, or last week). Also shown within the search results window 1930 is the information button 1942 which may be selected to reveal further information, such as an icon 1945 and additional information 1946 as shown for one entry under the today group. This additional information may be removed by selecting the contraction button 1944.
FIG. 19D shows a search result window 1950 in which a search for the text string “te” is grouped by date but the search was limited to a “home” folder as specified in the where menu selection region 1908. Time specific headers 1952, 1954, 1956, and 1958 separate items within one group from the other groups as shown in FIG. 19D.
FIG. 19E shows an alternative embodiment of a search result window. In this embodiment, the window 1970 includes elements which are similar to window 1901 such as the selection regions 1905, 1907, and a scrolling control 1926 as well as a close button 1925 and a resizing control 1925 A. The search result window 1970 further includes a “when” menu selection region 1972 which allows the user to specify a search parameter based on time in addition to the text entered into the text entry region 1903. It can be seen from the example shown in FIG. 19E that the user has decided to group the search results by the category and to sort within each group by date. This results in the headers 1973, 1975, 1977, and 1979 as shown in FIG. 19E.
FIG. 20 shows an exemplary method of operating a system wide menu for inputting search queries, such as the system wide menu available by selecting the search menu command 1505 shown in FIG. 15A or 15B, or 15C. In operation 2001, the system displays a system wide menu for inputting search queries. This may be the search menu command 1505. The user, in operation 2003, inputs a search, and as the search query is being inputted, the system begins performing and begins displaying the search results before the user finishes inputting the search query. This gives immediate feedback and input to the user as the user enters this information. The system is, in operation 2005, performing a search through files, meta-data for the files, emails within an email program, address book entries within an address book program, calendar entries within a calendar program, etc. The system then, in operation 2007, displays an abbreviated (e.g. incomplete) list of hits if there are more than a certain number of hits. An example of this abbreviated listing is shown in FIG. 15B. The listing may be sorted by relevance and segregated into groups such as categories or types of documents. Then in operation 2009, the system receives a command from the user to display all the hits and in operation 2011 the system displays the search results window, such as the window 1601 shown in FIG. 16A. This window may have the ability to display two different types of views, such as an icon view and a list view within the same closeable, resizable, and moveable window. It will be appreciated that the searching, which is performed as the user is typing and the displaying of results as the user is typing may include the searching through the meta-data files created from meta-data extracted from files created by many different types of software programs.
FIGS. 21, and 22A, 22B, 22C, and 22D will now be referred to while describing another aspect of the inventions. This aspect relates to a method of selecting a group of files, such as a group of individual data files. In an exemplary method of this aspect, a data processing system receives a selection of a plurality of items, such as data files, folders (e.g. graphical user interface representations of subdirectories), application programs or a combination of one or more of these items. This selection may be performed by one of the many conventional ways to select a plurality of items such as (a) positioning a cursor at each item individually (e.g. through the movement of a mouse) and indicating a selection individually by, for example, pressing and releasing a button, such as a mouse's button; (b) pointing a cursor at a first item in a list and indicating a selection of the first item and pointing the cursor at a last item in a list of items and indicating a selection of all items from the first item to the last item in the list; (c) drawing a selection rectangle by a dragging operation of the cursor, etc. Thus operation 2101 shown in FIG. 21 receives one or more inputs indicating a selection of a plurality of items. The system in operation 2103 receives a command requesting both the creation of a new storage facility (e.g. a folder) and an association of the plurality of items with the new storage facility. While the operation 2103 is shown following operation 2101, in certain embodiments operation 2103 may precede operation 2101. The association of operation 2103 may be a copy or a move operation. For example, the user may select multiple items and then command the system to move those items from their existing locations to a new folder which is created in one operation as a result of the move and create new folder command. In response to the command received in operation 2103, the system creates a new storage facility, such as a new folder, with a predetermined directory path name or a user specified path name and the system further associates the selected plurality of items with the new storage facility. This association may be either a move or a copy operation. A copy operation would typically involve making a copy of each selected item and storing the item with a path name that reflects the storage of the item within the new folder having a predetermined directory path name or a user specified directory path name. A move operation, in which the items are moved into the new folder, may merely change the path names associated with each of the selected items (rather than making a copy of the items) which changed path names will reflect the new file system location (e.g. within the subdirectory of the new folder) of the selected items.
FIGS. 22A -22D show one example of the method of FIG. 21. A desktop 2201 on a display device is shown containing multiple windows and also an icon 2227 on the desktop. A cursor 2211 is also shown on the desktop. The windows 2203, 2205, and 2207 each contain a plurality of items shown as icons. In particular, window 2203 includes a data file represented by icon 2215 in a folder (e.g. a graphical representation of a subdirectory in a file storage system) represented by icon 2217. The window 2205 includes a program icon 2223 and a document icon 2219 and another document icon 2225 and a folder icon 2221. The window 2207 shows a list view of several files including “File B.” The user may then, using the cursor 2211 or using other conventional user interface techniques, select multiple items. This may be done with one input or more inputs which indicate the selection of multiple items. FIG. 22B shows the result of the user having selected icons 2215, 2217, 2223, 2225, 2227, and “File B” in window 2207. It can be seen that the cursor 2211 is positioned adjacent to the icon 2225 at this point in the operation.
Then the user, after having selected a plurality of items, may invoke the command referred to in operation 2103. An example of this is shown in FIG. 22C which represents a portion of the desktop 2101, which portion is designated 2201A as shown in FIG. 22C. The user has caused a pop up menu 2230 to appear, which pop up menu includes three options 2231, 2232, and 2233. Option 2231 would allow a user to move all the selected items into the trash (e.g. delete them) while options 2232 and 2233 relate to the command referred to in operation 2103 of FIG. 21. In particular, option 2232 is a command which is selectable by the user to create a new folder and, in the same operation, move the items which have been selected into the new folder. Option 2233 is a command which allows the user to, in one operation, create a new folder and copy the selected items into the new folder. In the example shown in FIGS. 22A-22D, the user will select option 2232, thereby causing the system to create a new storage facility, such as a new folder with a predetermined directory name (e.g. “new folder”) or alternatively, a user specified path name. This result is shown in FIG. 22D in which the desktop 2201 now includes a new window labeled “new folder” which represents and shows the contents of this new folder, which is also shown as the folder 2253 which is a graphical user interface representation of this new folder.
It will be appreciated that this method may employ various alternatives. For example, a window may appear after the command option 2232 or 2233 has been selected, and this window asks for a name for the new folder. This window may display a default name (e.g. “new folder”) in case the user does not enter a new name. Alternatively, the system may merely give the new folder or new storage facility a default path name. Also, the system may merely create the new folder and move or copy the items into the new folder without showing the new window as shown in FIG. 22D.
Exemplary Processes for Meta-data Enabled Indexing in a Network Environment
FIG. 23 is a block diagram of a network environment 2300 in which a number of client devices (e.g., a master device 2306, at least one slave device(s) 2308, and other device(s) 2310) are communicating with a shared storage device 2302 having a master lock status 2322, and a shared storage volume 2312 having a content structure 2314, a trusted index structure 2316, a master list of changes 2318A, and at least one slave list of changes 2318B-N (e.g., if there is only one slave, then only a slave list 2318B may exist), according to one embodiment.
The shared storage device 2302 may be a standalone storage device, such as a redundant array of independent disks (RAID) device, a network capable hard drive, or other form of storage device (e.g., non-volatile and/or volatile storage device). The shared storage device 2302 may be a file server that has a shared storage volume 2312 that is shared with client devices. The shared storage device 2302 may have no file search/management capability of its own. The master device 2306 and the slave device(s) 2308 may be any form of client device that communicates with the file server. In one embodiment, the shared storage device 2302, the master device 2306, and the slave device(s) 2308 are embodied in a data processing system, which may be a general purpose computer system such as described in FIG. 1. The other device(s) 2310 may be any other device (e.g., a client device, a printer, a server, a security appliance, etc.) that is capable of communicating through the network 2304.
The network 2304 may be any type of local area network (LAN), wide area network (WAN), storage area network (SAN), and/or any other type of system that transmits any combination of voice, video and/or data between users.
The master device 2306 and the slave device(s) 2308 store files (e.g., content data files such as files generated by commercial programs) on the shared storage device 2302. The master device 2306 and the slave device(s) 2308 may have the same physical structure as illustrated in FIG. 23. In the embodiment illustrated in FIG. 23, the master device 2306 includes a search module 2324, an index data structure 2326, a meta-data extractor 2328, a change-list management module 2330, a change-list structure 2336, a notification module 2320A, and a prioritization module 2338. The change-list management module 2330 of the master device 2306 includes a change-list updater 2332 and a change-list generator 2334 in the embodiment illustrated in FIG. 23. Similarly, the slave device(s) 2308 each include a search module 2340, an index data structure 2342, a meta-data extractor module 2344, a change-list management module 2346, a change-list structure 2352, a notification module 2320B, and a prioritization module 2354 in the embodiment of FIG. 23. Also, in the embodiment of FIG. 23, the change-list management module 2346 of the slave device(s) 2308 includes a change-list updater 2348 and a change-list generator 2350.
A change-list generator (e.g., the change-list generator 2350) of the change-list management module (e.g., the change-list management module 2346) of a particular client device (e.g., the slave device 2308) may create a change-list entry (e.g., a change-list entry 2900 indicating an operation 2902, a master or slave 2904, a file name 2906, and optionally other data 2908 as illustrated in FIG. 29) in its change-list structure (e.g., the change-list structure 2352 stored within one of the slave list(s) of changes 2318B-N) based on an operation (e.g., an operation field 2902 such as delete, exchange, update status, hostname, sniff, exclusion change, rename, and/or end of file) to a content file (e.g., a file having data created by a user of an application program) stored in the shared storage device (e.g., within the content structure 2314) by the particular client device (e.g., the slave device 2308). Also, a change-list updater (e.g., the change-list updater 2348 of the slave device(s) 2308) of a change-list management module (e.g., the change-list management module 2346 of the slave device(s) 2308) may update its local index structure (e.g., the index data structure 2342 of the slave device(s) 2308) when a particular client device (e.g., the slave device(s) 2308) receives an updated master list of changes 2318A from another client device (e.g., the master device 2306).
The search module 2324 of the master device 2306 and the search module 2340 of the slave device(s) 2308 may perform the operations described in FIG. 2. In addition, the search module 2324 and the search module 2340 may perform the operation 511 of FIG. 5, and/or any other operation within FIGS. 2-23 related to searching of data. The index data structure 2326 and the index data structure 2342 may be each embodied as the index of files 421 of FIG. 4. In addition, the meta-data extractor module 2328 and the meta-data extractor module 2344 may be the embodied as the meta-data processing software 401 of FIG. 4. It will be understood the search modules, the index data structures, and the meta-data extractor modules of the client devices illustrated in FIG. 23 may be embodied in any of the various examples and user interfaces illustrated in FIGS. 1-22.
The functions of the remaining modules in the master device 2306 (e.g., the change-list management module 2330 and the prioritization module 2338) and the slave device(s) 2308 (e.g., the change-list management module 2346 and the prioritization module 2354) are best understood with reference to FIGS. 24-30.
FIG. 24 is a process flow of a one of the slave device(s) 2308 of FIG. 23 transforming into a master device 2306 through assertion of the master lock status 2322 of FIG. 23, according to one embodiment. In operation 2402, a slave device (e.g., each of the slave device(s) 2308) transmits a signal to the shared storage device 2302 to determine whether the master lock status 2322 is locked (e.g., the master lock status 2322 may determine which client device is in charge of maintaining the master list of changes 2318A). In operation 2404, if the master lock status 2322 is locked (e.g., a master lock in the master lock status 2322 indicates another client device is already the master client device), than one of the slave device(s) 2308 moves on to other operations 2403 (e.g., it should be noted that the slave device may also check whether the master client device is “dead” and/or no longer online, if the master device is dead, the master lock status 2322 may be interpreted by the slave device as unlocked) until it needs to access the shared storage device 2302 again. Each time one of the slave device(s) 2308 communicates with the shared storage device 2302, it may check whether the shared storage device 2302 is locked using operation 2402.
If master lock status 2322 is unlocked, in operation 2406, the slave device transforms (e.g., through a response packet and/or response data) into a new master device (e.g., the master device 2306) and updates the master lock status 2322 to indicate that it is now the new master device (e.g., the master device is a particular one of the client devices that manages the master list of changes 2318A of the shared storage device 2302). In alternate embodiments, the master lock status 2322 determines whether one of the slave device(s) 2308 is the master device based on an algorithm (e.g., a heartbeat messaging algorithm in which a current master device intermittently transmits heartbeat messages to the shared storage device 2302 to indicate that it is operational; a first-in-time assertion in which the first client device to indicate that it is ready and willing to become the master device when the master lock status 2322 is unlocked wins; and a preferred client analysis in which the master lock status 2322 may have certain preferences based on criteria such as speed, performance, bandwidth, etc. of a particular client device before making a determination whether the particular client device can become the master device).
Next, in operation 2408, the new master device collects published change-list entries created by other slave devices (e.g., and stored in the slave list(s) of changes 2318B-N) and updates the master list of changes 2318A. In one embodiment, a prefix (e.g., a period) in front of a file name indicates that a particular file is being updated by a slave device and the removal of the period signals a publication of a file from a slave device to one of the slave list(s) of changes 2318B-N. In this one embodiment, the master device intermittently scans the slave list(s) of changes 2318B-N to see if there are any changes made to files (e.g., periods removed to change list entries), and consolidates all change list entries (e.g., a change list entry 2900 of FIG. 29) changed by the slave devices to the master list of changes 2318A. Furthermore, in this one embodiment, the slave devices intermittently scan the master list of changes 2318A (e.g., through a variety of mechanisms the slave devices may know that the master list of changes 2318A has been updated such as when a period is removed, through a time stamp on the master list of changes 2318A, through a heartbeat packet, or any other form of notification) and update their local copies of the index structure (e.g., so that they can quickly search the index structure and ensure that they have the most current version of the index structure).
In operation 2410, the new master device (e.g., one of the slave device(s) 2308 transformed now the “master device”) intermittently updates the master list of changes 2318A based upon changes made the slave list of changes 2318B-N stored in the shared storage device 2302. In one embodiment, the new master device publishes (e.g., removes a period in front of the file name) its master list of changes 2318A whenever it has updated the master list of changes 2318A with entries of the slave list(s) of changes 2318A-N (e.g., so that slave devices can see that there have been changes to the master list of changes 2318A) so that bandwidth across the network 2304 is not extensively tied up and performance of an operating system remains acceptable to most users.
The new master device may occasionally (e.g., twice a day) replace the trusted index structure 2316 by updating a pre-existing trusted index structure 2316 with the master list of changes 2318A (e.g., the trusted index structure 2316 is provided to new slave devices that associate through network 2304 with the shared storage device 2302). The trusted index structure 2316 may reference both a meta-data library (e.g., the meta-data database 415 of FIG. 5) and a content library (e.g., storing actual content of various content files) stored within the content structure 2314. If the new master device (e.g., one of the slave device(s) 2308 now transformed to the “master device”) becomes disabled (e.g., turns off, freezes, restarts, etc.), the master lock status 2322 may become unlocked again (e.g., a master lock may be released by the master lock status 2322).
It should be noted that the meta-data library (e.g., the meta-data database 415 of FIG. 5) stored within the content structure 2314 of the shared storage device 2302 may include internally maintained meta-data (e.g., number of colors in a particular image, whether a flash camera was used, etc.) and published meta-data (e.g., a file's name, and/or a date of creation, and/or a date of modification, and/or a type of file).
The master list of changes 2318A may include changes made to the various content files (e.g., content files in the shared storage volume 2312) by different slave device(s) 2308. The various content files may be created by different application programs (e.g., a word processing program, an image processing program, etc.) and may include different internally maintained meta-data (e.g., different fields for non-published, internally managed meta-data as described in FIGS. 1-23).
The content structure 2314 may be searched for particular ones of the internally maintained meta-data (e.g., number of colors in a particular image, whether a flash camera was used, etc.), the content (e.g., the actual text of a content file created by the word processing program), the published meta-data (e.g., a file's name, and/or a date of creation, and/or a date of modification, and/or a type of file), and the new meta-data (e.g., inferred meta-data such as new meta-data of “war” whenever a document has the word “Iraq” and was created between the years 2001-2005).
The prioritization module (e.g., the prioritization module 2354 of one of the slave device(s) 2308, and/or the prioritization module 2338 of the master device 2306) may separate, within the change-list structure (e.g., the change-list structure 2352 and/or the change-list structure 2336), change-list entries of at least two sessions (e.g., multiple session may be created when a user of a master device forgets to log of from one computer and logs onto another computer with the same profile, as is common within universities and classrooms) of the master device based on physical station addresses (e.g., a machine authentication code (MAC) address burned into read only memory (ROM) of a hardware device and/or interface) associated with each of the at least two sessions (e.g., two different computers at a university on which a user of the master device profile logged on with).
The meta-data extractor module 2344 of each of the slave device(s) 2308 may update the local index data structure 2342 of each of the slave device(s) 2308 with internally maintained meta-data, content, and published meta-data of a particular content file modified by one of the slave device(s) 2308 and/or other client devices (e.g., when the change-list entries are stored on the shared storage device in one of the slave list(s) of changes 2318B-N).
It will be understood that the process as described in the previous paragraph is to ensure that only one client device is in charge of ensuring that the master list of changes 2318A and the trusted index structure 2316 is up to date (e.g., does not become stale) when multiple change-list entries are created by different ones of the slave device(s) 2308 (e.g., the creation and application of change-list entries are described in FIGS. 25-26).
FIG. 25 is a process flow of a slave device (e.g., one of the slave device(s) 2308 of FIG. 23) generating a change-list entry (e.g., a change-list entry 2900 of FIG. 29) based on an operation to a data of the slave device (e.g., a read/write/modify operation to a content file created/edited/or modified by the slave device and stored within the shared storage device 2302), according to one embodiment. In operation 2502, one of the slave device(s) 2308 (a particular slave device) performs an operation on a content file associated with the particular slave device (e.g., stored on the shared storage device 2302). In operation 2504, the notification module 2320B of the particular slave device receives notification of changes to the content file. In operation 2506, the particular slave device generates a change-list packet (e.g., the change-list packet may have fields within the change-list entry 2900 of FIG. 29, and/or may be the change-list entry 2900) of the received notification. In operation 2508, the particular slave device writes the change list packet to the shared storage device 2302 (e.g., so that the shared storage device 2302 may update the slave list(s) of changes 2318B-N).
The particular slave device as described in FIG. 25 may also transform the particular slave device into a master device when the particular slave device transmits a signal to a master lock status 2322 of the shared storage device 2302 before other client devices (e.g., the slave device(s) 2308) and when the master lock status is unlocked (e.g., as described in FIG. 23). In addition, the particular slave device as described in FIG. 25 may search the shared storage device 2302 for particular ones of the new meta-data, the internally maintained meta-data, and the published meta-data (e.g., associated with a search query generated by a user of the search module 2324 of the particular slave device).
FIG. 26 is a process flow of the master device 2306 of FIG. 23 updating a trusted index structure 2316 intermittently (e.g., twice a day). In operation 2602, the master device 2306 processes at least one change list entry generated by at least one slave device (e.g., after intermittently scanning the slave list of changes 2318B-N to determine whether there has been any periods removed from the file names). In operation 2604, the master device 2306 updates a master list of changes 2318A based upon the at least one change list entry. In operation 2606, the master device 2306 optionally prioritizes entries in the master list of changes based upon an algorithm (e.g., any type of algorithm such as one based on business rules of which data is most important). In operation 2608, the master device 2306 updates a trusted index structure intermittently (e.g., twice a day).
FIG. 27A is a process follow of a slave device (e.g., one of the slave device(s) 2308) publishing a change list (e.g., the change list 2900). In operation 2702, a slave device (e.g., one of the slave device(s) 2308) updates a change list (e.g., a change list 2900 as illustrated in FIG. 29) of the slave device. For example, a slave device may update a change list when a particular content file is created, edited, deleted and/or modified, etc. In operation 2704, the slave device publishes (e.g., by removing a period in front of a file name) the change list (e.g., renamed to a form that the master device 2306 can scan) to at least one of the slave list(s) of changes 2318B-N.
FIG. 27B is a process flow of a master device (e.g., the master device 2306) updating a trusted index structure with the master list of changes (e.g., the master list of changes 2318A). In operation 2706, the master device intermittently scans the at least one slave list(s) of changes 2318A to find publish change lists (e.g., the change list entry 2900 generated and published by at least one of the slave device(s) 2308). In operation 2708, the master device (e.g., the master device 2306) collects each of the at least one change list entry (e.g., the change list entry 2900) generated by at least one slave device (e.g., the slave device(s) 2308) and publishes a master list of changes 2318A. Next, in operation 2710, the master device (e.g., the master device 2306) intermittently updates the trusted index structure (e.g., the trusted index structure 2316) with the master list of changes 2318A (e.g., by incorporating change list entries from the master list of changes into the trusted index structure).
FIG. 27C is a process flow of a slave device updating a local meta-data database and a local index database. In operation 2712, a slave device (e.g., one of the slave device(s) 2308) scans the master list of changes 2318A. If there have been changes to the master list of changes 2318A, then the slave device (e.g., one of the slave device(s) 2308) retrieves the master list of changes 2318A and updates a local meta-data database and a local index database (e.g., the local meta-data database and the local index database may be stored within the slave device, rather than on the shard storage device 2302).
FIG. 28 is a process flow of the shared storage device 2302 managing at least two active sessions of the master device (e.g., the master device 2306) by generating separate change-list entries based on a physical station address (e.g., a MAC address), according to another embodiment. In operation 2802, the shared storage device 2302 determines that there are multiple sessions associated with a profile of a master device (e.g., multiple sessions may be created when a user of the master device forgets to log off a computer and re-logs on to another computer without terminating the session on the first computer). In operation 2804, the shared storage device 2302 segregates each session of the multiple sessions in the master list of changes 2318A by identifying each session based on unique identifiers (e.g., unique identifiers such as the physical station address) associated with each of the multiple sessions.
FIG. 29 is a data structure view of a change-list entry 2900. The change list entry 2900 may be generated by the change list generator 2334 of the master device 2306 and/or the change list generator 2350 of each of the slave device(s) 2308. The change-list entry 2900 includes an operation field 2902, a master or slave field 2904, a file name field 2906, and an other field 2908. In one embodiment, the operation field 2902 may be used for operations such as delete, exchange (e.g., for temporary updates to a content file to prevent accidental deletion), update status, hostname (e.g., transmitting client device), sniff, exclusion change, rename, and/or end of file. The master or slave field 2904 determines whether a particular change list entry 2900 is transmitted by a master device and/or a slave device, according to the one embodiment. The filename field operates to identify which file is being addressed by the change-list entry 2900, according to the one embodiment. The other field 2908 is operation filed 2902 specific in the one embodiment, and may be used for operations such as to identify a new name for a file being renamed, etc.
Various embodiments also relate to an apparatus for performing the operations described herein. The apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored on the computer on a machine-accessible medium. The machine-accessible medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer) including a machine-readable medium. The machine-readable medium includes read only memory (“ROM”); random access memory (“RAM”); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); etc.
This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable medium.
The processes and operations presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct a more specialized apparatus to perform the operations described. The required structure for a variety of these systems will appear from the description above. In addition, various embodiments are not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings as described herein.
It should be noted that the various embodiments having modules, circuits, switches, devices, tables, processors, and electronics described herein may be performed within hardware circuitry (e.g., logic circuitry such as CMOS based circuitry) as well as in software (e.g., through machine-implemented methods and/or through machine-readable mediums). Specifically, it should be noted that an architecture for various modules, generators, and updaters of FIGS. 1-30 can be implemented in some embodiments with software (e.g., programming code generated in machine language, C++, and/or any other type of programming language and accessible through a machine readable medium).
Furthermore, it should be noted that the architecture may be implemented with one or more semiconductor devices including circuitry such as logic circuitry to perform its various functions as described above. In some embodiments, hardware circuitry may provide speed and performance advantages over software implementations of the search modules 2324 and 2340, the prioritization modules 2338 and 2354, the change-list management modules 2330 and 2346, the notification modules 2320A-B, and the master lock status 2322, etc. of FIG. 23. In other embodiments, software implementations may be preferred. In one embodiment, the search modules 2324 and 2340, the prioritization modules 2338 and 2354, the change-list management modules 2330 and 2346, the notification module 2320A-B, the master lock status 2322 may be designed using a search circuits, a prioritization circuits, a change-list management circuits, a notification circuit, a master lock circuit, and/or any combination of these circuits, and may be built with semiconductor circuitry (e.g., logic circuitry such as CMOS based circuitry). A semiconductor chip may implement the functions (e.g., as described in FIGS. 1 thru FIG. 29) described within the various embodiments using logic gates, transistors, and hardware logic circuitry associated with implementing the various embodiments disclosed herein.
In the foregoing specification, the embodiments have been described with reference to specific exemplary embodiments thereof. It will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the embodiments as set forth in the following claims. For example, in some embodiments, the concepts disclosed herein may be applied to other networking standards and protocols consistent with this disclosure which are similar to, but not explicitly confined to various modules, generators, and structures explicitly disclosed herein. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.

## Claims

1. A method, comprising:
updating, by a slave device, a change list;
sending into a network, by the slave device, packetized information pertaining to the updating to a shared storage device for publication to a master device, the packetized information including:
i) information that identifies the slave device as a slave device;
ii) the identity of a file in which a change was made;
iii) the change;
iv) an operation performed on the slave device that imparted the change to the file;

receiving from the network, by the slave device, a published master list of changes provided by the shared storage device, the published master list of changes reflecting changes made by other slave devices updating at the slave device, a local metadata database and a local index database of the slave device;
transforming, by the slave device, into a new master device;
receiving from the network, by the new master device, additional changes made by at least certain ones of the other slave devices and processing the additional changes into a new master list of changes;
updating, by the new master device, the shared storage device with the new master list of changes for publication.

2. The method of claim 1, wherein transforming the slave device into the new master device comprises the slave device transmitting a signal to a master lock status of the shared storage device before other slave devices and when the master device is disabled.

3. The method of claim 2, wherein the master lock status uses an algorithm chosen from a group comprising at least one of a heartbeat messaging, a first-in-time assertion, and a preferred client analysis to determine whether the slave device becomes the new master device.

4. The method of claim 1 further comprising said new master device constructing a trusted index structure.

5. The method of claim 4, wherein the trusted index structure is provided to new slave devices by the new master device.

6. The method of claim 4, further comprising searching, by the slave device, the shared storage device for new meta-data.

7. The method of claim 4, wherein the shared storage device has no search management capability within its operating system and is merely a network storage device.

8. The method of claim 1, further comprising receiving, by the slave device, notifications from the master device when the master list of changes is published.

9. The method of claim 1, wherein the publication of the information pertaining to the updating is performed by removing a prefix in front of a file name.

10. The method of claim 1, further comprising optionally prioritizing, by the new master device, entries in the new master list of changes based upon an algorithm.

11. The method of claim 10, wherein the algorithm is based on at least one of a time stamp, a session identifier, and a status of each of the published change lists.

12. A machine readable storage medium containing program code that when executed by a computing system causes a method to be performed, the method comprising:
updating, by a slave device, a change list;
sending into a network, by the slave device, packetized information pertaining to the updating to a shared storage device for publication to a master device, the packetized information including:
i) information that identifies the slave device as a slave device;
ii) the identity of a file in which a change was made;
iii) the change;
iv) an operation performed on the slave device that imparted the change to the file;

receiving from the network, by the slave device, a published master list of changes provided by the shared storage device, the published master list of changes reflecting changes made by other slave devices;
updating at the slave device, a local metadata database and a local index database of the slave device;
transforming, by the slave device, into a new master device;
receiving from the network, by the new master device, additional changes made by at least certain ones of the other slave devices and processing the additional changes into a new master list of changes;
updating, by the new master device, the shared storage device with the new master list of changes for publication.

13. The machine readable storage medium of claim 12, wherein transforming the slave device into the new master device comprises the slave device transmitting a signal to a master lock status of the shared storage device before other slave devices and when the master device is disabled.

14. The machine readable storage medium of claim 13, wherein the master lock status uses an algorithm chosen from a group comprising at least one of a heartbeat messaging, a first-in-time assertion, and a preferred client analysis to determine whether the slave device becomes the new master device.

15. The machine readable storage medium of claim 12 wherein said method further comprises said new master device constructing a trusted index structure.

16. The machine readable storage medium of claim 15, wherein the trusted index structure is provided to new slave devices by the new master device.

17. The machine readable storage medium of claim 15, wherein said method further comprises searching, by the slave device, a shared storage device for new meta-data.

18. The machine readable storage medium of claim 15, wherein the shared storage device has no search management capability within its operating system and is merely a network storage device.

19. The machine readable storage medium of claim 12, wherein said method further comprises receiving, by the slave device, notifications from the master device when the master list of changes is published.

20. The machine readable storage medium of claim 12, wherein the publication of the information pertaining to the updating is performed by removing a prefix in front of a file name.

21. The machine readable storage medium of claim 12 wherein the method further comprises optionally prioritizing, by the new master device, entries in the new master list of changes based upon an algorithm.

22. The machine readable storage medium of claim 21, wherein the algorithm is based on at least one of a time stamp, a session identifier, and a status of each of the published change lists.

23. A computing system comprising a memory coupled to a processing unit, said memory to store program code, said program code to implement a method when read from said memory and processed by said processing unit, said method comprising:
updating, by a slave device, a change list;
publishing, by the slave device, the change list into at least one slave list of changes, the publishing including sending from the slave device to a master device a change of the at least one slave list of changes, the change sent in a packet having the following additional information:
i) information that identifies the slave device as a slave device;
ii) the identity of a file in which the change was made;
iii) an operation performed on the slave device that imparted the change to the file;

receiving from the master device a published master list of changes, the published master list of changes generated from published change lists of the slave device and other slave devices;
receiving, at the slave device, changes made to the master list of changes and updating a local metadata database and a local index database of the slave device;
transforming, by the slave device, into a new master device;
updating, by the new master device, a new trusted index structure with a new master list of changes.

24. The computing system of claim 23, wherein transforming the slave device into the new master device comprises the slave device transmitting a signal to a master lock status of the shared storage device before other slave devices and when the master device is disabled.

25. The computing system of claim 24, wherein the master lock status uses an algorithm chosen from a group comprising at least one of a heartbeat messaging, a first-in-time assertion, and a preferred client analysis to determine whether the slave device becomes the new master device.

26. The computing system of claim 23 further comprising said new master device constructing a trusted index structure.

27. The computing system of claim 26, wherein the trusted index structure is provided to new slave devices by the new master device.

28. The computing system of claim 26, wherein said method further comprises searching, by the slave device, the shared storage device for new meta-data.

29. The computing system of claim 26, wherein the shared storage device has no search management capability within its operating system and is merely a network storage device.

30. The computing system of claim 23, wherein said method further comprises receiving, by the slave device, notifications from the master device when the master list of changes is published.

31. The computing system of claim 23, wherein the publication of the information pertaining to the updating is performed by removing a prefix in front of a file name.

32. The computing system of claim 23 wherein said method further comprising optionally prioritizing, by the new master device, entries in the new master list of changes based upon an algorithm.

33. The computing system of claim 32, wherein the algorithm is based on at least one of a time stamp, a session identifier, and a status of each of the published change lists.