lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Keegan" <peterlkee...@gmail.com>
Subject Announcement: Lucene powering Monster job search index (Beta)
Date Fri, 27 Oct 2006 19:29:20 GMT
I am pleased to announce the launch of Monster's new job search Beta web
site, powered by Lucene, at: http://jobsearch.beta.monster.com (notice the
Lucene logo at the bottom of the page!).

The jobs index is implemented with Java Lucene 2.0 on 64-bit Windows (AMD
and Intel processors)

Here are some of the new features:

1. 'Improve your search by'...

The job search results page allows you to browse and 'drill down' through
the results by job category, status, type and salary. The number of matching
jobs in each facet is displayed. There will likely be many more facets to
browse by in the future.

This feature is currently implemented with a custom HitCollector and the
DocSet class from Solr.

2. 'More like this'

Find more jobs like the one you see by clicking on the 'MORE LIKE THIS'
link, which is visible when you hover the mouse over the job title.

This feature is implemented with Lucene's term vectors and the
'MoreLikeThis' contribution class. If you are in 'detailed view', the term
vectors from the job description are used. In 'brief' view, the job title's
term vectors are used.

3. 'Related Titles'

When you do a 'keywords' search, click on a 'related titles' link to filter
you search by similar job titles.

This feature is implemented via a separate Lucene.Net index.

4. Sort by 'Miles'

Find jobs close to you via zip code/radius search. In the search results
page, click on the 'Miles' column to sort the results by distance from your
zip code/radius.

This custom sorting feature is implemented via Lucene's
'SortComparatorSource' interface.

5. Search by date, salary, distance.

Find jobs posted in the last day (or 2,3, etc) or by salary range or
distance.

Numeric range search is one of Lucene's weak points (performance-wise) so we
have implemented this with a custom HitCollector and an extension to the
Lucene index files that stores the numeric field values for all documents.

It is important to point out that this has all been implemented with the
stock Lucene 2.0 library. No code changes were made to the Lucene core.

If you have any feedback regarding the UI, please use the link on the web
page ("send us your feedback"). You can hit me with any other
questions/comments.

Peter

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message