<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>LibLime Developers' Blog - Latest Comments in Deciding on an API for Biblios</title><link>http://liblimedevelopers.disqus.com/</link><description>The LibLime Developers’ Blog is a place for LibLime’s programmers and analysts to briefly tear themselves away from specs and code and talk about free and open-source library software including Koha.</description><language>en</language><lastBuildDate>Wed, 04 Jun 2008 08:31:09 -0000</lastBuildDate><item><title>Re: Deciding on an API for Biblios</title><link>http://blogs.liblime.com/developers/2008/05/24/deciding-on-an-api-for-biblios/#comment-1567078</link><description>Fernando,&lt;br&gt;&lt;br&gt;I had not seen your project before: it is very interesting and exciting.  It looks as if we have adopted some of the same techniques (not to mention, javascript framework).&lt;br&gt;&lt;br&gt;I will read over your project's documentation - indeed it seems as if we could collaborate and settle on some best practices as well!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Catalfo</dc:creator><pubDate>Wed, 04 Jun 2008 08:31:09 -0000</pubDate></item><item><title>Re: Deciding on an API for Biblios</title><link>http://blogs.liblime.com/developers/2008/05/24/deciding-on-an-api-for-biblios/#comment-1567077</link><description>Frederic,&lt;br&gt;&lt;br&gt;Thank you for your comment; I think these are good suggestions.  &lt;br&gt;&lt;br&gt;In fact I think Biblios should allow callbacks at all important events in the record life cycle: on retrieval from z3950 server, on record editing, on record saving (or "send"ing to a remote ils).  This way plugins will have the opportunity to modify things as needed.&lt;br&gt;&lt;br&gt;This also goes hand in hand with the concept of editor plugins, whereby someone could write an editor for another kind of metadata record, like MODS.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Catalfo</dc:creator><pubDate>Wed, 04 Jun 2008 08:21:35 -0000</pubDate></item><item><title>Re: Deciding on an API for Biblios</title><link>http://blogs.liblime.com/developers/2008/05/24/deciding-on-an-api-for-biblios/#comment-1567076</link><description>Hi Chris,&lt;br&gt;&lt;br&gt;I'm happy that you keep working on Biblios and sharing some of your developer thoughts.&lt;br&gt;&lt;br&gt;My work on a similar project during the last years makes me naturally interested in what you are doing now. I'm wondering if perhaps we could collaborate somehow...</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fernando</dc:creator><pubDate>Thu, 29 May 2008 19:49:58 -0000</pubDate></item><item><title>Re: Deciding on an API for Biblios</title><link>http://blogs.liblime.com/developers/2008/05/24/deciding-on-an-api-for-biblios/#comment-1567075</link><description>I haven't seen yet 'biblio' but I suppose there is a way to target Z39.50 hosts in order to download records. I would be nice to manage Z39.50 list from API. It would be nice also to be able to register a callback function to be called after biblio record has been retrieved from z3950 server and before being displayed in 'biblio'. This function (one by z3950 target) would be able to clean record, do whatever on it, create items, deduplicate, etc.&lt;br&gt;&lt;br&gt;Thanks and continue the good work.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Frédéric</dc:creator><pubDate>Sun, 25 May 2008 01:55:41 -0000</pubDate></item></channel></rss>