DISQUS

DISQUS Hello! LibLime Developers' Blog is using DISQUS, a powerful comment system, to manage its comments. Learn more.

Community Page

  • Subscribe

  • Community

  • Top Commenters

  • Popular Threads

  • Recent Comments

    • Sounds like fun. Have you been to a BarCamp before?

      11 months ago by Owen

      in BarCampOhio aka LibraryCampOhio

    • ...and who are the guys and gals who get blamed from nearly everything from the Internet being down to the coffee maker not working to someone stealing the Any Key. :-) If it doesn't work we...

      11 months ago by Mike Jackiw

      in Hug a sysadmin at your library

    • Regarding your suggestion of having publishers provide metadata in machine-readable form, here is what I wrote in 1999: "Finally, not to forget cataloguers, whose meticulous task is essential...

      1 year ago by Miklos

      in Frankenstein, or the modern FRBR

    • Fernando, 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). I will read...

      1 year ago by Chris Catalfo

      in Deciding on an API for Biblios

    • Frederic, Thank you for your comment; I think these are good suggestions. In fact I think Biblios should allow callbacks at all important events in the record life cycle: on retrieval from z3950...

      1 year ago by Chris Catalfo

      in Deciding on an API for Biblios

LibLime Developers' Blog

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.
Jump to original thread »
Author

Deciding on an API for Biblios

Started by nengard · 10 months ago

As I continue to work on Biblios in anticipation of its release (soon, I hope!), it is about time to decide on an API.
I have already put into place a simple macro system for batch editing of bibliographic records. The language is Javascript and makes use of a MarcRecord javascript obje ... Continue reading »

4 comments

  • Frédéric

    1 year ago

    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.

    Thanks and continue the good work.
    reply
  • Fernando

    1 year ago

    Hi Chris,

    I'm happy that you keep working on Biblios and sharing some of your developer thoughts.

    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...
    reply
  • Chris Catalfo

    1 year ago

    Frederic,

    Thank you for your comment; I think these are good suggestions.

    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.

    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.
    reply
  • Chris Catalfo

    1 year ago

    Fernando,

    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).

    I will read over your project's documentation - indeed it seems as if we could collaborate and settle on some best practices as well!
    reply

Add New Comment

Returning? Login