Rewrote and extended the contents.xq code to add:

• Sorting by document type (previously missing from the sort parameters, for some reason)
• XML <list> elements containing items for each distinct value of year, author, title (truncated), vol/issue, and content type.
• Addition of @rend attribute for an item in the list which matches an existing search parameter.

This will enable easy creation of drop-down lists with correctly-selected values in the XSLT which processes the contents page.

The next stage is to plan how that XSLT will be written -- in particular, how it will work with the rest of the site. I'm assuming at this stage that we'll want a standard set of processing libraries for the non-article site content, and that this content will be drawn from the db as well (although perhaps from another area of the db). I'll need to look at the strings components we have in the db, to see if it's going to be sufficient to build all the surrounding content with those alone, or whether we'll need some user-editable XML files for menus, headers, footers etc.