Public Interfaces Committee
PIC Minutes
March 2, 2005
9:30-11am
Attending: Dale Askey, Katie Bauer, Debbie Falvey, Julie Linden, Stephen Naron
(recorder), Karen Reardon, Earl Roy, Andy Shimp, Kalee Sprague, Tao Yang, Rick
Zwies.
1. Announcements:
Karen and Julie held a library web developers meeting, which was well attended.
Several issues were raised by David Stern who asked whether PIC has discussed
a standardization of web subject guides. Since PIC has not discussed this, we
will consider this at a future meeting. Stern also asked about the use of quick
links by sections of the library, if each unit uses them in its website, and
if so, is there a standardized list of required quick links? Quick links are
discussed below in the section on homepage facelift.
On a related note, Julie mentioned that SQIC members wanted to make sure PIC
was considering how a homepage facelift would affect other departments who use
the library's template or model their pages on the library's homepage (e.g.
MSSA and area studies).
There was a suggestion to develop a glossary of standardized terminology for
certain library services. PIC will take already existing glossaries, expand
them, and add them to our documentation of library website guidelines.
PIC's Survey Monkey survey, which was linked from the News section of the home
page, had a less than stellar response rate. Only 31 individuals participated
in the survey, half of which were staff (the survey did not distinguish between
library staff and other university staff). The question: Why the poor turnout?
Was it overlooked because the whole News section is overlooked, or did people
not respond because they don't care about the topic? By contrast, participation
in last spring's CCL survey (also linked from News) was much higher (over 100
participants). Among the survey results, which are limited to serve decision
making purposes, was a request for stack directory information - something that
PIC has discussed in earlier meetings (oh, and of course, directions to the
Payne Whitney gym).
The above discussion digressed to other survey/usage statistics and data, primarily
the data from the library website's Google powered search this site. Most of
the searches were "subject" searches (e.g. Huckleberry Hound, Hedonism,
etc.) and therefore fruitless, since the search this site is designed to search
the site's html pages. PIC has a great deal of data about these searches, and
will make it a point of discussion on the next meeting agenda. Some changes
suggested are the removal of the Google icon and the deletion of the first paragraph
- which PIC deemed confusing. Bonnie can remove these items from the search
page, but Karen will have to do the coding to make changes to the results page.
Oh, and Andy pointed out the link to Google scholar at the end of the hit results
- what a shameless plug. Katie will investigate to confirm that it can't be
removed, and if not, will make suggestions for how to deal with it.
Karen noted a recent SSH training session attended by 15 people. The class
was well received and should be offered more than once a year. Also, there is
interest in a Front door template class. Julie is willing to teach it, but needs
other volunteers as well. Stephen offered his services.
Kalee announced progress on the Orbis unicode release, which means netid authentication
issues will be coming back on the table for discussion. The release is slated
for July. The next batch of Orbis changes is coming up for discussion in April.
2. Metalib
PIC needs to further discuss the Metalib roll out. For instance, what will
it be named, where will we link to it from the homepage, and what part of Metalib
will we link to? Also, how will we gather feedback on our decisions?
Consensus is on some kind of temporary link (News or Quick links) on the homepage
and a link on the database searching page. Of course the database searching
page will need a facelift. Eventually, perhaps, a Metalib search box on top
of database page could take the place of the current database searching text.
In any case we want Metalib visible, and the database searching page is the
top link clicked from the front door, so essentially it IS the front door.
The Metalib group is not yet sure which section we should link to -- quick
search or multidatabase search. Perhaps usability testing will gauge how people
react to different points of entries, for instance if we offer the same tasks
with different points of entry into Metalib? How can people get from one part
of Metalib to the other?
Some suggestions were floated as to what to name the Metalib interface. Perhaps
the terminology will also be probed in the usability test? Rick warned of the
pitfalls of the word database, which is understood by different people to mean
many different things. Other members discussed the use of abstract names, like
Orbis, for resources, and the limited utility thereof.
We agreed to link to it from the Databases and Article Searching page and not
to call it anything in particular (although we will need some text on the page
to describe it). Eventually, if MetaLib replaces DBOW, we'll continue to use
"Databases and Article Searching" to describe and link to MetaLib.
PIC will make final decisions about which part of MetaLib to link to after usability
testing, slated for mid-March.
3. Frontpage facelift
As an aside, Julie will follow up on deleting the Human Resources link and
add a link for creating bibliographies under "Research tools."
PIC compares Katie and Stephen's facelift design to Cornell's site, i.e. the
right hand column with announcements and exhibitions. Andy agrees PIC should
move the news to the right column, but suggests bumping up point size on the
tree.
Parameters PIC agrees on:
-We won't touch the search box and the tree
-We want to keep the news section
-We want to keep some form of macronavigation, but we need to review the current
one
-Keep text only link
-Keep Ask a librarian, and make it more prominent if possible
-Keep but redesign language links bar
-Keep copyright and last updated info (they are required elements)
Parameters in need of further discussion:
-the possibility of an "In Focus" section. Perhaps it can be used
as a feedback tool and polling station, with brief radio button surveys. PIC
seems to be leaning toward some kind of section, perhaps not called "in
focus", but a place for items that are less fleeting than news.
-A welcome from Alice. A text from the AUL could serve as a default for the
"in focus" section. But it's not even clear whether she wants that
much exposure. Alice may just want a link from the "About the library"
page. In any case, it looks like an AUL welcome box in the right hand column
is out.
-Quicklinks. People aren't using them. And as it is currently configured,
it takes up too much real estate. But what links do we need to retain? Proxy
and Ask a librarian? Or Reference resources and View Library Account/Renew
Books too? And where do we keep the revised quick links? We could incorporate
information on Proxy/VPN in a revised link under "About the Library"
called "computer support" rather than "Computers in the library."
PIC agrees to bring in professional designers, most likely the original designer
to ensure continuity of design. But we must provide adequate specs for the code
this time around, including CSS. Julie will talk to Danuta about funding for
fixing the website's deviated septum. We all agree no major or abrupt change
of style, as a major overhaul of the site would take way too long and is not
necessary at this time.
4. SQIC
Julie described her presentation of PIC's annual report to SQIC. They want
to see us communicate more, and are keen on seeing a usage data forum, i.e.
a presentation of webtrends, Orbis stats, etc. Kalee and Julie briefly discussed
the possibility of a joint PIC/Portal Opportunities Group forum to discuss how
library resources and services can be pushed to external interfaces. SQIC thought
such ideas could be aired in a brainstorming session. Dale felt forum mania
was gripping the library, and expressed concern that forum fatigue would develop.
Karen feels we need to raise consciousness by presenting webtrends and stats
first to prepare for a constructive conversation. Katie, Karen, Kalee and Rick
will work on material for a potential presentation on usage data.
© 2007 Yale University Library
This file last modified 10/18/06
Send comments to libweb@www.library.yale.edu
