lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson" <>
Subject Re: Advise for Mediabase with Lucene
Date Thu, 02 Oct 2008 21:37:06 GMT
Well, that depends (tm). What do you expect Lucene to do for you?
Lucene would e a fine tool for creating a keywords index, searching
it, etc. Really, the rest of the stuff in step <2>. Conceptually, you'd
store each file as a document, with several fields. Say

then mix-n-match your search queries to allow you to construct the
page you're returning to the user.

You could do the navigation thing by searching for filepaths that
begin with the correct fragment, then display that.

But rendering, moving files around, etc would be up to the rest
of your framework.


On Thu, Oct 2, 2008 at 5:23 PM, Mathias P.W Nilsson <>wrote:

> Hi!
> I'm currently developing a mediabase for 20-100 customers. A Customer can
> upload a file, folder via ftp and a file grabber searches the file system
> and adds the new file to a mysql database. It also creates thumbnails, adds
> search words etc. Now, this mediabase is pretty old and is developed in php
> for the web and the server that monitors events on the file system is java
> based.
> I want to recreate the mediabase with Wicket as web framework and lucene as
> file indexer and have Spring manage the File grabber thread.
> This is what I want to do.
> 1.) Create a file grabber that searches files and folders for new files.
> 2. ) Add keywords to the file. ( The folder path, file size, user rights,
> index the content in the document )
> 3.) Make the files and folders searchable. Tree view for all the folders
> and
> when a user clicks on a folder branch the files in that folder will be
> visible for the user.
> Is Lucene the right tool for me?
> --
> View this message in context:
> Sent from the Lucene - Java Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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