Actually, one of the things we are currently working on here needs this
extension to PagedImgPlug. (I didn't realise this in my last email).
Over the next couple of days, we will be modifying the .item file format
so that you can have metadata for each page, and can have hierarchically
If you like, I can send you this when its finished. This might save you
a bit of work. (But of course feel free to do it yourself if you want to
You'd still need to work on the interface to get eg the TOC on its own
page and not with each page. You can work on this with the current
PagedImgPlug - use the hierarchy mode to have the table of contents. (it
will just be flat in the meantime).
To get it expanded automatically, you need the gc=1 arg.
Gus Clifton wrote:
> Hi Katherine,
>> Re hierarchical documents. Is the document style in the demo collection
>> suitable for what you want? I.e. there is a hierarchical table of
>> contents at the top of each document page, you can click around the
>> table of contents to get to different sections, and also there are next
>> and previous buttons.
>> Or do you want the table of contents to be on a separate page?
> Yes, we'd like the toc to be a separate page, and the first page that
> the user comes to after selecting the item.
>> If you are happy with the demo collection style, then using the toc mode
>> for pagedimg plug gets you part way there - it gives you that style of
>> interface, but the toc will have a flat structure.
>> To do a proper hierarchy, we need to change the .item file structure
>> (and therefore the plugin) so that you can represent subsections. This
>> is something we have talked about doing, but is not in our immediate job
> Exactly- instead of a flat toc with folder icons that you can click to
> expand (on another page), we'd like them already expanded and indented,
> even though this will cause the toc to be much longer a lot of the time.
> I know a little Perl, and I'm taking a look at the plugin right now.
> I'll let you know what I come up with in the coming week...
> Thank you, Katherine!