I suspect that most of the people on this list are more interested in
the next generation "front-end" of our library catalogs (public-
facing side such as book search, book holdings display, reviews?)
rather than the next generation "back-end" functions that are used to
manage library holdings and inventory control. Please speak up if
I'm wrong!
Academic libraries have typically serviced both of these functions in
single "ILS" platform, but that is not a technical requirement. One
can imagine one library system that handles inventory, and a
different library system to handle the online public access to the
catalog (oops, I almost said OPAC).
Tito
On Jun 7, 2006, at 9:31 AM, Drew, Bill wrote:
> One of the first things that needs to be done is to define what the
> catalog is currently. I see it as a badly designed front end designed
> for locating physical resources. Some designs work better than
> others.
> It is not designed for the typical user but for an imaginary user
> who is
> supposed to think like a cataloger.
>
> Wilfred (Bill) Drew
> E-mail: mailto:drewwe_at_morrisville.edu
> AOL Instant Messenger:BillDrew4
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety." (Benjamin Franklin)
Received on Wed Jun 07 2006 - 10:08:34 EDT