How configurable is the ROADS user interface?
Very flexible. Most of the HTML generated by the ROADS software is based on configurable skeleton files – including the rendering of search results. Compare results from the eLib project database, SOSIG and ADAM for example. There is no reason why skeleton files couldn’t contain JavaScript and make use of cookies to configure the output further – though I don’t think anyone is doing this yet. ROADS also contains support for I18N based on client supplied HTTP headers.