You have a couple of options for presenting hierarchy (and other
structural relationships) between separate items in Greenstone.
One way is to use the hierarchy classifier, which is documented
in chapter 2 of the Greenstone Developer's Guide ("Getting the
most out of your documents"). Another option, as you suggested,
is to keep parent or children identifiers in metadata. However,
this is a little problematic because the hash identifier used
for displaying a specific item in Greenstone changes if there is
any change to that item. If your collection isn't static then
you need some way of managing the identifiers when they change.
This collection uses both of those options. It is a comic book
serial with separate items for each article. The "table of
contents" available from an issue item uses the hierarchy
classifier to display a list of articles. From any article,
you can access the issue it is part of with a link created from
the Dublin Core relation.ispartof metadata element that goes
through a simple CGI registry that maps our stable id to the
current Greenstone hash id. This registry is automatically
updated everytime the collection is rebuilt.
On Sun, July 16, 2006 2:17 am, Lost Samoan \(Corporate\) wrote:
> I have a library of books but each chapter is a separate file. I wish to
> present the books with a book>chapter hierarchy (as seen in the demo) but
> rather than combining the chapters into a single file and placing section
> metadata within, is it possible to apply a hierarchical relationship
> between files (maybe in the meta data)? Thank you for any suggestions.
> Colin J. Murfett
> Lost Samoan (Corporate)