Review current search facilities (including how to deal with protected
resources). Investigate how people search and the possibility of providing
extra search facilities (see "Wolfram Alpha",
"Ask.com", "A Study of Web
Search
Trends", "Lost in
Cyberspace: Where to Go? What to
Believe?", "More
Effective Web Search Using Bigrams and Trigrams") .
jmrm notes that "Search in the context of the University's websites as whole is quite a
hot topic at the moment and Autonomy's search product has received some
attention as having technology better suited to an organisation's web
site rather than Google-type solutions which rely on vast numbers of pages
and users."

New System design and delivery

Use a CMS? jmrm writes "day.com's content management looks quite good but [is] by no means cheap. It's
based on free software, e.g. jackrabbit and sling, which the next version of
CamTools will also be using so there would be a commonality of underlying
data format, etc. Bits of the CMS are also, I think, public domain and there's
a free download at http://dev.day.com/microsling/content/blogs/main.html
along with some comments on Content Integration Standards. This might be
useful technology for generating and maintaining help pages, indexing them,
and keeping a consistent style. http://www.day.com generally has some useful
material."

Have our own CUED CamTools? Write a CamTools extension?

More reporting tools? jmrm wrote "How do we ensure up-to-dateness and lack of duplication in our web pages. ... I at least would actually welcome a system like RT's that
nags me if I forget provided that, like RT, it provides a mechanism for
me to close the ticket ... Maybe we should simply have an RT queue for web pages
needing attention with the ticket assigned at the outset to the author?"