Hi Savitra -- Please detail which kind of FRBR you intend to pursue: weak (i.e. related works), something stronger or "complete". From what I understand, the level of detail needed for total FRBR would challange the representational capacity of *any* ILS in existence. There was a lot of talk about FRBR at the recent code4lib convention. The last diagram I saw had four levels to a "strong" implementation: Work, Expression, Manifestation and Item. And then it got crazy for what "complete" would look like. The (large) PDF from this year's talk on this issue, "What we talk about when we talk about FRBR" is here: <goog_1236968080767>www.code4lib.org/files/frbr_code4lib09.pdf It seems like we would do best to implement additional related works connectors for external data like LibraryThing, and especially FreeBase. The PDF from the Freebase presentation is here: www.*code4lib*.org/files/*freebase*.pdf<http://www.code4lib.org/files/freebase.pdf> I'll leave the ornate highly-differentiated data modeling to academics (or external sources) for now. --Joe 2009/3/16 savitra sirohi <savitra.sirohi@osslabs.biz>
Folks,
We might be interested in developing better FRBR capabilities on Koha. This will help us market Koha better here in India. I see some posts on this topic from a while back, nothing recent.
http://listes.koha-fr.org/pipermail/koha-devel/2005-October/005536.html
http://library-matters.blogspot.com/2008/12/ranganathans-5-laws-and-frbr.htm...
I am aware that Koha can use webservices like xISBN.
Is anybody working on FRBR?
I will appreciate input from users and developers on how to move forward on this.
Thanks, Savitra Sirohi MD, Nucsoft OSS Labs http://www.osslabs.biz