|Jong Hann wrote:
>>You don't need to do anything special to your source documents to
>>get them to display in a hierarchical browse structure. The only
>>time you may need to edit the source is if you wish to display your
>>documents with their own table of contents. I'd suggest you not do
>>that until you get everything else sorted.
> Well, Greenstone's demo config does have a hierarchy (books are filed
> into different "Organization" categories), so there's no question
> about Greenstone's capabilities to solve my particular problems.
> I was guessing that Greenstone's designers forgot to include source
> documents in that demo (or example). But now I learn (from you) that I
> don't have to edit the source to get that hierarchical structure.
The source documents and configuration files for the demo collection
should be included with all our distributions of greenstone.
> Fact is, you have stated that I don't need to do anything special to
> my source documents to get Greenstone to display them in a
> hierarchical browse structure. This fact is... rather puzzling (or
> scary, if seen in another perspective explained below).
> Suppose I want a sub-set `A' of documents to fall under category
> `B_Cat', and a sub-set `B' of documents under `A_Cat'. (The A-to-B
> counter-intuitive flip is deliberate to illustrate a point). How would
> the Collector know to sort my documents thus, without my instruction?
The Collector is a fairly simple front-end to building collections.
If you want to setup hierarchical browsing categories, you will need
to create the configuration files for this yourself.
I suggest you read the greenstone manuals, since they describe in detail how to use greenstone and get the most out of your collections. At the very least, you should read the section on "Classifiers" in the Developers Guide since that explains exactly how to use the Hierarchy classifier.