Yes, I did find that page earlier and have rebuilt the index. Perhaps I am misunderstanding how this class works. In my directory structure above, each of the three parent directories (Trunking_and_Access, NetX and SBC) may have one or more subdirectories which correspond to product releases.

Does each document in the directory structure require a field that then identifies the relationship to its parent ? In the page you referenced, it states the following:

The document text1.txt would need to have a field with the following format:
@field : c; c|folder1;

Does this mean that each document in my directory ./Trunking_and_Access/Release_8.x/Release_8.2/Access8.2/ASX_8.1_Feature_TOI would have to have the following line added ?

Thanks for the clarification. Then I do not want to use that class. Is there a way to present the Facets in a hierarchical manner that reflects the directory structure ? I guess you can think of this as being a hierarchy of facets. May not be possible but just thought I would ask. My alternative is to create a Facet for each parent directory (Trunking and Access, SBC and NetX). This is related to my other question about 'data-id'. I'll wait for Mark to respond.