> 1 - Quite frequently when I "Build Collection," it will complete to 100%
> and then generate an error message: "Exception detected during
> collection install. Most likely caused by Windows or Local Library
> holding locks on files: Index directory cannot be removed." A second
> run-through then generally completes successfully and allows the
> preview. At first I thought the error was occuring because I had a
> document from the collection or a config file open in another program,
> but it still happens even when all files that Greenstone is accessing
> are closed in other programs. Platform is Windows 2000.
Yes, this is a known bug which we are currently working on.
> 2 - It seems that manual changes to the collect.cfg file are overridden
> by the next build of the collection, to reflect the settings in the
> Librarian. At least that is happening each time I try a manual edit.
> Is that always the case? If yes, where does one add a line such as
> "groupsize," as I see no place for it in the Librarian menus.
Yes, this is also true. If you want to manually edit the config file,
you will need to close the collection in the Librarian before making the
Theoretically all options should be available from the Librarian itself,
but there may be some that we have missed.
Try setting the mode to Library Systems Specialist or Expert (under
File/Preferences/Mode) and then looking for the options. The groupsize
option is under Import Options on the Create pane.
> 3 - I've set up browse indexes to include DateList, however, when I
> click on Date in order to browse by date, I get an error "server.exe is
> shutting down. An error log is being generated." Well, the error logs
> appear to be empty and I'm not sure why it is choking on DateList.
I have recently changed the Datelist to allow using namespaced Dates eg
dc.Date. Partway through the changes you might have gotten errors like
the above, but I thought I had fixed it so that it all works. I have
just tried it here on linux and windows XP and the DateList works.
Perhaps if you send me your config file, and tell me what Date metadata
you have, I could have a look for you.
> 4 - And a question more about the philosophy of buildilng a collection -
> when might it be better to include metadata in the document itself vs.
> including it from the Librarian and/or a separate metadata file? If
> it's included from the Librarian, is it ever exportable should we
> migrate to a different program some day?
The Librarian stores metadata in the collection in metadata.xml files -
so it is exportable in that you could write XSLT or a script to convert
the metadata to some other form.