» Home › Forums › Project Discussion › Locum ›

Locum and VuFind Connectors

» Submitted by stompro on Thu, 09/25/2008 - 4:29pm

I'm curious if there would be any interest in combining work with the VuFind project, which also has a ILS connection layer with drivers for various ILS products? It might not be feasible since the projects probably don't have similar designs, but it is something to think about. They currently have a Voyager connector that might help someone who is developing a voyager connector for Locum.

http://www.vufind.org/wiki/building_an_ils_driver
http://vufind.org/roadmap.php

‹ Support for III scope-like functionality? III Connector Fines Bug ›
Submitted by jblyberg on Thu, 09/25/2008 - 11:28pm.

It's an interesting thought, and one that definitely bears some looking at. The primary difference between VuFind and Locum (and by extension, SOPAC) is that Locum serves as a secondary abstraction layer. In other words, the stack looks like:

  1. ILS
  2. Locum Connector (ILS-specific abstraction layer)
  3. Locum (Normalized abstraction layer)
  4. SOPAC

Instead of this:

  1. ILS
  2. ILS Connector (ILS-specific abstraction layer)
  3. OPAC

The benefit to the Locum model is that it makes it possible to develop a myriad of different applications on top of it--it's not made specifically for SOPAC.