While I think that some common UI widgets would be useful, what the
OPAC looks like, how it works and what tools are available will likely
depend on the library mission/audience. I would expect a different
interface for a public library versus a research oriented university
library. Subject specific libraries may also have a more complicated,
jargon rich interface that makes sense for their patrons. I would
expect a public library to be more "amazon-ish" then a
research-oriented library.
That's not to say they are completely different. There are overlaps in
all of the audiences. But the tools you provide to the users will
likely depend on who you're trying to serve. Making things overly
generic runs the chance of serving no one well.
Ryan Eby
On 6/15/06, Jacobs, Jane W <Jane.W.Jacobs_at_queenslibrary.org> wrote:
> **Views expressed by the author do not necessarily represent those of the Queens Library.**
>
> However, it is worth noting that the Card catalog did have consistent "look and feel" from library to library. It provided customers with a familiar looking interface, a certain level of comfort and the illusion that they knew what they were doing when they searched it.
>
> It might be worth considering whether instead of outdoing ourselves innovatively redesigning and branding our OPACs, individually, whether we ought not to look for some common design elements that could make life easier for customers and bibliographic instruction easier for librarians.
>
Received on Thu Jun 15 2006 - 11:40:35 EDT