{"id":2176,"date":"2007-11-12T13:02:58","date_gmt":"2007-11-12T18:02:58","guid":{"rendered":"http:\/\/blog.librarysupportstaff.org\/?p=429"},"modified":"2007-11-12T13:02:58","modified_gmt":"2007-11-12T18:02:58","slug":"library-software-manifesto","status":"publish","type":"post","link":"https:\/\/www.libology.com\/blog\/2007\/11\/12\/library-software-manifesto.html","title":{"rendered":"Library Software Manifesto"},"content":{"rendered":"<p>The <a href=\"http:\/\/techessence.info\/manifesto\/\">Library Software Manifesto<\/a> was compiled by Roy Tennant (<a href=\"http:\/\/techessence.info\/node\/91\">with input from many others<\/a>) and should be read by everyone who uses an <a href=\"http:\/\/en.wikipedia.org\/wiki\/Integrated_library_system\">Integrated Library System<\/a> (ILS).<\/p>\n<p>Why?\u00a0 Reviewing the manifesto puts one into the mindset of critically reviewing your ILS, detailing its strength and weaknesses from your perspective.<\/p>\n<p>What did I get out of it?<\/p>\n<ul>\n<li>A great deal of of the manifesto deals with open and honest communication &#8211; in both directions.\u00a0 This includes the vendor being straightforward about what their system can and cannot do, as well as the consumer communicating their needs and issues clearly and with the understanding of what can reasonably be done by the vendor in response.<\/li>\n<li>Another large part of the manifesto deals with access.\u00a0 There is no reason why we shouldn&#8217;t be able to connect to our system in various ways in order to better understand our data, or to enhance our offerings.\u00a0 One of the shocks at my current job is how clunky the default reporting tool is in our product, compared to my previous place of work.\u00a0 Setting up this access was complicated, but the end result was powerful and relatively easy to learn.\u00a0 There is no reason why we shouldn&#8217;t have direct, read-only access to our own database.<\/li>\n<li>Thinking about the Evergreen project in relation to this manifesto is illuminating.\u00a0 Open Source is going to transform the ILS landscape, sooner or later, especially when people recognize that the access and communication issues improve dramatically for a healthy open source project.\u00a0 The downside will be some of the documentation issues (often times a problem with open source&#8230; rare are the people who like to write software documentation, and valuable are their contributions), and the need to actively engage the community.\u00a0 Note:\u00a0 I am not specifically discussing Evergreen&#8217;s documentation, which I have only viewed once or twice&#8230; I am referring to open source as a whole.<\/li>\n<li>I like the last point:\u00a0 &#8220;&#8230;lighten up and have fun!&#8221;\u00a0 There is more than enough mind-numbing detail for us to deal with; if we all make an effort to enjoy our work as well as helping others to do so, then we are all better off.<\/li>\n<\/ul>\n<p>So, read the <a href=\"http:\/\/techessence.info\/manifesto\/\">manifesto<\/a>, note the issues that exist with your current system, but also note the issues that exist on your institution&#8217;s side, as well.\u00a0 Think about all of it, and remember it in the future, especially when it is time to consider changing to a new system.\u00a0 This may be the single best tool for you to begin that process.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The Library Software Manifesto was compiled by Roy Tennant (with input from many others) and should be read by everyone who uses an Integrated Library System (ILS). Why?\u00a0 Reviewing the manifesto puts one into the mindset of critically reviewing your &hellip; <a href=\"https:\/\/www.libology.com\/blog\/2007\/11\/12\/library-software-manifesto.html\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[2940,2943,2982,2966],"tags":[3646,3506,3647],"class_list":["post-2176","post","type-post","status-publish","format-standard","hentry","category-ils","category-libraries","category-open-source","category-software","tag-default-reporting-tool","tag-roy-tennant","tag-software-documentation"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pSU5g-z6","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts\/2176","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/comments?post=2176"}],"version-history":[{"count":0,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/posts\/2176\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/media?parent=2176"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/categories?post=2176"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.libology.com\/blog\/wp-json\/wp\/v2\/tags?post=2176"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}