<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>librarian.net &#187; simplesystems</title>
	<atom:link href="http://www.librarian.net/tag/simplesystems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.librarian.net</link>
	<description>putting the rarin back in librarian since 1999</description>
	<lastBuildDate>Fri, 10 Feb 2012 04:37:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>asking the right questions, when to be simple, when to be complex</title>
		<link>http://www.librarian.net/stax/1790/asking-the-right-questions-when-to-be-simple-when-to-be-complex/</link>
		<comments>http://www.librarian.net/stax/1790/asking-the-right-questions-when-to-be-simple-when-to-be-complex/#comments</comments>
		<pubDate>Sun, 09 Jul 2006 13:51:15 +0000</pubDate>
		<dc:creator>jessamyn</dc:creator>
				<category><![CDATA['puters]]></category>
		<category><![CDATA[dchud]]></category>
		<category><![CDATA[onebiglibrary]]></category>
		<category><![CDATA[simplesystems]]></category>
		<category><![CDATA[tek]]></category>

		<guid isPermaLink="false">http://www.librarian.net/stax/1790</guid>
		<description><![CDATA[Dan Chudnov has a blog called One Big Library where he talks about the programmming and social issues invovled in helping people build their own libraries, or making library data so that it&#8217;s accessible and usable and repurposable by others, or rather everyone else. I like the site because while some of it verges into [...]]]></description>
			<content:encoded><![CDATA[<p>Dan Chudnov has a blog called <a href="http://onebiglibrary.net/">One Big Library</a> where he talks about the programmming and social issues invovled in helping people build their own libraries, or making library data so that it&#8217;s accessible and usable and repurposable by others, or rather everyone else. I like the site because while some of it verges into the &#8220;blah blah programming blah blah&#8221; realm, he is always thinking about the human side of why our systems work and don&#8217;t work. This post about <a href="http://onebiglibrary.net/story/software-simplicity-librarian-corner-case">building simple systems</a> and why that&#8217;s so darned <em>complicated</em> really helps me get my head around some of the technology hurdles we as a profession are facing in the age of interoperability and openness, assuming we&#8217;re even interested in moving in that direction. </p>
<blockquote><p>If you&#8217;re a librarian like me and you take this example and turn it toward your own work to help people build their own libraries, it hits you&#8230; it is not simple to build a library of one&#8217;s own. And if you&#8217;re a librarian like me, you have a ready list of why not:</p>
<ul>
<li> Metadata is complicated
    </li>
<li> People in libraries don&#8217;t all use the same items the same way
    </li>
<li> Maybe 20% of the collection is responsible for 80% of the use but that other 80% includes some really important stuff
    </li>
<li>Attempts to use new tools works great for new data but can be exceedingly hard for old stuff. Like, anything predating 1960. Which we have a *lot* of, and which is often *really* important.
    </li>
<li> Did I mention metadata being complicated?</li>
</ul>
</blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.librarian.net/stax/1790/asking-the-right-questions-when-to-be-simple-when-to-be-complex/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

