Hi Deborah, > We have an existing application that would be more efficient if > it could get that data, but which only uses ODBC. Did the "existing application" connect to your former integrated library system? If it did so via ODBC, then it was accessing tables and fields in the ILS's underlying relational database. Even if your Alma instance allowed for a database listener-ODBC connection, the underlying database structure would differ from your previous ILS, so you would essentially have to refactor the application. > It’s on The Cloud so we’re not going to be getting direct > access to the database anytime soon. <cough> ever <cough> > Does anyone know if there’s any middleware out there that could make > these two things talk to each other The ODBC client facilitates communication (via SQL) to and from a relational database listener. If your existing application utilizes ODBC, there's no easy way to communicate with a RESTful API instead. At least not in the way that you are thinking (i.e. you wouldn't be avoiding the substantial rewriting of the original existing application). > ... or do we give this up as a “Would have been nice, but <shrug>”? Yes, that. Or determine the input data requirements of the existing application and then start digging through the Alma RESTful API documentation and see if they can be gotten that way. And start recoding the application. -- 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 > Fitchett, Deborah > Sent: Monday, September 22, 2014 5:01 PM > To: [log in to unmask] > Subject: [CODE4LIB] REST vs ODBC > > Morning, all, > > We have a small dilemma: > > > 1. Our brand new Alma system provides access to a bunch of data via > RESTful API. It’s on The Cloud so we’re not going to be getting direct > access to the database anytime soon. > > > 2. We have an existing application that would be more efficient if > it could get that data, but which only uses ODBC. (I’m told other > available drivers are: > - Microsoft Jet 4.0 OLE > - Microsoft Office > - Microsoft OLE DB Provider > - Microsoft Datashape > - OLE DB Provider > - SQL Server Native Client 10.0) > > Does anyone know if there’s any middleware out there that could make > these two things talk to each other, or do we give this up as a “Would > have been nice, but <shrug>”? > > Nâku noa, nâ > > Deborah Fitchett > Senior Advisor, Digital Access > Library, Teaching and Learning > > p +64 3 423 0358 > e [log in to unmask]<mailto:[log in to unmask]> | > w library.lincoln.ac.nz<http://library.lincoln.ac.nz/> > > Lincoln University, Te Whare Wânaka o Aoraki > New Zealand's specialist land-based university > > > ________________________________ > P Please consider the environment before you print this email. > "The contents of this e-mail (including any attachments) may be > confidential and/or subject to copyright. Any unauthorised use, > distribution, or copying of the contents is expressly prohibited. If you > have received this e-mail in error, please advise the sender by return e- > mail or telephone and then delete this e-mail together with all > attachments from your system."