Web Opac -- Webpac Pro

Need to begin serious work on Webpac Pro.

Plan:

• Review latest info on CSDirect
• Make sure I have latest downloads
• Check for wwwoptions files for sites that are good
• Check for my experimental briefcit files
• Check IUG clearinghouse for webpub.def examples

In addition, ask other librarians to take a look at Encore at ACRL.

Ban the word "re-design"

Interesting thought from Louis Rosenfeld via David King. It's not that we don't do this, it's just that we may not think about it this way. The RSS feed from David's site is short and can be quoted here. (http://www.davidleeking.com/2007/02/20/design-for-your-audience/)

Louis Rosenfeld has started a 5-part series on Information Architecture. Part one includes this:

Step #1: Ban the word “redesign” from your meetings.
Step #2: Determine who your most important audiences are.
Step #3: Determine each primary audience’s 3-5 major needs.
Step #4: Make damned sure your site addresses each of those needs.

Great words of wisdom, I think! Now… who are your library’s most important audiences?

Update on reference wiki

I submitted a proposal to Richard before the winter break to load wiki software on the IRT server since I really did not get a response from Melanie that was adequate after her initial refusal saying that it was inappropriate to do. Here is the gist of the email and the proposal:

Email:
Julie asked me to submit a request to you about loading wiki software on an IRT server. I previously sent a preliminary request to Melanie, Stevan, and Jen Weber in early November -- not being certain which was the best person to ask. Melanie responded that she felt it was not an appropriate service to put on an IRT server and suggesting a public wiki.
Since we felt a public wiki is not appropriate for this use, I'd like to put forth this proposal to you. The rationale is in the attached document. The software that appears to be a best fit for us is called Perspective. I've included links in the document.

Let me reiterate that we don't expect other IRT staff to run this wiki for us although they would certainly have to help us load and setup the software to their satisfaction. It is also possible that the software could be used for a wiki for some other IRT department. However, I haven't explored its capability for multiple wikis.

Proposal:

Proposal for a Library Services Reference Wiki

For several years we have been trying to use the InsideLS site to promulgate information, policies, procedures, and guidelines for the reference desk librarians. Since we have to rely upon so many adjunct refernce librarians to staff the desks at each campus and these librarians come and go, we have found it difficult to adequately share information in a timely manner. As we strive for consistency of service, we recognize that, although location may drive some idiosyncratic practices, a common tool easily accessible to library staff and easily updateable would be a good way to serve our students and employees better.

After considering several approaches, including content management software, we think that a wiki might be a good solution for us. Since some of the information contained in the wiki is not appropriate for viewing by those outside of the library staff, the wiki should be password protected and not easily available to others. This is why I am proposing that we load wiki software on an IRT server and make it accessible to all librarians, even adjuncts.

à I first suggested Flexwiki because I know it runs on Windows servers, but I am open to other software. In particular, I’d like to find software that makes it very easy for unskilled librarians to add pages and topics as well as to edit existing content.

à Another possible wiki that can run on Windows servers is Perspective. It’s fairly easy to use and edit.

(http://www.high-beyond.com/perspective.aspx?action=view&page=perspective:Welcome)

This one would seem to be a possible best choice. The documentation is easy to read and it looks like it would be easy to set up and control security and authentication.

(http://www.high-beyond.com/perspective.aspx?action=view&page=documentation:Index)

o I’ve experimented with their demo editing and it is very easy to edit and to attach files and insert images.

Some example of libraries using wikis:

Note: Most of the library wikis I see run on Linnux or Unix servers.

à Uconn wiki.lib.ucon (http://wiki.lib.uconn.edu/wiki/Main_Page)

à Univ of Minn staff pages (http://wiki.lib.umn.edu/)

à Ohio Univ Biz Wiki

à LaGuardia CC Ref Desk

à Baruch’s Newman Library ref handbook

à Virtual Reference Wikis (http://vrsig.pbwiki.com/Wikis) lists a number of library wikis

We would not expect other IRT staff to run the wiki for us. After some preliminary work to load and initially set up the software, we would expect that the program would be maintained and updated by Library Services staff. Initally that would probably be Margaret Peloquin, Steven Self, and Teresa Ashley. [Of course, the front end would be accessible and editiable by all full-time and adjunct reference librarians.]

Wiki for the Ref Desk

I've been fiddling around with trying to solve a problem that the reference
librarians have with sharing information about sources and class assignments,
etc. We played around with the idea of a blog, but that isn't really what we
need. I think a Wiki would be a good tool to use. There are some Windows-based wiki software programs. I've taken a look at some and am favoring one called Flexwiki

http://www.flexwiki.com/default.aspx

Live Chat link on the navigation bar

Red fielded a complaint about the color contrast of the Live Chat link on the home page navigation bar. He asked if I could change it.

>Red Wassenich  said:
>
> > A faculty member said we should not have the link to chat on the home
> > page not be in red letters. He said it was hard to see due to lack of
> > contrast. I agree.

I informed the Web Cmte and asked for suggestions:

>Shall I make it cyan?  Julie likes the current color but really just wants it
>to stand out.  I use cyan on the second catalog pages if you want to look at
>what it might look like.  Then I'll run it by the Web Cmte before making the
>change.
>
>As an aside, I wanted to make it different, but didn't want to make it so
>different from the ACC homepage so I chose a color that stood out just a
>little from the other nav links.  This is the first adverse comment we have
>got on it.

...... Committee replies .......
> I would make it the yellow color that appears when you mouse over it. The mouseover color could be white. The
> professor is right about the contrast. --Teresa

> Maybe bright yellow words? If not that, maybe we could change the background behind that part of the bar?
> Don't know if we want to go there. We could also detach it from that bar in some way, although I'm not sure
> where it would go. --Steve

> I think the yellow color that appears on mouse overs would be more readable. --Jon

There are some issues that govern why we might not follow these suggestions. My reply to these suggestions:

> The mouseover color is one determined by the ACC stylesheet. That is -- the style sheet determines what
> the color is for the mouseover on all the items on the nav bar. If we made the item that color, it would look
> like the mouse is over it all the time. I agree that it is a nice color, but we will have to use something else.
> --mp

I experimented with several colors, trying to balance the look but make the link distinctive while keeping the look of an ACC second tier page. And sent an example to the Cmte.
http://library.austincc.edu/libhome-chatover.htm


With some amusement, I read the following two replies:

> I find this more difficult to see than the current red lettering. - Red

> It's a lot more visible and doesn't clash with the graphic above it. --Teresa