LLT has approved the following recommendations to convert Camelot to a Wiki.

1. The Camelot website is replaced by a wiki progressively over the next 12 months
2. Documents are either converted to wiki pages or the link refers to the original document on the appropriate drive. Duplicate documents should not be stored in the wiki as attachments.
3. Counterculture for Library staff news will remain unchanged.
4. A guide to wiki contributions be created (in the wiki)

If you have ideas on which areas of Camelot should be converted first, please add them as a comment or email Library IT. It will be easier if we can concentrate on particular areas rather than convert on a file by file basis. For example Library IT would like to work on our section of the “How to” area including IT Help as it will be faster to update in a wiki. New projects should have a wiki area. There may be other high use areas that would be good to convert first.

Camelot has 7,058 files in 829 directories, but only 477 files have been updated in the last year and around 1,000 files accessed, so it can be trimmed significantly.

Advantages of moving to the university wiki
• Any library staff member can edit a page without needing Dreamweaver or html knowledge
• Editing pages is much faster than using Dreamweaver
• Often Camelot files duplicate documents unnecessarily on Library drives and can get out-of-date
• Many files on Camelot are old and/or outdated so a cleanup will be very useful
• While in general there should be open access in Camelot for Library staff to edit files, some areas such as SOPs or the LLT area could be limited to particular staff to view or edit
• Library staff can become comfortable with a collaborative Web 2.0 open access environment in a controlled area.
• Library staff will become familiar with the same wiki software used across the university including students in Moodle
• The University retains ownership and control of the data unlike external wikis such as PBWiki currently used by the Engineering Library where there could be potential security or privacy issues with the content.
• Collaborative wiki spaces on Camelot will be very useful for projects
• The wiki has much better searching and tagging capabilities
• Ability to track changes, see history/how content has evolved
• Ability to access Camelot remotely

Disadvantages
• Library staff will need to login to Camelot via the wiki
• There will be some confusion during the conversion period, particularly for searching, but this can be minimised in a number of ways including prioritising which areas will be converted.

Comments most welcome. Cheers, Anne