[OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Library Communications Framework

[Lori Bowen Ayre]

Dan,

Thanks for the clarification. But, isn't suggesting BIC develop modules for
Evergreen like asking NISO to write the SIP3 interface for Evergreen?
 Maybe that is how something like this is done but I do know that there has
already been one implementation of the LCF (the work was done by
Bibliotheca and Axiell I believe) so perhaps that pilot project is what you
mean by an implementation platform?

Anyway, the point is that BIC isn't in a position to do the development
work.  The work will need to be done by our Evergreen developers or
developers we libraries hire to do it in cooperation with Evergreen
developers.

My feeling is that if there is going to be any new development work done on
Evergreen that is related to RFID functionality, we should be looking at
what has already been done elsewhere and doing our best to support other
international efforts to standardize these communications.  From what I can
see, BIC's LCF is the only game in town that is specifically designed for
RFID....specifically ISO 28560-2 systems like ours.

It's great that PV Supa is supporting this development.  I'd just like to
be sure that they are supporting code that will work for RFID vendors
besides PV Supa.  That means code written that follows the LCF (unless you
know of something better) without requiring the next RFID vendor to tweak
their software to accommodate the unique (dare I say proprietary?) approach
that PV Supa may choose to take.

Lori



On Mon, Nov 19, 2012 at 2:25 PM, Dan Scott <dan at coffeecode.net> wrote:

> On Mon, Nov 19, 2012 at 02:12:29PM -0800, Lori Bowen Ayre wrote:
> > I think instead of inviting BIC to use Evergreen, it would be more
> fruitful
> > for we, US Libraries, build on the work they've done to look beyond those
> > many protocols (from among the "yet another" you mention) that a) are
> > implemented completely differently across systems) and b) are limited in
> > the functionality they support and c) are built around one-at-a-time
> > barcode technology.
>
> I think that you completely misunderstood what I meant, which was the
> BIC / CILIP could use Evergreen as a reference implementation for their
> LFC work. As in, they could go ahead and develop modules that add the
> LFC standard protocols to Evergreen, thereby making at least one ILS
> capable of speaking to equipment that would also implement the LFC
> standard protocols.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20121119/ce9b1135/attachment.htm>