[opencms-dev] Indexing offline project - proposal for more useful setting than 'auto'

Jonathan Woods jonathan.woods at scintillance.com
Tue Jun 6 08:32:14 CEST 2006


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.
 
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.
 
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?
 
Jon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20060606/d19017de/attachment.htm>


More information about the opencms-dev mailing list