[OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Evergreen API

Mike Rylander mrylander at gmail.com
Sat May 12 21:37:56 EDT 2012


On Fri, May 11, 2012 at 10:25 PM, Dan Scott <dan at coffeecode.net> wrote:
> On Fri, May 11, 2012 at 07:18:09PM -0700, Lori Bowen Ayre wrote:
>> Hi Devs and Community,
>>
>> Has there ever been serious consideration given to developing an Evergreen
>> API?  And if not, why not?
>>
>> I'm just wondering if that might be something that we could make happen as
>> a community, perhaps with funds we raise through some clever activity or by
>> selling some groovy merchandise.  We've been talking about doing something
>> like that on the Oversight Board although no particular project has been
>> suggested.
>>
>> But, I may suggest developing an Evergreen API unless there's some reason
>> not do.  Please advise!
>
> Maybe you need to define what you mean by API. If you mean "a set of
> methods that you can call to return data or produce results", then I
> think Evergreen has had that since day one. It would be really hard for
> us to develop Evergreen without an API. A Google search for "Evergreen
> API" returns this as hit #2 for me: http://evergreen-ils.org/blog/?p=46

And here's a recent-ish system with the above-described docgen.xsl in
place, showing the acquisitions API:
http://commidore64.esilibrary.com/opac/extras/docgen.xsl?service=open-ils.acq&all=on&offset=0&limit=25

-- 
Mike Rylander
 | Director of Research and Development
 | Equinox Software, Inc. / Your Library's Guide to Open Source
 | phone:  1-877-OPEN-ILS (673-6457)
 | email:  miker at esilibrary.com
 | web:  http://www.esilibrary.com


More information about the Open-ils-dev mailing list