More about installing the New Clio System
ClioWeb is the patron Web interface portion of the Clio System. Getting it running is the most complicated and variable part of setting up the new Clio System, since exactly how much help you'll need from your IT department with setting up ClioWeb depends a bit on how things are set up in your network. In some cases, an IT person can create a directory on your web server where ClioWeb will live, copy in its files, make some settings and it's done. In other situations there can be a bit of fiddling required to get file permissions just right or to get the web site to communicate with the mail server.
To be more specific, here is a list of the things that need to be accomplished when setting up ClioWeb:
- Create a Virtual Directory, set up as an ASP 2.0 application using IIS (6.0 or better)
- Decide on a location for the central database - the file/directory will need to allow read/write/modify privileges from both the web application's user account and the desktop applications
- Set those permissions accordingly
- Set permissions to allow the web application to modify its own settings files
- Enter settings for your smtp server (and verify that the smtp server will forward mail to 'outside' addresses)
- (If you want to use an LDAP server for authentication) Enter and test settings for ldap server
- Create a backup process for the central database file
All these items are verified with a test application first. Once that's done, things are pretty easy: the real application is copied into place and you can customize the look/feel as much or as little as you like. We provide minimal formatting in a set of CSS files and you can modify those or replace them with your own to make our pages fit seamlessly into your library's website. We've had customers take approaches on either extreme.
Once your site is up and running, updates are delivered as a zip file along with an update page; when you put them in place and navigate to the update page a button click takes care of replacing old files and making any structural changes to the application.
It's useful, though not required, for someone in the ILL office to have access to the one of the settings files on the website, particularly during the initial setup process. Most of the functional customizing is done through the Staff interface of the site but there are a few things that the ILL folks may want to change in that settings file directly.