- From: Karen Coyle <kcoyle@kcoyle.net>
- Date: Thu, 10 Nov 2011 07:42:13 -0800
- To: public-lld@w3.org
This makes sense to me. I was thinking along the lines of "dog food" - if LD is good for linking globally, it should also be good for linking locally. And if our bibliographic data ends up in a triple store, it is possible that library management data will also be in such a data store since there are always points where the bib data and management data need to interact. kc Quoting Jakob Voss <Jakob.Voss@gbv.de>: >>> Has anyone started to express patron data in RDF? > >> What's the use-case? e.g. internal structure of an RDF-backed library >> system maybe? >> >> I was looking around recently to see if I could find any bulk >> (aggregate, 'anonymised', etc) loans data, but it seems a pretty taboo >> topic due to the privacy concerns. Since RDF is largely about sharing >> data, I'm curious if you have a particular use in mind. > > RDF is not only about sharing but also about information integration. > I found the support of NCIP in integrated library systems somehow > disappointing and report of the Digital Library Federation more like > a lip service. The chance of someone writing a Linked Data seems > more likely than someone writing an NCIP wrapper, as RDF is much > more common than library-specific formats. In addition, mapping > one part of your library system to RDF helps you to map the rest. > >> Re loans data and their un-shareability, if that info could be kept >> long enough *within* a library to compute similarities and generate >> recommendations, sharing the results of such processing would be >> interesting. However I have the impression that many (all? most?) >> libraries try to keep such data for as short a time as possible... > > I had only aggregation on a smaller scale in mind: a user (or a user's > client) would aggregate patron data from different libraries, for > instance > to show a combined list of his loans. For this reason I was looking for > a simple ontology to express the most relevant library patron data in > RDF. I guess that user account information can be expressed with SIOC > and FOAF, but some specific properties such as > > - due-date > - number-of-renewals > - sum-of-dues > ... > > would be needed. I hesitate to create yet another library-specific > ontology (in addition to DAIA/RDF) and I wonder why no integrated > library system has started to use RDF. Maybe hacking it into Koha > is a good strategy, as I do not expect any commercial vendor to do so. > > Jakob > > > -- > Verbundzentrale des GBV (VZG) > Digitale Bibliothek - Jakob Voß > Platz der Goettinger Sieben 1 > 37073 Goettingen - Germany > +49 (0)551 39-10242 > http://www.gbv.de > jakob.voss@gbv.de > -- Karen Coyle kcoyle@kcoyle.net http://kcoyle.net ph: 1-510-540-7596 m: 1-510-435-8234 skype: kcoylenet
Received on Thursday, 10 November 2011 15:42:46 UTC