I've written a decent amount of code against Sierra, but I don't know if
any of it amounts to an "API".
* I've built some utility code that has grown into a handful Perl modules
that I use regularly in creating new reports. Most of these are
special-purpose for applications we have in-house but I'm trying to find
ways to generalize them. Examples: wrapper functions around the Patron
Update Web Service, functions to look-up shelf location names, find/clean
up patron data entry errors, etc
* I've also started creating little web services with mod_perl for use in a
web-application I'm working on. Examples: a script that spits back item
information in JSON when given an item barcode, a script that spits back a
JSON list of all attached items when given a bib record number. Again
these are mostly special purpose, but I have a notion to find ways to
I'm aware of two github repo's that might be of interest in this
Sadly, I'm a team of one here and I'm a bit shy about the state my code is
currently in, so I haven't published it anywhere. ( Also the way I use git
locally is probably "wrong", not to mention there are probably passwords in
old commits. )
Nonetheless, I'd definitely be interested in collaborating on anything that
might benefit all Sierra users.
Feel free to contact me off-list if you want to chat more.
On Tue, Oct 15, 2013 at 5:36 PM, Julia Bauder <[log in to unmask]>wrote:
> 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 Bauder
> Social Studies and Data Services Librarian
> Grinnell College Libraries
> 1111 Sixth Ave.
> Grinnell, IA 50112
> 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
> > that attended #c4l13 has since left the company) so I'm not sure what's
> > 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
> > >