Patent Grant
10181116
The present disclosure relates generally to data correlation. In particular, the present application provides apparatuses, systems, and methods suited to job application tracking and identifying jobs matching the interests and abilities of an applicant.
Complex processes involving numerous steps, voluminous information and multiple parties are often difficult for users to visualize, monitor, correlate, initiate and manage. Individuals are often forced to develop ad hoc systems to manage processes, with varying degrees of success. This problem is particularly acute in situations where the processes are highly information-intensive and involve multiple data sources. As such, it is often a challenging proposition for an individual to simply manage their own data, let alone derive meaningful search criteria from the data or correlate additional data entries based on their data.
One situation where users are faced with the problem of managing information intensive processes is searching for a new job. Job search is a particularly difficult process for individuals to manage because it is not done very often, it requires interaction with various different systems, and in order to be successful there is little tolerance for error.
Job applicants typically search numerous job listings from any number of job search web sites, classified ads, and employer web sites. The jobs listings discovered in these searches would most likely each have their own application procedures and feedback processes. The searches will also often result in the applicant encountering many jobs not suited to the applicant as well as the same job listing in multiple locations. To effectively and efficiently conduct their job search, applicants must recognize duplicate job listings, manage the various application processes, and receive and respond to application feedback.
In addition to identifying multiple listings to avoid duplicative submissions, it is also advantageous to know about duplicate listings of a single job because the information provided by the various listing sites might differ. For example, one site listing the job might provide information indicating that the position has been filled before the other sites.
After the applicant has collected different relevant job listings, the applicant must evaluate the different jobs to determine which best fit the applicant's interests and abilities as well as identify which are the most desirable. As the number of job listings increases managing this evaluation becomes more and more difficult.
Beyond merely identifying relevant job listings, job applicants usually decide to apply to one or many of the jobs discovered in their search. The job applicant must then fill out applications and/or provide resumes for the chosen jobs and coordinate the filing of those applications with the prospective employers. Once filed, the job applicant must monitor the status of the various applications. This monitoring may include scheduling interviews, responding to requests for additional information, checking the status of the employer's review of the application, and/or managing outstanding job offers. The provided status information may assist the job applicant in making important decisions. For example, knowing the progress of outstanding applications through the employers' review and selection may help the applicant decide whether to accept a pending offer or wait for a pending decision from another employer.
In some embodiments of the present invention, a system and method are provided for process tracking and management. In one embodiment, a job application tracking and management system comprises an application tracking and management core and an application tracking and management extension that interfaces with a host application and is in communication with the application tracking and management core. The application tracking and management extension provides a user interface that enables the user of the host application to select listings to be saved, apply to a desired listing and find listings matching a set of criteria pertaining to the applicant. The application tracking and management core provides a user interface to review saved and applied for listings, check the status of applied for listings, identify other instances of the listing and find jobs matching the interests and abilities of the applicant.
In another embodiment of the invention, a browser plug-in is provided to enable job hunters to easily search, save, evaluate, and apply to job listings. In one implementation, the plug-in interacts with a host application providing access to a plurality of job listings. For a current job listing displayed on the host application, one embodiment of the plug-in may provide a save control that stores information relating to the current job listing and, in a further embodiment, an apply control that initiates a job application process for the current job listing.
In another embodiment, the plug-in may facilitate matching jobs control that initiates a search for jobs matching or similar to the current job listing. In a further embodiment, the show matching jobs control initiates a search for jobs according to an analysis of the plurality of jobs saved and/or applied to by the applicant. In another embodiment, the browser plug-in also allows the applicant's browsing history to be incorporated into the process of identifying appropriate job listings for the applicant.
In another embodiment, feedback is provided for a pending job application comprising receiving an application along with a feedback generating object; accessing the application; automatically activating the feedback generating object in response to the accessing of the application; generating a feedback message via the feedback object; and transmitting the feedback message.
In another embodiment, jobs relevant to an applicant are identified by retrieving information pertaining to the applicant, including but not limited to the applicant's desired location, income expectations, experience level, educational background, and other attributes and preferences of the applicant. One or more job listing services are searched based on the retrieved information. A plurality of job listings are received from the search and the received job listings are scored based on the retrieved information. Based on their respective scores, one or more job listings are identified for an applicant. In one embodiment, job listings that score over a certain threshold (e.g., 90 out of 100) are identified as being appropriate for an applicant. In some embodiments, information pertaining to the applicant may come from the applicant's resume. In one embodiment, jobs relevant to an applicant are identified by an analysis of the jobs saved and/or applied to by the applicant. In some embodiments, jobs relevant to an applicant are identified by analysis of the applicant's profile, which in one embodiment may include an applicants browsing history.
In another embodiment, a method for obtaining job listing information is provided, comprising obtaining information relating to a job listing in a host application; activating a control to save the contents of the job listing; analyzing the job listing and extracting relevant job information including an employer name, a job location, a job title, an experience requirement, and a job description.
The Process Tracking And Management Viewer allows the applicant to access the functions of the Process Tracking And Management Environment, such as integrating input data 20 or conducting process tracking. The Process Tracking And Management Viewer may connect to a network 40 to receive information concerning the processes being tracked, such as a status update for a particular process.
The Process Tracking And Management Viewer also interacts with the Process Tracking And Management Plug-In 50. The Process Tracking And Management Plug-In provides a mechanism for information to be transferred to and from the Process Tracking And Management Viewer. For example, a monitored process might be generated through the use of another application (i.e., a host application) with which the Process Tracking And Management Plug-In is integrated in order to provide added functionality. In this way, when a new process is started in the host application the Process Tracking And Management Plug-In provides a user interface and communications infrastructure to communicate the relevant information about the new process to the Process Tracking And Management Plug-In. The Process Tracking And Management Plug-In can similarly make relevant information from the Process Tracking And Management Viewer, such as the input data, accessible to the host program.
An applicant would typically have a unique instance of the Job Application Tracking And Management Environment for his or her use. Typically this might be accomplished by having one local version of the Job Application Tracking And Management Environment on the applicant's personal computer. Applicants might alternately be provided a unique instance of the Job Application Tracking And Management Environment through the use of user accounts with usernames and passwords. The applicant's unique instance of the Job Application Tracking And Management Environment stores relevant personal information about the applicant and his or her job search. In particular, the Job Tracking And Management Core 110, for example, might take as input the applicant's resume and/or cover letter 120. The resume and cover letter can then be made available to aid in filing job applications for the applicant and/or in finding job listings suitable to the interests and abilities of the applicant. The Job Tracking And Management Core would most likely keep a copy of the applicant's resume and cover letter or a symbolic link to its location. In a web application embodiment the resume and cover letter could be up-loaded to the web application's host server.
Once accessed by the Job Tracking And Management Core, the resume and cover letter information can be parsed by the Job Tracking And Management Core to extract relevant information about the applicant, such as, the applicant's name, address, phone number, email address, educational background, title, work history, etc. This parsed information might be presented to the applicant for confirmation and then used by the Job Tracking And Management Core to create a profile associated with the applicant. In a further embodiment, the applicant could be prompted to provide additional information to expand the profile created by the Job Tracking And Management Core. Alternately, elements of the applicant's profile could be entered by hand or imported from some other source. In some embodiments, key terms associated with the applicant may be extracted from a resume during the creation/upload process. The key terms may be used for as search terms in a job matching application that will be described in greater detail below.
In the job application process, information about job listings is likely to be derived from multiple sources, e.g., various job listing services and various employer listings. Typically, these job listings will come to the attention of the applicant through searches on the World Wide Web, or a similar information-gathering environment. The Job Listing Tracking Extension can be embodied by a web browser plug-in, for example, with the web browser acting as the host application for the Job Listing Tracking Extension. Alternately, it could be a separate utility, a network, e.g. web, interface, or an integrated function of the host application.
In the embodiment of
Relevant data is extracted 215 from the received input, for example, if the input were a resume, the extraction could include parsing and analyzing the resume to distill the key data relevant to the job listing search. The relevant data is used to build a search profile 225 that may then be utilized, either in whole or in part, in generating and conducting a job listing search or searches 235. The results of the search or searches are processed 245, which in some embodiments may include a further analysis and/or refinement of the search results, and from the processing, relevant results (i.e., a plurality of job listings corresponding to the input 205) are identified 255.
In a further embodiment, shown in
In some embodiments, the base data entry and/or user correlation parameters may be direct input, such as an applicant's response(s) to one or more brief and/or in-depth surveys as discussed in
In one embodiment, the relevant user correlation parameters may include an applicant's historical information. In some embodiments, the historical information may include an applicant's search for job listings, viewing of job listings, responses to job listings, aspects of the applicant's profile, application submission to job listings, and/or saved job listings. In another embodiment, the historical information includes the applicant's web site viewing and/or web search history.
In one implementation, shown in
For example, in one embodiment, the analysis of a particular applicant's base data entry (in this case the applicant's resume) may yield base data entry correlation metrics that correspond to skills, education, work history and other details relevant to software engineering. User correlation metrics corresponding to the applicant (in this case the job search terms used by the applicant on a job listing site, such as job locations searched) are retrieved and correlated to the base data entry metrics and a data entry correlation report is generated. In this case, the metrics may indicate that the applicant has a certain level of experience in software engineering and has previously worked in the southwest (from analysis of the base data entry), but has been searching for jobs in the northwest (from the user correlation parameters). This data entry correlation report may then be utilized to better target and serve the applicant's interest by, for example, providing matching software engineering jobs in the northwest.
In another embodiment, the base data entry may be selected by the applicant, but is not necessarily applicant specific, including but not limited to a job listing. For example, if a job listing is the base data entry, the job listing would be processed to extract the relevant base data entry metrics. In some embodiments, the correlation metrics may include the metrics mentioned above, and may be extracted from the base data entries previously listed (e.g., resumes, cover letters, survey responses, profiles). In one embodiment, the data entry correlation report may be useful in finding job listings similar to the job listing used as the base data entry that are especially well suited to an applicant.
For example, for the case where a job listing is the base data entry, the correlation metrics may be based on the applicant's web or internet browsing history. If the job listing selected is for a general software engineer with C/C++ programming experience, and the applicant's browsing history shows indicates an interest in video game development as well as a particular geographic region, the data entry correlation report would reflect the potential correlation. The data entry correlation metrics could then be used in finding and/or evaluating job listings for the applicant, i.e., a job listing for a video game programmer requiring C++ programming abilities in applicant's geographic region of interest would be identified as being a good match for the applicant.
One implementation of the Job Listing Tracking Extension 150 may be a web browser toolbar. An implementation of a Job Listing Tracking Extension toolbar 400 is shown in
The Job Listing Tracking Extension can also retrieve information from the Job Tracking And Management Core for use in its host program (e.g., a web browser). For example, if the applicant discovers a listing for a job of interest while browsing, he or she can use the Apply To Job control 425, to initiate the application process. The Apply To Job control can display a menu with a number of different options for application purposes. For example, if the on-line job application has an on-line web form, selecting the Apply To Job option can use information from the Job Tracking And Management Core to auto-populate the web form. If the job listing provides an email address for application submissions, the Choose Resume And Apply option can open the applicant's email client and format an email with the applicant is cover letter content in the body of the email and the applicant's resume attached to the email. In the alternative, the Apply To Job control might generate a cover letter document for transmission to the prospective employer. The Apply To Job control can also be configured to provide a one-click apply feature. For example, if the applicant has provided sufficient information to the system and the currently viewed job listing is in a known format. The process could by configured to effectuate application with only one user action, such as clicking on an automatic apply button.
In some embodiments of the disclosed invention, the Job Listing Tracking Extension may also submit information to the Job Tracking And Management Core from its host program. For example, if the applicant is browsing a web site, particularly a web site listing jobs, the Job Listing Tracking Extension can communicate this information to the Job Tracking And Management Core, which may store the information and in a further embodiment, use it to modify the applicant's profile. For example, if an applicant frequently goes to a particular company's job site, that information could be sent from the Job Listing Tracking Extension to the Job Tracking And Management Core, which could indicate the applicant's interest in employment at the particular company.
The
Another option provided by the Match control 435 in some embodiments of the disclosed invention is Show Jobs Matching Saved 437 option, which allows the applicant to find jobs similar to jobs previously saved using the Save Job control 415. The Job Listing Tracking Extension will then activate processes to analyze the plurality of saved jobs and extract the common and relevant job description terms. The Job Listing Tracking Extension uses the extracted terms to initiate a search for similar jobs, the results of which are provided to the applicant, by way of non-limiting example, jobs from the same area, jobs with the same skills and/or educational requirements, same job description, or a combination of these.
In another embodiment the Match control 435 provides an option to Score This Job 438, which in some embodiments may be provided as a one-click function. In one embodiment, shown in
In one embodiment, the results of selecting Score This Job 438 option can be provided to the applicant via the Job Listing Tracking Extension toolbar 400, as a number or some other relative indicia of the job's suitability for the applicant (e.g., the job listing is an 86% match for the applicant). The applicant can score other job listings and use the resulting indicia to compare different jobs and/or further refine the applicant's profile. In some embodiments, the Job Tracking And Management Core may further enhance the process of creating the score by receiving, storing and analyzing the applicant's goals, criteria, and preferences. Some embodiments of the invention enhance the scoring process by analyzing aspects of an applicants browsing or surfing history, such as job listings viewed as well as companies sites, news sites and retailer sites visited. In one embodiment, a data entry correlation report related to an applicant may be utilized in the scoring process.
This information could then be provided to the Job Listing Tracking Extension and taken into account when performing the job scoring routine. In one embodiment, the scoring process is iterative and may be refined by receiving additional information and/or feedback from the applicant. For example, based on the applicant's interests, the applicant may raise or lower the provided score of a particular job, and this adjustment may then be incorporated when performing the job scoring routine. In terms of implementation, the actual job scoring processes could reside in the Job Tracking And Management Core with the Job Listing Tracking Extension passing the Job Tracking And Management Core the relevant data and the Job Tracking And Management Core providing the score back to the Job Listing Tracking Extension and/or storing for later reference by the applicant. The function could also be implemented on a remote server that processes the job scoring request.
Another option provided by the Match control 435 is Show Jobs Matching Me 439, shown in
The
In another embodiment of the disclosed invention, the Job Listing Tracking Extension and/or the Job Tracking And Management Core may continue to search for matching job listings and notify an applicant if a job listing is found that is especially well matched to the applicant (e.g., the job listing represents the applicant's ideal job). Similarly, an applicant may be notified if a particular listing has an especially high score according to the applicant's profile. In some embodiments the system keeps searching for matching job listings for the applicant even if the applicant has stopped actively looking for a job. In one embodiment, the notification may be provided to an applicant regardless of whether or not the applicant is currently searching for a job. For example, take an applicant who had previously searched for jobs but was unable to find a job listing that was a perfect match. The system could continue searching for matching listings, and if at some future time the system found a job listing that was especially well-suited to the applicant and/or the applicant's profile, the system would notify the applicant that a good match had been found.
Each user initiated action yields a respective action group of listings from which relevant data may be extracted 510. The extracted data from individual listings may be compared with extracted data from other listings in each group and/or, across groups, to identify key common/distinguishing job listing characteristics 520. In a further embodiment, comparisons within and across sub-groupings, such as rated job listings sub-grouped according to ratings or viewed job listings sub-grouped according to view times, may be utilized in identifying key characteristics. The key characteristics identified may then be used to build a search profile 530 from which job listings searches are conducted 540. The job listings resulting from the searches 550 may then be presented to the applicant for browsing 500, and in a further embodiment, the process repeated to provide the applicant with progressively more relevant job listings. In a further embodiment, the method disclosed is used to dynamically update the job listings browsed by an applicant.
Next an iterative match screening of job listings is performed. The queries discussed can be performed through a variety of methods. In some embodiments, the iterative match screening begins with a primary criteria matching 662 of the job listings to obtain a first pool of potential matches for the applicant. The primary criteria match screening 662 uses match criteria that are essential to finding an appropriate match for the applicant, such as skills and/or qualifications required. In some embodiments, required skills and qualifications are fundamental criteria and provide a solution for narrowing down the list of jobs (i.e., the job at least requires skills and qualifications similar to the applicant's skills and qualifications).
In one embodiment, aspects of a data entry correlation report related to an applicant may be included in the primary criteria and/or used in selecting primary criteria. In one embodiment, the applicant may also be allowed to indicate required criteria. For example, if an applicant is interested in finding a job with a particular schedule, salary and/or location, the applicant might designate one of these parameters as required criteria. Any such identified required criteria would be added to the primary criteria matching 662.
The results of the primary criteria matching 662 are passed to a decision block 663 where a check is made to determine if any matching job listings were identified. If no job listings meeting the primary criteria were found, a “no matches found” error 664 is generated and communicated. The criteria may then be adjusted 671 to update the primary match criteria 661 for the screen or start a new Match request 660, and in a further embodiment, update the search criteria. In a further embodiment, the match screen and/or search criteria may be saved and the search be re-run at a later date when the job listings information may have been supplemented or modified. If the matching job listings are only a small number of entries (i.e., the number of entries is <k, where k may be set by the applicant, the system, etc.), the information for those job listings is output 665 to the applicant. If the matching job listings has many entries (number of entries >k), the process continues on to the secondary criteria match screening.
A screen of the remaining job listings is performed to determine which job listings meet one or more of the secondary criteria 666. The results of this match screen are passed to a decision block 667. If none of the jobs meet any of the secondary criteria, the job listings meeting the primary criteria may be reported to the applicant 668. If only a small number of job listings meet any of the secondary criteria, the information for those job listings is output 669 to the applicant. If many job listings meet one or more of the secondary criteria further refinement of the screen can be performed as follows.
In one embodiment, all job listings meeting at least a specified number of secondary criteria can then be presented to the applicant for review 670. This approach works particularly well when the secondary criteria are not ordered in terms of importance. In other words, if there are a number of secondary criteria without an indication that some of those criteria are more preferred than others, it might be best to give the applicant the information for all the job listings that meet their primary criteria plus the specified number of their secondary criteria.
The applicant can then review the job listings to see how each meet their secondary criteria and choose whichever they feel is the best match. In one embodiment, the applicant may rate some or all of the provided job listings and/or select job listings that the applicant feels are a good match and in a further embodiment, the rated and/or selected job listings may be used to refine or adjust criteria 671 and update the match criteria 661 used to select job listings for the applicant. For example, if the applicant gives a low rating for a particular employer or type of job, the criteria would be modified to screen against the particular employer or job type. In one embodiment, an applicant's screen criteria and/or modified screen criteria may be reflected in subsequent data entry correlation reports for an applicant.
The approach described above could be refined, as shown in
The process as described above will result in job listings that meet the highest number of the applicant's criteria. In other words, if twenty jobs meet any five of the applicant's criteria, but none of the jobs meet six of the criteria, this match process will identify those twenty job listings. This procedure, however, does not value any of the secondary criteria more than the rest. Accordingly, if some of the applicant's secondary criteria are more important than others a different process might be advisable.
The process begins with job listings meeting one or more of the secondary criteria 690. These are screened for job listings matching the (n)th most important secondary criteria 691, i.e., the first most important criteria in the first iteration of the process, etc. The results derived from the match screen are checked to determine the number of matching job listings 692. If only a small number of job listings remain after the matching, those job listings are output 693. If no job listings remain after the matching, a determination is made to discover whether there are other criteria to check 694. If not, the job listings found after the screen for matches for the (n−1)th criteria are output 695. If other criteria remain to be screened, the value of n is incremented 696. The job listings remaining after the previous matching are now screened again at 691 to determine if any of those job listings match the new (n)th criteria and the iterative process continues. If multiple job listings are found to meet the (n)th criteria at decision 692, a determination 697 is made to find whether there are any criteria remaining to be screened. If no criteria remain, the job listings meeting the (n)th criteria are output 698. If other criteria remain to be screened, the value of n is incremented 699. The job listings remaining after the previous matching are now screened again at 691 to determine if any of those job listings match the new (n)th criteria and the iterative process continues.
Alternatively, the matching systems disclosed in
In addition to screening for matching job listings, in some embodiments of the disclosed invention the above methods may be similarly utilized in scoring job listings for an applicant. For example, the more criteria a job listing met, the higher the relative score of the job listing would be. As discussed above, the scoring could similarly incorporate different priority levels and/or weights for different criteria in calculating a job listing's score. Also, some level of iterative screening may be implemented as part of the search process.
Job listings saved and/or applied for by the applicant using the Job Listing Tracking Extension are recorded by the Job Tracking And Management Core. The Job Tracking And Management Core allows the applicant to access this information. For example, the Job Tracking And Management Core can provide a history screen listing the applicant's saved and applied for jobs, along with relevant information about each saved job. For example, the embodiment of
In one embodiment, the applicant may rate the stored jobs according to their preferences, as shown in
The Job Tracking And Management Core can also provide a Job View screen that provides detailed information about the applicant's saved jobs. This screen could, for example, be accessed by selecting a job from the history screen. One embodiment of a Job View screen is shown in
As it is advantageous for the applicant to know whether the same job is listed elsewhere, the Job View screen can also include controls identifying other web sites containing the same job listing 811, which also allow the applicant to view the job listing as it appears on that site. This could be accomplished by integrating a browser window showing the job listing as it appears on the various listing sites or by retrieving and reformatting the information from the various listing sites. The Job Tracking And Management Core can independently search out these duplicate listings or they can be identified through the applicant's search process, such the Job Tracking And Management Core recognizes when to retrieved jobs are in fact identical.
Additionally, as with the job history screen, in some embodiments the Job View Screen may also allow the applicant to rate aspects of the job displayed on the Job View Screen, as shown in
The Job Tracking And Management Core 110 can also provide a Company Metrics screen such as is shown in
The entirety of this disclosure (including the Cover Page, Title, Headings, Field, Background, Summary, Brief Description of the Drawings, Detailed Description, Claims, Abstract, Figures, and otherwise) shows by way of illustration various embodiments in which the claimed inventions may be practiced. The advantages and features of the disclosure are of a representative sample of embodiments only, and are not exhaustive and/or exclusive. They are presented only to assist in understanding and teach the claimed principles. It should be understood that they are not representative of all claimed inventions. As such, certain aspects of the disclosure have not been discussed herein. That alternate embodiments may not have been presented for a specific portion of the invention or that further undescribed alternate embodiments may be available for a portion is not to be considered a disclaimer of those alternate embodiments. It will be appreciated that many of those undescribed embodiments incorporate the same principles of the invention and others are equivalent. Thus, it is to be understood that other embodiments may be utilized and functional, logical, organizational, structural and/or topological modifications may be made without departing from the scope and/or spirit of the disclosure. As such, all examples and/or embodiments are deemed to be non-limiting throughout this disclosure. Also, no inference should be drawn regarding those embodiments discussed herein relative to those not discussed herein other than it is as such for purposes of reducing space and repetition. For instance, it is to be understood that the logical and/or topological structure of any combination of any program modules (a module collection), other components and/or any present feature sets as described in the figures and/or throughout are not limited to a fixed operating order and/or arrangement, but rather, any disclosed order is exemplary and all equivalents, regardless of order, are contemplated by the disclosure. Furthermore, it is to be understood that such features are not limited to serial execution, but rather, any number of threads, processes, services, servers, and/or the like that may execute asynchronously, concurrently, in parallel, simultaneously, synchronously, and/or the like are contemplated by the disclosure. As such, some of these features may be mutually contradictory, in that they cannot be simultaneously present in a single embodiment. Similarly, some features are applicable to one aspect of the invention, and inapplicable to others. In addition, the disclosure includes other inventions not presently claimed. Applicant reserves all rights in those presently unclaimed inventions including the right to claim such inventions, file additional applications, continuations, continuations in part, divisions, and/or the like thereof. As such, it should be understood that advantages, embodiments, examples, functional, features, logical, organizational, structural, topological, and/or other aspects of the disclosure are not to be considered limitations on the disclosure as defined by the claims or limitations on equivalents to the claims.
This application is a Continuation-in-part of non-provisional patent application “Job Application Tracking System,” Ser. No. 11/383,412, filed May 15, 2006 and priority is claimed to the application under 35 U.S.C. § 120. This application also claims all rights of priority under 35 USC § 119 to provisional patent application “Job Application Tracking System”, Ser. No. 60/757,781, filed Jan. 9, 2006. Application titled, “Apparatuses, Systems and Methods for Application Submission Tracking and Management,” Ser. No. 11/614,929, filed Dec. 21, 2006 is a co-pending related application. Each of these applications are hereby incorporated by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4831403 | Ishida et al. | May 1989 | A |
| 4882601 | Taniguchi et al. | Nov 1989 | A |
| 4910548 | Taniguchi et al. | Mar 1990 | A |
| 4912648 | Tyler | Mar 1990 | A |
| 5023646 | Ishida et al. | Jun 1991 | A |
| 5062074 | Kleinberger et al. | Oct 1991 | A |
| 5164897 | Clark et al. | Nov 1992 | A |
| 5168299 | Taniguchi et al. | Dec 1992 | A |
| 5197004 | Sobotka et al. | Mar 1993 | A |
| 5218395 | Taniguchi et al. | Jun 1993 | A |
| 5416694 | Parrish et al. | May 1995 | A |
| 5539493 | Kusaka | Jul 1996 | A |
| 5663910 | Ko et al. | Sep 1997 | A |
| 5671409 | Fatseas et al. | Sep 1997 | A |
| 5740477 | Kosako et al. | Apr 1998 | A |
| 5805747 | Bradford | Sep 1998 | A |
| 5832497 | Taylor | Nov 1998 | A |
| 5884270 | Walker et al. | Mar 1999 | A |
| 5931907 | Davies et al. | Aug 1999 | A |
| 5950022 | Hagiwara | Sep 1999 | A |
| 5978767 | Chriest et al. | Nov 1999 | A |
| 5978768 | McGovern et al. | Nov 1999 | A |
| 6006225 | Bowman et al. | Dec 1999 | A |
| 6026388 | Liddy et al. | Feb 2000 | A |
| 6052122 | Sutcliffe et al. | Apr 2000 | A |
| 6144944 | Kurtzman, II et al. | Nov 2000 | A |
| 6144958 | Ortega | Nov 2000 | A |
| 6169986 | Bowman et al. | Jan 2001 | B1 |
| 6185558 | Bowman et al. | Feb 2001 | B1 |
| 6226630 | Billmers | May 2001 | B1 |
| 6247043 | Bates et al. | Jun 2001 | B1 |
| 6249784 | Macke et al. | Jun 2001 | B1 |
| 6263355 | Harrell et al. | Jul 2001 | B1 |
| 6272467 | Durand et al. | Aug 2001 | B1 |
| 6275812 | Haq et al. | Aug 2001 | B1 |
| 6289340 | Puram et al. | Sep 2001 | B1 |
| 6304864 | Liddy et al. | Oct 2001 | B1 |
| 6363376 | Wiens et al. | Mar 2002 | B1 |
| 6370510 | McGovern | Apr 2002 | B1 |
| 6385620 | Kurzius | May 2002 | B1 |
| 6401084 | Ortega et al. | Jun 2002 | B1 |
| 6434551 | Takahashi et al. | Aug 2002 | B1 |
| 6453312 | Goiffon et al. | Sep 2002 | B1 |
| 6460025 | Fohn et al. | Oct 2002 | B1 |
| 6463430 | Brady et al. | Oct 2002 | B1 |
| 6492944 | Stilp | Dec 2002 | B1 |
| 6502065 | Imanaka et al. | Dec 2002 | B2 |
| 6516312 | Kraft et al. | Feb 2003 | B1 |
| 6523037 | Monahan et al. | Feb 2003 | B1 |
| 6546005 | Berkley et al. | Apr 2003 | B1 |
| 6563460 | Stilp | May 2003 | B2 |
| 6564213 | Ortega et al. | May 2003 | B1 |
| 6567784 | Bukow | May 2003 | B2 |
| 6571243 | Gupta et al. | May 2003 | B2 |
| 6578022 | Foulger | Jun 2003 | B1 |
| 6603428 | Stilp | Aug 2003 | B2 |
| 6615209 | Gomes et al. | Sep 2003 | B1 |
| 6636886 | Katiyar et al. | Oct 2003 | B1 |
| 6646604 | Anderson | Nov 2003 | B2 |
| 6658423 | Pugh et al. | Dec 2003 | B1 |
| 6661884 | Shaffer | Dec 2003 | B2 |
| 6662194 | Joao | Dec 2003 | B1 |
| 6678690 | Kobayashi et al. | Jan 2004 | B2 |
| 6681223 | Sundaresan | Jan 2004 | B1 |
| 6681247 | Payton | Jan 2004 | B1 |
| 6697800 | Jannink et al. | Feb 2004 | B1 |
| 6701313 | Smith | Mar 2004 | B1 |
| 6704051 | Takahashi | Mar 2004 | B1 |
| 6714944 | Shapiro et al. | Mar 2004 | B1 |
| 6718340 | Hartman et al. | Apr 2004 | B1 |
| 6757691 | Welsh et al. | Jun 2004 | B1 |
| 6781624 | Takahashi | Aug 2004 | B1 |
| 6782370 | Stack | Aug 2004 | B1 |
| 6803614 | Takahashi | Oct 2004 | B2 |
| 6853982 | Smith et al. | Feb 2005 | B2 |
| 6853993 | Ortega | Feb 2005 | B2 |
| 6867981 | Murohara | Mar 2005 | B2 |
| 6873996 | Chand | Mar 2005 | B2 |
| 6904407 | Ritzel | Jun 2005 | B2 |
| 6912505 | Linden et al. | Jun 2005 | B2 |
| 6917952 | Dailey et al. | Jul 2005 | B1 |
| 6952688 | Goldman et al. | Oct 2005 | B1 |
| 6963867 | Ford et al. | Nov 2005 | B2 |
| 6973265 | Takahashi | Dec 2005 | B2 |
| 7016853 | Pereless et al. | Mar 2006 | B1 |
| 7043433 | Hejna | May 2006 | B2 |
| 7043443 | Firestone | May 2006 | B1 |
| 7043450 | Velez et al. | May 2006 | B2 |
| 7076483 | Preda et al. | Jul 2006 | B2 |
| 7080057 | Scarborough et al. | Jul 2006 | B2 |
| 7089237 | Turnbull et al. | Aug 2006 | B2 |
| 7096420 | Peikes | Aug 2006 | B1 |
| 7124353 | Goodwin et al. | Oct 2006 | B2 |
| 7137075 | Huang | Nov 2006 | B2 |
| 7146416 | Yoo et al. | Dec 2006 | B1 |
| 7191176 | McCall et al. | Mar 2007 | B2 |
| 7219073 | Taylor et al. | May 2007 | B1 |
| 7225187 | Dumais et al. | May 2007 | B2 |
| 7249121 | Bharat et al. | Jul 2007 | B1 |
| 7251658 | Dane et al. | Jul 2007 | B2 |
| 7292243 | Burke | Nov 2007 | B1 |
| 7379929 | Meteyer | May 2008 | B2 |
| 7424438 | Vianello | Sep 2008 | B2 |
| 7424469 | Ratnaparkhi | Sep 2008 | B2 |
| 7487104 | Sciuk | Feb 2009 | B2 |
| 7490086 | Joao | Feb 2009 | B2 |
| 7512612 | Akella | Mar 2009 | B1 |
| 7519621 | Harik | Apr 2009 | B2 |
| 7523387 | Greenwald et al. | Apr 2009 | B1 |
| 7613631 | Walker et al. | Nov 2009 | B2 |
| 7668950 | Horowitz et al. | Feb 2010 | B2 |
| 7702515 | Fujino et al. | Apr 2010 | B2 |
| 7711573 | Obeid | May 2010 | B1 |
| 7720791 | Hyder | May 2010 | B2 |
| 7734503 | Agarwal et al. | Jun 2010 | B2 |
| 7761320 | Fliess et al. | Jul 2010 | B2 |
| 7778872 | Kamangar et al. | Aug 2010 | B2 |
| 7827117 | MacDaniel et al. | Nov 2010 | B2 |
| 7865451 | Hyder | Jan 2011 | B2 |
| 7881963 | Chudnovsky | Feb 2011 | B2 |
| 8195657 | Dellovo | Jun 2012 | B1 |
| 8244551 | Mund | Aug 2012 | B1 |
| 8321275 | Collins et al. | Nov 2012 | B2 |
| 8375067 | Hyder | Feb 2013 | B2 |
| 8433713 | Chen | Apr 2013 | B2 |
| 8527510 | Chen | Sep 2013 | B2 |
| 8600931 | Wehrle | Dec 2013 | B1 |
| 8645817 | Fisher | Feb 2014 | B1 |
| 8914383 | Weinstein | Dec 2014 | B1 |
| 20010034630 | Mayer et al. | Oct 2001 | A1 |
| 20010037223 | Beery | Nov 2001 | A1 |
| 20010039508 | Nagler et al. | Nov 2001 | A1 |
| 20010042000 | Defoor, Jr. | Nov 2001 | A1 |
| 20010047347 | Perell et al. | Nov 2001 | A1 |
| 20010049674 | Talib et al. | Dec 2001 | A1 |
| 20020002479 | Almog et al. | Jan 2002 | A1 |
| 20020010614 | Arrowood | Jan 2002 | A1 |
| 20020024539 | Eleftheriadis et al. | Feb 2002 | A1 |
| 20020026452 | Baumgarten et al. | Feb 2002 | A1 |
| 20020038241 | Hiraga | Mar 2002 | A1 |
| 20020042733 | Lesandrini | Apr 2002 | A1 |
| 20020045154 | Wood | Apr 2002 | A1 |
| 20020046074 | Barton | Apr 2002 | A1 |
| 20020049774 | Ritzel | Apr 2002 | A1 |
| 20020055867 | Putnam et al. | May 2002 | A1 |
| 20020055870 | Thomas | May 2002 | A1 |
| 20020059228 | McCall et al. | May 2002 | A1 |
| 20020072946 | Richardson | Jun 2002 | A1 |
| 20020091629 | Danpour | Jul 2002 | A1 |
| 20020091669 | Puram et al. | Jul 2002 | A1 |
| 20020091689 | Wiens et al. | Jul 2002 | A1 |
| 20020095621 | Lawton | Jul 2002 | A1 |
| 20020103698 | Cantrell | Aug 2002 | A1 |
| 20020111843 | Wellenstein | Aug 2002 | A1 |
| 20020116203 | Cherry | Aug 2002 | A1 |
| 20020120506 | Hagen | Aug 2002 | A1 |
| 20020120532 | McGovern et al. | Aug 2002 | A1 |
| 20020123921 | Frazier | Sep 2002 | A1 |
| 20020124184 | Fichadia et al. | Sep 2002 | A1 |
| 20020128892 | Farenden | Sep 2002 | A1 |
| 20020133369 | Johnson | Sep 2002 | A1 |
| 20020143573 | Bryce et al. | Oct 2002 | A1 |
| 20020156674 | Okamoto et al. | Oct 2002 | A1 |
| 20020161602 | Dougherty et al. | Oct 2002 | A1 |
| 20020169669 | Stetson | Nov 2002 | A1 |
| 20020174008 | Noteboom | Nov 2002 | A1 |
| 20020194056 | Summers | Dec 2002 | A1 |
| 20020194161 | McNamee et al. | Dec 2002 | A1 |
| 20020194166 | Fowler | Dec 2002 | A1 |
| 20020195362 | Abe | Dec 2002 | A1 |
| 20020198882 | Linden et al. | Dec 2002 | A1 |
| 20030009437 | Seiler et al. | Jan 2003 | A1 |
| 20030009479 | Phair | Jan 2003 | A1 |
| 20030014294 | Yoneyama | Jan 2003 | A1 |
| 20030018621 | Steiner et al. | Jan 2003 | A1 |
| 20030023474 | Helweg-Larsen | Jan 2003 | A1 |
| 20030033292 | Meisel et al. | Feb 2003 | A1 |
| 20030037032 | Neece | Feb 2003 | A1 |
| 20030046139 | Beman et al. | Mar 2003 | A1 |
| 20030046152 | Colas et al. | Mar 2003 | A1 |
| 20030046311 | Baidya et al. | Mar 2003 | A1 |
| 20030046389 | Thieme | Mar 2003 | A1 |
| 20030061242 | Warmer et al. | Mar 2003 | A1 |
| 20030071852 | Stimac | Apr 2003 | A1 |
| 20030093322 | Sciuk | May 2003 | A1 |
| 20030125970 | Mittal et al. | Jul 2003 | A1 |
| 20030144996 | Moore, Jr. | Jul 2003 | A1 |
| 20030158855 | Farnham et al. | Aug 2003 | A1 |
| 20030160887 | Takahashi | Aug 2003 | A1 |
| 20030172145 | Nguyen | Sep 2003 | A1 |
| 20030177027 | DiMarco | Sep 2003 | A1 |
| 20030182171 | Vianello | Sep 2003 | A1 |
| 20030182173 | D'Elena et al. | Sep 2003 | A1 |
| 20030187680 | Fujino et al. | Oct 2003 | A1 |
| 20030187842 | Hyatt | Oct 2003 | A1 |
| 20030195877 | Ford et al. | Oct 2003 | A1 |
| 20030204439 | Cullen | Oct 2003 | A1 |
| 20030220811 | Fan et al. | Nov 2003 | A1 |
| 20030229638 | Carpenter et al. | Dec 2003 | A1 |
| 20040015371 | Thomas | Jan 2004 | A1 |
| 20040030566 | Brooks Rix | Feb 2004 | A1 |
| 20047006447 | Swauger | Apr 2004 | |
| 20040107112 | Cotter | Jun 2004 | A1 |
| 20040107192 | Joao | Jun 2004 | A1 |
| 20040111267 | Jadhav et al. | Jun 2004 | A1 |
| 20040117189 | Bennett | Jun 2004 | A1 |
| 20040128282 | Kleinberger et al. | Jul 2004 | A1 |
| 20040133413 | Beringer et al. | Jul 2004 | A1 |
| 20040138112 | Cassart | Jul 2004 | A1 |
| 20040148180 | Pajwani | Jul 2004 | A1 |
| 20040148220 | Freeman et al. | Jul 2004 | A1 |
| 20040163040 | Hansen | Aug 2004 | A1 |
| 20040186743 | Cordero | Sep 2004 | A1 |
| 20040186776 | Llach et al. | Sep 2004 | A1 |
| 20040193484 | Allen | Sep 2004 | A1 |
| 20040193582 | Smyth | Sep 2004 | A1 |
| 20040210565 | Lu | Oct 2004 | A1 |
| 20040210600 | Chand | Oct 2004 | A1 |
| 20040210661 | Thompson | Oct 2004 | A1 |
| 20040215793 | Ryan et al. | Oct 2004 | A1 |
| 20040219493 | Phillips | Nov 2004 | A1 |
| 20040225629 | Eder | Nov 2004 | A1 |
| 20040243428 | Black et al. | Dec 2004 | A1 |
| 20040249801 | Kapur | Dec 2004 | A1 |
| 20040267554 | Bowman et al. | Dec 2004 | A1 |
| 20040267595 | Woodings et al. | Dec 2004 | A1 |
| 20040267735 | Melham | Dec 2004 | A1 |
| 20050004927 | Singer | Jan 2005 | A1 |
| 20050033633 | LaPasta et al. | Feb 2005 | A1 |
| 20050033698 | Chapman | Feb 2005 | A1 |
| 20050050440 | Meteyer et al. | Mar 2005 | A1 |
| 20050055340 | Dresden | Mar 2005 | A1 |
| 20050060318 | Brickman | Mar 2005 | A1 |
| 20050080656 | Crow et al. | Apr 2005 | A1 |
| 20050080657 | Crow et al. | Apr 2005 | A1 |
| 20050080764 | Ito | Apr 2005 | A1 |
| 20050080795 | Kapur et al. | Apr 2005 | A1 |
| 20050083906 | Speicher | Apr 2005 | A1 |
| 20050096973 | Heyse et al. | May 2005 | A1 |
| 20050097204 | Horowitz et al. | May 2005 | A1 |
| 20050114203 | Savitsky et al. | May 2005 | A1 |
| 20050125283 | Fan et al. | Jun 2005 | A1 |
| 20050125408 | Somaroo et al. | Jun 2005 | A1 |
| 20050154701 | Parunak et al. | Jul 2005 | A1 |
| 20050154746 | Liu et al. | Jul 2005 | A1 |
| 20050170321 | Scully | Aug 2005 | A1 |
| 20050171867 | Doonan | Aug 2005 | A1 |
| 20050177408 | Miller | Aug 2005 | A1 |
| 20050192955 | Farrell | Sep 2005 | A1 |
| 20050210514 | Kittlaus et al. | Sep 2005 | A1 |
| 20050222901 | Agarwal et al. | Oct 2005 | A1 |
| 20050228709 | Segal | Oct 2005 | A1 |
| 20050240431 | Cotter | Oct 2005 | A1 |
| 20050273348 | Brooks Rix | Dec 2005 | A1 |
| 20050278205 | Kato | Dec 2005 | A1 |
| 20050278709 | Sridhar et al. | Dec 2005 | A1 |
| 20060010108 | Greenberg | Jan 2006 | A1 |
| 20060026067 | Nicholas et al. | Feb 2006 | A1 |
| 20060026075 | Dickerson et al. | Feb 2006 | A1 |
| 20060031107 | Aihara et al. | Feb 2006 | A1 |
| 20060047530 | So et al. | Mar 2006 | A1 |
| 20060069614 | Agarwal et al. | Mar 2006 | A1 |
| 20060080321 | Horn et al. | Apr 2006 | A1 |
| 20060100919 | Levine | May 2006 | A1 |
| 20060106636 | Segal | May 2006 | A1 |
| 20060116894 | DiMarco | Jun 2006 | A1 |
| 20060133595 | Ravishankar | Jun 2006 | A1 |
| 20060155698 | Vayssiere | Jul 2006 | A1 |
| 20060177210 | Ichimiya | Aug 2006 | A1 |
| 20060178896 | Sproul | Aug 2006 | A1 |
| 20060195362 | Jacobi et al. | Aug 2006 | A1 |
| 20060206448 | Hyder et al. | Sep 2006 | A1 |
| 20060206505 | Hyder et al. | Sep 2006 | A1 |
| 20060206517 | Hyder et al. | Sep 2006 | A1 |
| 20060206584 | Hyder et al. | Sep 2006 | A1 |
| 20060212466 | Hyder et al. | Sep 2006 | A1 |
| 20060229895 | Rosen et al. | Oct 2006 | A1 |
| 20060229896 | Rosen et al. | Oct 2006 | A1 |
| 20060235884 | Pfenninger | Oct 2006 | A1 |
| 20060265266 | Chen et al. | Nov 2006 | A1 |
| 20060265267 | Chen et al. | Nov 2006 | A1 |
| 20060265268 | Hyder et al. | Nov 2006 | A1 |
| 20060265269 | Hyder et al. | Nov 2006 | A1 |
| 20060265270 | Hyder et al. | Nov 2006 | A1 |
| 20060277102 | Agliozzo | Dec 2006 | A1 |
| 20070022188 | Kohs | Jan 2007 | A1 |
| 20070033064 | Abrahamsohn | Feb 2007 | A1 |
| 20070038636 | Zanghi et al. | Feb 2007 | A1 |
| 20070050257 | Fine | Mar 2007 | A1 |
| 20070054248 | Bare | Mar 2007 | A1 |
| 20070059671 | Mitchell | Mar 2007 | A1 |
| 20070100803 | Cava | May 2007 | A1 |
| 20070162323 | Gorham | Jul 2007 | A1 |
| 20070185884 | Kantamneni | Aug 2007 | A1 |
| 20070190504 | Schwartz et al. | Aug 2007 | A1 |
| 20070203710 | Habichler et al. | Aug 2007 | A1 |
| 20070203906 | Cone et al. | Aug 2007 | A1 |
| 20070218434 | Habichler et al. | Sep 2007 | A1 |
| 20070239777 | Toomey | Oct 2007 | A1 |
| 20070260597 | Crame | Nov 2007 | A1 |
| 20070271109 | Wang et al. | Nov 2007 | A1 |
| 20070273909 | Chen et al. | Nov 2007 | A1 |
| 20070288308 | Chen et al. | Dec 2007 | A1 |
| 20080059523 | Schmidt | Mar 2008 | A1 |
| 20080133343 | Hyder et al. | Jun 2008 | A1 |
| 20080133499 | Hyder et al. | Jun 2008 | A1 |
| 20080133595 | Hyder et al. | Jun 2008 | A1 |
| 20080140430 | Hyder | Jun 2008 | A1 |
| 20080140680 | Hyder et al. | Jun 2008 | A1 |
| 20080155588 | Roberts et al. | Jun 2008 | A1 |
| 20080275980 | Hansen | Nov 2008 | A1 |
| 20090138335 | Lieberman | May 2009 | A1 |
| 20090164282 | Goldberg | Jun 2009 | A1 |
| 20090198558 | Chen et al. | Aug 2009 | A1 |
| 20100082356 | Verma et al. | Apr 2010 | A1 |
| 20110060695 | Boyland | Mar 2011 | A1 |
| 20110134127 | Gundlapalli et al. | Jun 2011 | A1 |
| 20120226623 | Jurney et al. | Sep 2012 | A1 |
| 20140244534 | Simmons et al. | Aug 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 104001976 | Aug 2014 | CN |
| 1085751 | Dec 2002 | EP |
| 1596535 | May 2004 | EP |
| 63-246709 | Oct 1988 | JP |
| 6-265774 | Sep 1994 | JP |
| 6-313844 | Nov 1994 | JP |
| 7-287161 | Oct 1995 | JP |
| 8-76174 | Mar 1996 | JP |
| 61-62011 | Mar 1996 | JP |
| 8-292366 | May 1996 | JP |
| 8-286103 | Nov 1996 | JP |
| 10-26723 | Jan 1998 | JP |
| 2001-083407 | Mar 2001 | JP |
| 2002203030 | Jul 2002 | JP |
| 2002251448 | Sep 2002 | JP |
| 2004062834 | Feb 2004 | JP |
| 2005109370 | Nov 2005 | JP |
| 0026839 | May 2000 | WO |
| 0148666 | Feb 2001 | WO |
| 0146870 | Jun 2001 | WO |
| Entry |
|---|
| “yahoo!_hotjobs” (webpage, published Apr. 1, 2005 and dowmloaded from http://web.archive.org/web/2005040109545/hotjobs.yahoo.com/jobs/ on Dec. 11, 2009. |
| Greg Linden, Brent Smith, Jeremy York, “Amazon.com Recommendations Item-to_item Collaborative Filtering,” IEEE Internet Computing, vol. 7, No. 1, Jan./Feb. 2003: 76-80. University of Maryland. Department of Computer Science. Dec. 2, 2009 <http://www.cs.umd.edu/˜samir/498/Amazon-Recommedations.pdf>. |
| Bettman, James R., “A Threshold Model of Attribute Satisfaction Decisions.” Journal of Consumer Research Policy Board, pp. 30-35, 1974. |
| Hotjob webpag, published Apr. 1, 2005 and downloaded from http://web.archive.org/web/20050401095045/hotjobs.yahoo.com/ on Dec. 11, 2009. |
| Notice of Acceptance on Australian patent application No. 2007249205 dated Mar. 12, 2013. |
| International search report and written opinion for PCT/US2007/068913 dated Nov. 30, 2007. |
| International search report and written opinion for PCT/US2007/068914 dated Dec. 7, 2007. |
| International search report and written opinion for PCT/US2007/068916 dated Feb. 22, 2008. |
| International search report and written opinion for PCT/US2007/068917 dated Nov. 30, 2007. |
| Examiner first report on Australian patent application No. 2007249205 dated Jun. 30, 2011. |
| Examiner's search information statement on Australian patent application No. 2007249205 dated Jun. 29, 2011. |
| “Commsland: Contractors cut out the middleman.” M2 Presswire. Coventry: Nov. 5, 2002, p. 1. |
| Hallet, Karen Schreier. “Mastering the expanding Lexis-Nexis academic universe,” EContent. Wilton: Oct./Nov. 1999. vol. 22, Iss. 5, p. 47. |
| Hayes, heather B. “Hiring on the Fast Track,” Federal Computer Week, Falls Church: Jul. 29, 2002, vol. 16, Iss. 26, p. 26. |
| “Steve Wynn Begins Search for 9000 Employees fro Wynn Las Vegas.” PR Newswire. New York: Nov. 8, 2004. p. 4. |
| M. Balabanovic et al. (Mar. 1997). “Fab: content-Based, Collaborative Recommendation,” Communications of the ACM 40(3): 66-72. |
| Bettman, James R., “A Threshold Model of Attribute Satisfaction decisions”, Joournsumer Research Policy Board, pp. 30-35 (1974). |
| “Key” Oxford English Dictionary Online, located at <http://dictionary.oed.com>, last accessed on Sep. 23, 2006 (34 pgs). |
| Calishan, T. et al., “Google Hacks” First Printing, pp. 18-24, 33, 288-289, 293-297, Feb. 2003. |
| Dialog Chronolog., “New Features on DialogWeb TM”, Sep. 1998 (2 pgs). |
| Dialog Information Services, “DialogOnDisc User's Guide”, Version 4.0 for DOS, (Jan. 1992) pp. v1, (c), 2-1, 2-2, 3-4, 3-5, 3-9, 3-10, 3-11, 3-15, 3-17, 3-19, 3-21, 4-11, 4-21, 4-22, 4-27, 5-2, 5-7, 5-8, 5-9, 2-10, 5-11, c-2. |
| Dialog Information Services, “DialogLink for the WindowsTM Operating SystemUser's Guide”, (May 1995) Version 2.1 pp. 1-2, 1-3, 4-1, 4-2, 5-2, 5-3. |
| DialogLink, “DialogLink for Windows and Machintosh: User's Guide”, Dec. 1993, Version 2.01, P/ (cover sheet), (3-11). |
| dictionary.oed.com, “Oxford English Dictionary”, 1989-1997, retrieved Sep. 23, 2006, 2nd Ed. (34 pgs). |
| Genova, Z. et al., “Efficient Summarization of URLs using CRC32 for Implementing URL Switching”, Proceedings of the 37th Annual IEEE Conference on Local Computer Networks LCN'02, Nov. 2002 (2 pgs.) |
| Hammami, M. et al., “Webguard: Web Based Adult Content and Filtering System”, Proceedings of the IEEE/WIC Conference on Web Intelligence, Oct. 2003 (5 pgs.). |
| Lam-Adesina, A.M. et al., “Applying Summarization Techniques for Term Selection in Relevance Feedback”, SIGIR'01, ACM Press, Sep. 9, 2001 (9 pgs). |
| Merriam-Webster.com, “Merriam Webster Thesaurus”, located at <http://web.archive.org/web/20030204132348http://www.m-w.com>, visited on Feb. 4, 2003 (7 pgs). |
| Netcraft, Site Report for “www.dialoweb.com”, (May 10, 1998), located at <http://toolbar.netcraft.com/site_report?url=http://www.dialogweb.com> last visited on Sep. 27, 2006, (1 pg). |
| OED.com, “Definition of prescribed”, Dec. 2003, retrieved Mar. 3, 2008, located at <http://dictionary.oed.com/cgi/ent...>(2 pgs). |
| Salton, G., “Abstracts of Articles in the Information Retrieval Area Selected by Gerald Salton”, ACM Portal: 39-50 (1986). |
| Sherman, C. “Google Power, Unleash the Full Potential of Google”, McGraw-Hill/Osboume, Aug. 23, 2005, pp. 42-47, 77, 80-81, 100-107, 328-239, 421-422 |
| Sugiura, A. et al., “Query Routing for Web search engines: Architecture and Experiments”, Computer Networks 2000, pp. 417-429, Jun. 2000, located at www.elsevier.com/locate/comnet. |
| Thomson Dialog. (2003) “DialogWeb Command Search Tutorial”, Dialog Web Version 2.0, located at <http://support.dialog.com/techdocs/dialogweb_command_tutorial.pdf#search=%22dialogweb%22> last visited on Dec. 10, 2002, (23 pgs). |
| Thomson Products, Extrinsic Evidence of the Common Ownership and Distribution of DialogWeb & DialogOnDisc, located at <http://dialog.com/contacts/forms/member.shtml>, <http://dialog.com/products/platform/webinterface.shtml>, and <http://dialog.com/products/platform/desktop_app.shtml> last visited on Sep. 27, 2006 (3 pgs). |
| Balabanovic, M. et al. “Fab: Content-Based, Collaborative Recommendation”, Communications of the ACM 40 (3):66-72, (Mar. 1997). |
| Kawano, H. et al., “Mondou: Web Search Engine with Textual Data Mining”, 0-7803-3905, IEEE, pp. 402-405 (Mar. 1997). |
| Tanaka, M. et al., “Intelligent System for Topic Survey in MEDLINE by Keyword Recommendation and Learning Text Characteristics”, Genome Informatics 11:73-82, (2000). |
| Donath et al., “The Sociable Web” located at <http://web.web.archive.org/web/19980216205524/http://judith.www.media> visited on Aug. 14, 2003 (4 pgs). |
| Liu, Yi et al., “Affinity Rank: A New Scheme for Efficient Web Search”, AMC 1-85113-912-8/04/0005, pp. 338-339 (May 2004). |
| Ji, Minwen, “Affinity-Based Management of Main Memory Database Clusters”, AMC Transactions on Internet Technology, 2(4):307-339 (Nov. 2002). |
| Careerbuilder.com “My Job Recommendations,” located at <http://www.careerbuilder.com/JobSeeker/Resumes/MyNewJobRecommendationsOrganized.aspx?sc_cmp2=JS_Nav_JobsRecs> visited on Oct. 1, 2007 (2pgs). |
| Careerbuilder.com “Post Your Resume on Careerbuilder.com,” located at <http://www.careerbuilder.com/JobSeeker/Resumes/PostResumeNew/PostYourResume.aspx?ff=2> visited Oct. 1, 2007 (3 pgs). |
| Number | Date | Country | |
|---|---|---|---|
| 60757781 | Jan 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13450207 | Apr 2012 | US |
| Child | 14244415 | US | |
| Parent | 11614845 | Dec 2006 | US |
| Child | 13450207 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11383412 | May 2006 | US |
| Child | 11614845 | US |
