[ale] Linux in libraries (a heads-up for June 2002)

[Douglas Knudsen]

Interesting.  I just moved to Atlanta from the Univeristy of Florida.  The
state uni system had a web based UI to search any of the states university
libraries via a web browser.  Yet, within the library were many terminals
running a text based UI to do queries.  This text based UI reminded me of
LYNX, which is what I meant to say earlier, 'LYNX like'.  Clearly a DB is
involved.  That would be one big ass DB though.  I do not have much
experience with PostGres (SP?), would this handle something of that size?
I'm sure MySQL would not, yet. Hmmm...

DK

-> -----Original Message-----
-> From: owner-ale at ale.org [mailto:owner-ale at ale.org]On Behalf Of Dan
-> Newcombe
-> Sent: Tuesday, July 17, 2001 11:59 PM
-> To: ALE
-> Subject: Re: [ale] Linux in libraries (a heads-up for June 2002)
->
->
-> On Tue, 17 Jul 2001, Wandered Inn wrote:
-> > Douglas Knudsen wrote:
-> > > What software?  IIRC, many libraries use LYNX to do queries
-> for books, etc..
-> > Cherokee County libraries uses Windows with a Netscape browser.
->
-> I was just getting ready to mention something about this.  A lot of the
-> State of Georgia libraries use the PINES system (http://pines.lib.ga.us/)
-> which is a unit of the University System of Georgia.  Their catalog is
-> stored at the central server - not sure where - probably GA State or UGA,
-> and as Geoffrey mentioned, the libraries just use standard PC's with
-> Winders and Netscape or IE on them for the patrons to access it.
->  It is an
-> okay system...however due to the session variables, the back
-> button causes
-> issues.
->
-> I'm not sure what system our library at Clayton State uses, but
-> it is some
-> commercial software running one Windows (for checkout/checkin) and seems
-> to be very functional.
->
-> In the simplest terms, it's just a big ole database of customers
-> and books
-> with a front-end for patrons to look things up, and a front-end for the
-> librarians to check things out, and manage the inventory/user databases.
->
-> If using a standard database that supports ODBC or some other
-> semi-standard network connection, it wouldn't really matter what
-> the front
-> end was written in/for - as long as it was simple for both the librarians
-> and the patrons to use.  Of course a web interface is even
-> better, because
-> I can now see if a book is in from home/work and decide if I should stop
-> by or not.
->
-> 	-Dan
->
->
->
->
-> --
-> To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in
-> message body.
->

--
To unsubscribe: mail majordomo at ale.org with "unsubscribe ale" in message body.