{"id":197,"date":"2009-01-14T16:07:00","date_gmt":"2009-01-14T03:07:00","guid":{"rendered":"http:\/\/deborahfitchett.com\/blog\/?p=197"},"modified":"2009-01-14T16:07:00","modified_gmt":"2009-01-14T03:07:00","slug":"libraries-and-sharing","status":"publish","type":"post","link":"https:\/\/deborahfitchett.com\/blog\/2009\/01\/libraries-and-sharing\/","title":{"rendered":"Libraries and sharing"},"content":{"rendered":"<p>In December last year Dale Askey wrote a Code4Lib column, <a href=\"http:\/\/journal.code4lib.org\/articles\/527\">We Love Open Source Software. No, You Can\u2019t Have Our Code<\/a> which raised some discussion for a while.<\/p>\n<p>But of course it&#8217;s not just software.<\/p>\n<p>Oh, I haven&#8217;t personally experienced libraries refusing to share information.  In fact when I was researching <a href=\"http:\/\/deborahfitchett.com\/lib_onlocation.php\">our &#8220;Library on Location&#8221; project<\/a>, everyone I contacted was more than happy to give me stories, photos, even survey data.  But&#8230; I did have to track them down from oblique references in old blogs and newsletters and email them, one by one.<\/p>\n<p>And we put our own Library on Location reports online, which I&#8217;m glad we could do.  But&#8230; we had to ask if we could do it, and only our conference paper is in any kind of official repository sort of space.<\/p>\n<p>Is this consistent with our profession&#8217;s attempts to convince academics to put their research papers and data into institutional repositories?<\/p>\n<p>And is it an efficient, librarian-like way of organising the accumulated knowledge within the profession?<\/p>\n<p>Statistics.<br \/>User surveys.<br \/>Projects that work.<br \/>Projects that don&#8217;t work.<br \/>Projects that might work but we ran out of funding.<br \/>Projects that would work if we could share the workload with another institution.<\/p>\n<p>This might have been why the <a href=\"http:\/\/www.libsuccess.org\/\">Library Success wiki<\/a> was created.  It&#8217;s a great idea, but its contributors are individuals, not libraries, so it just doesn&#8217;t have the kind of oomph I&#8217;m thinking about.<\/p>\n<p><b>What if&#8230;<\/b><\/p>\n<p>What if every library in the world brought their <a href=\"http:\/\/www.daveyp.com\/blog\/archives\/528\">anonymised circulation data<\/a>, their <a href=\"http:\/\/www.teachinglibrarian.org\/weblog\/2009\/01\/chat-service-at-baruch-college-shows.html\">IM reference<\/a> <a href=\"http:\/\/www.teachinglibrarian.org\/weblog\/2009\/01\/most-popular-times-of-day-for-chat.html\">statistics<\/a>, their anonymised usability testing and survey results, their project reports, their lesson plans and handouts, and their <a href=\"http:\/\/www.walkingpaper.org\/1100\">iPhone applications<\/a> out from their hard drives and their intranets and made them publically accessible?<\/p>\n<p>What if they all licensed this stuff (and photos and podcasts and vidcasts and&#8230;) with a Creative Commons or GPL license?<\/p>\n<p>What if they all created a single website where this stuff could be stored and searched in one place?<\/p>\n<p>What if that website allowed space for libraries and librarians to comment and collaborate on and add to each other&#8217;s work?<\/p>\n<p><b>No, seriously, I mean it<\/b><\/p>\n<p>At the end of the month my library&#8217;s delegates to LIANZA2008 are going to report back to the rest of the staff about what we got out of the conference.  I got 4 things out of conference, 3 of which were:<\/p>\n<ol>\n<li>Leadership &#8211; future taking vs future making<\/li>\n<li>Innovation &#8211; just do it<\/li>\n<li>Why are <i>they<\/i> presenting on this topic when <i>we&#8217;ve<\/i> gone further in our analogous project and have more experience of how it works in practice?  Oh yes:  <i>because it never occurred to us to share<\/i>.<\/li>\n<\/ol>\n<p>So in my allotted 5 minutes of the reporting back, I plan to pitch the idea that we should move all our (sanitised if need be) project work from the intranet to open webspace.<\/p>\n<p>What about the rest of the world?<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In December last year Dale Askey wrote a Code4Lib column, We Love Open Source Software. No, You Can\u2019t Have Our Code which raised some discussion for a while. But of course it&#8217;s not just software. Oh, I haven&#8217;t personally experienced libraries refusing to share information. In fact when I was researching our &#8220;Library on Location&#8221; [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[],"tags":[194,195,131,16,4,94,22],"_links":{"self":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts\/197"}],"collection":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/comments?post=197"}],"version-history":[{"count":0,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/posts\/197\/revisions"}],"wp:attachment":[{"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/media?parent=197"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/categories?post=197"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/deborahfitchett.com\/blog\/wp-json\/wp\/v2\/tags?post=197"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}