From: Mark T. <mt...@nl...> - 2010-09-14 21:00:58
|
Ah, good point. I've modified the code to look for the "bibleech" Java System property if the "BIBLEECH" environment isn't set and have modified the browse indexing script to use that instead. Changes again pushed to: https://vufind.svn.sourceforge.net/svnroot/vufind/branches/alphabetic-browse-fixes The "BIBLEECH" class get used here: https://code.nla.gov.au/redmine/projects/nlabrowse/repository/revisions/master/entry/browse-indexing/PrintBrowseHeadings.java#L118 and is responsible for doing the extraction of sort keys and headings from the Lucene indexes. The default "Leech" implementation just enumerates the value of a single field, whereas the VuFindTitleLeech takes the sort key values from the title sort field, and the heading values from title field. Leech was a silly name really :) Demian Katz <dem...@vi...> writes: > Thanks for doing this so quickly! Just one question -- how is the > BIBLEECH environment variable being used? Is the Java looking for > this value explicitly? Would it be better to make this a new > parameter to the build_browse function which then gets passed to Java > via a command-line property setting? I'm starting to think about the > Windows batch file port of the current shell script, and I think life > would be a little easier if I could avoid having to manipulate the > environment (it might or might not be a problem... but it seems like a > potential source of platform-specific eccentricities that we might as > well stay away from if we can). -- Mark Triggs <mt...@nl...> |