{"id":342,"date":"2009-08-06T10:24:22","date_gmt":"2009-08-06T15:24:22","guid":{"rendered":"http:\/\/dilettantes.code4lib.org\/?p=342"},"modified":"2009-08-06T10:24:22","modified_gmt":"2009-08-06T15:24:22","slug":"where-is-the-outrage","status":"publish","type":"post","link":"https:\/\/rossfsinger.me\/blog\/2009\/08\/where-is-the-outrage\/","title":{"rendered":"Where is the outrage?"},"content":{"rendered":"<p>For a couple of months this year, <a href=\"http:\/\/wiki.code4lib.org\/index.php\/OCLC_Policy_Change\" target=\"_blank\">the library world was aflame with rage at the proposed OCLC licensing policy regarding bibliographic records<\/a>.\u00c2\u00a0 It was a justifiable complaint, although I basically  stayed out of it:\u00c2\u00a0 it just didn&#8217;t affect me very much.\u00c2\u00a0 After much gnashing of teeth, petitions, open letters from consortia, etc. <a href=\"http:\/\/www.oclc.org\/news\/releases\/200939.htm\" target=\"_blank\">OCLC eventually rescinded their proposa<\/a>l.<\/p>\n<p>Righteous indignation: 1, &#8220;the man&#8221;: 0.<\/p>\n<p>While this could certainly counted as a success (I think, although this means we default to the much more ambiguous 1987 guidelines), there is a bit of a mixed message here about where the library community&#8217;s priorities lie.\u00c2\u00a0 It&#8217;s great that you now have the right to share your data, but, really, how do you expect to do it?<\/p>\n<p>It has been a little over a year since the <a href=\"http:\/\/jangle.org\/spec\/1.0\" target=\"_blank\">Jangle 1.0 specification<\/a> has been released; 15 months or so since all of the major library vendors (with one exception) <a href=\"http:\/\/blogs.lib.berkeley.edu\/shimenawa.php\/2008\/04\/04\/ils_basic_discovery\" target=\"_blank\">agreed to the Digital Library Federation&#8217;s &#8220;Berkeley Accord&#8221;<\/a>; and we&#8217;re at the anniversary of the workshop where the vendors actually agreed on <a href=\"http:\/\/www.diglib.org\/architectures\/ilsdi\/DLF_ILS_Discovery_1.1.pdf\" target=\"_blank\">how we would implement a &#8220;level 1&#8221; DLF API<\/a>.<\/p>\n<p>So far, not a single vendor at the table has honored their commitment, and I have seen no intention to do so <a href=\"http:\/\/www.biblibre.com\/node\/122\" target=\"_blank\">with the exception of Koha<\/a> (although, interestingly, not by the company represented in the Accord).<\/p>\n<p>I am going to focus here on the DLF ILS-DI API, rather than Jangle, because it is something we all agreed to.\u00c2\u00a0 For all intents and purposes, Jangle and the ILS-DI are interchangeable:\u00c2\u00a0 I think anybody that has invested any energy in either project would be thrilled if either one actually caught on and was implemented in a major ILMS.\u00c2\u00a0 Both specifications share the same scope and purpose.\u00c2\u00a0 The resources required to support one would be the same as the other, the only difference between the two are the client-side interfaces.\u00c2\u00a0 Jangle technically meets all of the recommendations of the ILS-DI, but not to the bindings that we, the vendors, agreed to (although there is an &#8216;adapter&#8217; to bridge that gap).\u00c2\u00a0 Despite having spent the last two years of my life working on Jangle, I would be thrilled to no end if the ILS-DI saw broad uptake.\u00c2\u00a0 I couldn&#8217;t care less about the serialization; I only care about the access.<\/p>\n<p>There is only one reason that the vendors are not honoring their commitment:\u00c2\u00a0 libraries aren&#8217;t demanding that they do.<\/p>\n<p>Why is this?\u00c2\u00a0 Why the rally to ensure that our bibliographic data is free for us to share when we lack the technology to actually do the sharing?<\/p>\n<p>When you look at the open source OPAC replacements (I&#8217;m only going to refer to the OSS ones here, because they are transparent, as opposed to their commercial counterparts):\u00c2\u00a0 VuFind, Blacklight, Scriblio, etc. and take stock of hoops that have to be jumped through to populate their indexes and check availability, most libraries would throw their hands in the air and walk away.\u00c2\u00a0 There are batch dumps of MARC records.\u00c2\u00a0 Rsync jobs to get the data to the OPAC server.\u00c2\u00a0 Cron jobs to get the MARC into the discovery system.\u00c2\u00a0 Screen scrapers and one off &#8220;drivers&#8221; to parse holdings and status.\u00c2\u00a0 It is a complete mess.<\/p>\n<p>It&#8217;s also the case for every Primo, Encore, Worldcat Local, AquaBrowser, etc. that isn&#8217;t sold to an internal customer.<\/p>\n<p>If you&#8217;ve ever wondered why the third party integration and enrichment services are ultimately somewhat unsatisfying (think BookSite.com or how LibraryThing for Libraries is really only useful <em>when you can actually find something<\/em>), this is it.\u00c2\u00a0 The vendors have made it nearly impossible for a viable ecosystem to exist because there is no good way to access the library&#8217;s own data.<\/p>\n<p>And it has got to stop.<\/p>\n<p>For the OCLC withdrawal to mean anything, libraries have either got to put pressure on their vendors to support one of the two open APIs, migrate to a vendor that does support the open APIs, or circumvent the vendors entirely by implementing the specifications themselves (and sharing with their peers).\u00c2\u00a0 This cartel of closed access is stifling innovation and, ultimately, hurting the library users.<\/p>\n<p><a href=\"http:\/\/code.google.com\/p\/talislms-jangle\/\" target=\"_blank\">I&#8217;ll hold up my end<\/a> (and ensure it&#8217;s ILS-DI compatible via <a href=\"http:\/\/code.google.com\/p\/jangle\/source\/browse\/#svn\/trunk\/external_interfaces\/dlf-api\">this<\/a>) and work towards it being officially supported <a href=\"http:\/\/www.talis.com\/integration\/\" target=\"_blank\">here<\/a>, but the 110 or so Alto customers aren&#8217;t exactly going to make or break this.<\/p>\n<p>Hold your vendor&#8217;s feet to the fire and insist they uphold their commitment.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>For a couple of months this year, the library world was aflame with rage at the proposed OCLC licensing policy regarding bibliographic records.\u00c2\u00a0 It was a justifiable complaint, although I basically stayed out of it:\u00c2\u00a0 it just didn&#8217;t affect me very much.\u00c2\u00a0 After much gnashing of teeth, petitions, open letters from consortia, etc. OCLC eventually [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[69,47,7,14,70,63],"tags":[],"class_list":["post-342","post","type-post","status-publish","format-standard","hentry","category-ils-di","category-jangle","category-libraries","category-oai","category-rant","category-standards-schmandards"],"_links":{"self":[{"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/posts\/342","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/comments?post=342"}],"version-history":[{"count":1,"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/posts\/342\/revisions"}],"predecessor-version":[{"id":343,"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/posts\/342\/revisions\/343"}],"wp:attachment":[{"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/media?parent=342"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/categories?post=342"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rossfsinger.me\/blog\/wp-json\/wp\/v2\/tags?post=342"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}