 |
 |
On Wed, Mar 14, 2012 at 9:37 AM, Owen, Will <[log in to unmask]> wrote: > Endeca provides a public interface to library holdings: it is not > and could not be an ILS, performing functions like circulation, accounting > control, etc. In this respect it's more akin to Blacklight that to an ILS. One could build the catalog part of an ILS around Endeca or one of the solrmarc based discovery engines, though they don't maintain real-time circulation data etc internaly, so the existence of an external circulation system is required. An idea of some of the functionality that is needed from outside can be gotten from the vufind ILS driver spec<http://vufind.org/wiki/building_an_ils_driver> ; one might argue that different parts of the functionality could come from different systems, which makes the driver the integrator. A lot of functionality bundled up in the monolithic "ILS" could be delegated if there was some Protocol for Interchanging Circulation information that was standard enough to interoperate with. If it weren't for UNC's ERP project, I would probably still thing that accounting controls, purchase management, ought to be handled outside the ILS. Simon