This is great news! Thanks to PV Supa for sponsoring the work. I would
like to ask that you use the Library Communication Framework (aka BLCF or
LCF) to guide your development. The LCF has been developed by a British
entity (Book Industry Communication). The draft document is available
here:
Hi Evergreen Community,
Are there any plans for a completely web-based Evergreen? Meaning no download
of the staff client and all is on the web?
Thanks!
Jennifer Bielewski
LTS Representative
LYRASIS
jennifer.bielew...@lyrasis.orgmailto:jennifer.bielew...@lyrasis.org
404.892.0943 x3848
Viannin
I don't believe so. In fact, I am personally for moving *away* from
some of the browser compatible interfaces we do have (most of which
are for configuration purposes only anyway).
Thomas Berezansky
Merrimack Valley Library Consortium
Quoting Jennifer Bielewski
I have just returned from the UK where I met with BIC and CILIP (Chartered
Institute of Library and Information Professionals) representatives as well
as RFID vendors.
BIC has commissioned of a new set of library interoperability standards,
which define a framework for the communication of data
On Mon, Nov 19, 2012 at 10:13:01AM -0800, Lori Bowen Ayre wrote:
I have just returned from the UK where I met with BIC and CILIP (Chartered
Institute of Library and Information Professionals) representatives as well
as RFID vendors.
BIC has commissioned of a new set of library
TADL has interest in more staff functions being made available via
web-based interfaces, and will likely be experimenting in that area at some
point over the next 6 months. Such work would be taking place in public
working repos, with communication and discussion likely taking place in IRC
and on
I've been poking at building one Sap I called it. Would be interested in
working with others.
On 19 Nov 2012 10:53, Jeff Godin jgo...@tadl.org wrote:
TADL has interest in more staff functions being made available via
web-based interfaces, and will likely be experimenting in that area at some
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
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
