 |
 |
Jason, To expand on Becky's answer a bit: we haven't written our own APIs yet, but I did write a Sierra driver for VuFind, so I do have some notes that might be useful to you that I'm happy to share. At least, I've learned the hard way some things that you don't want to do when you're querying the database. ;-) Julia ********************************************* Julia Bauder Social Studies and Data Services Librarian Grinnell College Libraries 1111 Sixth Ave. Grinnell, IA 50112 641-269-4431 On Tue, Oct 15, 2013 at 2:41 PM, Becky Yoose <[log in to unmask]> wrote: > Hi Jason, > > We haven't planned to write our own APIs for Sierra at this point (we're > still working on getting Sierra to work in the first place), but Grinnell > would be interested in seeing how the process goes for you in terms of > local API building. > > As for the Sierra APIs - III just hired a new API project manager (the one > that attended #c4l13 has since left the company) so I'm not sure what's all > going on. They are still saying that patron facing APIs will be out by > winter, though I'd wish the staff facing APIs would get some love too... > > Thanks, > Becky > > ----------------------------------------------------------------- > Becky Yoose > Discovery and Integrated Systems Librarian > Grinnell College > > > On Tue, Oct 15, 2013 at 2:29 PM, Thomale, Jason <[log in to unmask] > >wrote: > > > Hello Code4lib, > > > > I'm wondering if any III Sierra users out there have worked on building > an > > API for accessing their ILS data on top of Sierra's Postgres database. > > Right now I'm looking into possibly building something to serve local > needs > > and use cases, as we're not terribly confident that III's forthcoming > > APIs--if they are indeed forthcoming--will really fit the bill. > > > > If this is something you're doing or have considered doing and wouldn't > > mind comparing notes, please drop me a line! Thanks. > > > > Jason Thomale > > Resource Discovery Systems Librarian > > University of North Texas > > >