<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=320515905-06062006><FONT face=Arial size=2>In
opencms-search.xml, the online and offline projects can be set to have their
Lucene indexes rebuilt automatically using rebuild=auto - but as it's
currently implemented, this isn't much good for the offline project. Even
with this setting, he offline project index is only brought up to date when
resources are published - i.e. when they're in the online project (and index) in
any case.</FONT></SPAN></DIV>
<DIV><SPAN class=320515905-06062006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=320515905-06062006><FONT face=Arial size=2>For dynamic sites
where much depends on the contents of the Lucene index, the current situation
means that content managers can't see the effects of their work without
publishing everything. It would be great if the 'auto' setting were
renamed 'onPublication', and there were a new setting for all non-online
projects called 'onSave' or something like that. The new setting would
incrementally re-index saved resources to keep (e.g.) offline indexes up to
date.</FONT></SPAN></DIV>
<DIV><SPAN class=320515905-06062006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=320515905-06062006><FONT face=Arial size=2>I realise there'd be
some details to iron out - e.g. what does 'saved' mean, and should only unlocked
resources be re-indexed? - but this feels like a useful piece of new
functionality. Any comments?</FONT></SPAN></DIV>
<DIV><SPAN class=320515905-06062006><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=320515905-06062006><FONT face=Arial
size=2>Jon</FONT></SPAN></DIV></BODY></HTML>