 |
 |
> > Since we can't SQL-query our own ILS data directly... > > I don't know why we tolerate such limitations in our > contractual agreements. For Voyager ILS libraries the "can't SQL-query" is strictly a local limitation imposed by local IT fiat. Many, if not most of us, SQL-query to our hearts content, whether it's server-side via SQL*Plus, Perl/DBI/DBD::Oracle, or PC-based via the Oracle ODBC. In fact that's one of the things I really like about the Voyager system -- the architecture is pretty wide open and we can get at the data any way we want. Besides getting things like custom reports, many of us have leveraged that direct data access to produce a number of add on utilities, apps, and web services that do neat things. What we can *not* do is the Oracle DBA stuff -- we can't use any Oracle APIs to run Data Manipulation Language (DML) statements to directly update the database, nor can we create new Oracle tables, Oracle users, etc. -- Michael # Michael Doran, Systems Librarian # University of Texas at Arlington # 817-272-5326 office # 817-688-1926 mobile # [log in to unmask] # http://rocky.uta.edu/doran/ > -----Original Message----- > From: Code for Libraries [mailto:[log in to unmask]] On > Behalf Of Eric Lease Morgan > Sent: Friday, January 19, 2007 6:02 AM > To: [log in to unmask] > Subject: Re: [CODE4LIB] Getting data from Voyager into XML? > > On Jan 19, 2007, at 6:37 AM, Birkin James Diana wrote: > > > Since we can't SQL-query our own ILS data directly... (ok, blood > > pressure is fine again) this solved a lot of issues. > > > I don't know why we tolerate such limitations in our > contractual agreements. Maybe we should charge a fee or > demand a reduction in fees for living with this. It's like > this, "No, you are not allowed to look under the hood of your > car or take apart your radio." Weird. > > -- > Earache >