[NBP web-reskin] Regarding Swish indexer

[Ethan Rowe]

All,

We've looked into the Swish index matter a bit.

The index files are built on a nightly basis in production.  They don't
exist in your camp without some preparation.  If you want to create the
index in your camp so that you won't get hard errors from the site
search, you can run:
  (for camp26, for example)
  /usr/local/bin/swish-e -c \
   /home/fidelity_camp/camp26/catalogs/nbp/etc/swish/site_search.conf \
   -S prog

That'll run for a little while and built the Swish-e index files that
the site search relies upon.

However, you're not likely to find the results all that satisfying,
because the revamped pages, from what we're seeing, mostly involve the
deletion of text content and the introduction of images.  The site
indexer focuses on text and doesn't do much with images.

Consequently, we can run the indexer, but the newly-revamped pages won't
really do great in the results because they have relatively little
content to index.  That's based on a camp built yesterday; perhaps there
are some outstanding commits that haven't been pushed upstream yet that
would change the content situation?

I think it would probably make sense to get all your reskin efforts more
settled, disregarding the search index matters for the duration, and
then let me dig into the concerns for the site search indexer at the
end.  Does that seem reasonable?

Thanks.
- Ethan
-- 
Ethan Rowe
End Point Corporation
ethan at endpoint.com