<?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>Librations &#187; by Meredith Kahn</title>
	<atom:link href="http://www.librations.us/category/good-librations/by-meredith/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.librations.us</link>
	<description>Get here fast and then we&#039;ll take it slow.</description>
	<lastBuildDate>Thu, 12 Aug 2010 01:02:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Lessons for a New Librarian</title>
		<link>http://www.librations.us/2010/02/22/lessons-for-a-new-librarian/</link>
		<comments>http://www.librations.us/2010/02/22/lessons-for-a-new-librarian/#comments</comments>
		<pubDate>Tue, 23 Feb 2010 02:43:35 +0000</pubDate>
		<dc:creator>mkahn</dc:creator>
				<category><![CDATA[by Meredith Kahn]]></category>
		<category><![CDATA[Colorado]]></category>
		<category><![CDATA[first life]]></category>
		<category><![CDATA[librarianship]]></category>

		<guid isPermaLink="false">http://www.librations.us/?p=517</guid>
		<description><![CDATA[I&#8217;m just shy of six months into my job as the Art &#38; Architecture Librarian here at CU-Boulder, and I&#8217;m learning a lot&#8211;about my job, the organization I work for, the students and faculty I serve, and so much more.
Several weeks ago, I helped a student at the reference desk with a particularly difficult question. [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m just shy of six months into my job as the Art &amp; Architecture Librarian here at <a href="http://ucblibraries.colorado.edu/">CU-Boulder</a>, and I&#8217;m learning a lot&#8211;about my job, the organization I work for, the students and faculty I serve, and so much more.</p>
<p>Several weeks ago, I helped a student at the reference desk with a particularly difficult question. We started chatting, and she identified herself as a <a href="http://www2.ed.gov/programs/triomcnair/index.html">McNair Scholar</a>. She asked if the library had a liaison to the McNair program, and I offered to find out for her. Long story short, I am now the liaison to the McNair program.</p>
<p>This brief story illustrates an important lesson: If you express interest in something, there&#8217;s a strong chance you&#8217;ll be asked to be in charge of it.</p>
<p>As a new librarian, how can you use this organizational quirk to your advantage? Well, if you see something that you think needs to be changed, or might just need the attention of a dedicated individual to make it work better, don&#8217;t be afraid to speak up. Make sure folks around you (boss, colleagues, etc.) know what you&#8217;re truly passionate about. And don&#8217;t forget to be strategic about your interests! As a tenure-track librarian here at CU-Boulder, a focus of my developing research agenda has been working with underrepresented students. Serving as the liaison to the McNair program helps me unite the &#8220;librarianship&#8221; and &#8220;research&#8221; pieces of my librarianship/research/service puzzle.</p>
<p>So what do YOU want to be in charge of?  :)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librations.us/2010/02/22/lessons-for-a-new-librarian/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>“We should be so lucky!”: The Kind of Problems You Wish You Had</title>
		<link>http://www.librations.us/2009/09/14/we-should-be-so-lucky/</link>
		<comments>http://www.librations.us/2009/09/14/we-should-be-so-lucky/#comments</comments>
		<pubDate>Mon, 14 Sep 2009 17:11:42 +0000</pubDate>
		<dc:creator>mkahn</dc:creator>
				<category><![CDATA[by Meredith Kahn]]></category>
		<category><![CDATA[Colorado]]></category>

		<guid isPermaLink="false">http://www.librations.us/?p=468</guid>
		<description><![CDATA[Here at the University of Colorado-Boulder, we recently completed a partial renovation of our main library.  We added a technology-equipped learning commons (open 24/5!), a coffee shop (serving high-quality caffeine from local business The Laughing Goat), several new instructional spaces, a more welcoming reference area, and much more (read all about it here).
We anticipated that [...]]]></description>
			<content:encoded><![CDATA[<p>Here at the <a href="http://ucblibraries.colorado.edu/">University of Colorado-Boulder</a>, we recently completed a partial renovation of our main library.  We added a technology-equipped learning commons (open 24/5!), a coffee shop (serving high-quality caffeine from local business The Laughing Goat), several new instructional spaces, a more welcoming reference area, and much more (read all about it <a href="http://ucblibraries.colorado.edu/learningcommons/index.htm">here</a>).</p>
<p>We anticipated that the new spaces would be popular with students, but the response has been even better than we expected.  The library is busier than anyone has ever seen it (especially for this early in the term), and the feedback has been overwhelmingly positive.</p>
<p>But in the midst of our excitement, there is concern.  If the library is full of students and faculty now, what will it look like during midterms and finals?  Will we be able to handle the increased traffic?  Will quality of service suffer?  And how do we spin all of this to our advantage (convincing administration that we need more space, funds, staff, and resources)?  It’s really the kind of problem you wish for, which has caught us a bit off guard.</p>
<p>Is your organization facing a similar challenge?  Maybe you’ve recently introduced a new collection or service, and are overwhelmed by the response you’ve received.  I’m interested in hearing other stories about what to do when things go well, rather than just when they flop.</p>
<p>[This post originally appeared on <a href="http://arlisnap.org/2009/09/14/we-should-be-so-lucky/">ArLiSNAP.org</a>]</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librations.us/2009/09/14/we-should-be-so-lucky/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Information Literacy in Real Life</title>
		<link>http://www.librations.us/2009/08/20/information-literacy-in-real-life/</link>
		<comments>http://www.librations.us/2009/08/20/information-literacy-in-real-life/#comments</comments>
		<pubDate>Fri, 21 Aug 2009 04:09:58 +0000</pubDate>
		<dc:creator>mkahn</dc:creator>
				<category><![CDATA[by Meredith Kahn]]></category>
		<category><![CDATA[first life]]></category>
		<category><![CDATA[information literacy]]></category>
		<category><![CDATA[lifelong learning]]></category>

		<guid isPermaLink="false">http://www.librations.us/?p=453</guid>
		<description><![CDATA[I recently finished a housing search in Boulder, Colorado.  After seeing nearly a dozen apartments, I ended up with a fabulous place to live.  But along the way, I also saw the most frightening rental property I have ever seen.  Let’s call it “the cottage.”
The cottage was advertised in the local paper with very little [...]]]></description>
			<content:encoded><![CDATA[<p>I recently finished a housing search in Boulder, Colorado.  After seeing nearly a dozen apartments, I ended up with a fabulous place to live.  But along the way, I also saw the most frightening rental property I have ever seen.  Let’s call it “the cottage.”</p>
<p>The cottage was advertised in the local paper with very little detail&#8211;just a price, a neighborhood, and a phone number.  The price and location matched what I was looking for, so I called the owner to find out more about the property.  He described it as a “rustic” one bedroom, single-family home, and warned that a tenant had just moved out, so it probably needed a good cleaning before anyone else could move in.  I made an appointment to see it later that morning.  I had a very what-the-hell attitude since it was the first day of my housing search, and I figured that it couldn’t hurt to just take a look.  It wouldn’t waste much time, and I had other apartments to look at later in that same neighborhood.</p>
<p>I arrived at the cottage to find that it was an in-law building built behind another home and accessible only from an alley, not the street on which its address implied it sat.  It was surrounded by overflowing dumpsters and recycling bins.  The entire house was no more than 250 square feet, and it smelled of dead mice and mold.  It appeared (and smelled!) as if it had been vacant for some time.  There were no interior walls, and the ceilings were only about six feet high.  There were holes and cracks in the wood flooring that appeared to be open to a crawl space below.  There was no overhead lighting.  A previous tenant had been heating the building with a space heater.  The refrigerator was mid-1950s vintage&#8211;and not in a good way.  I’ll spare you a description of the bathroom.</p>
<p>Basically, this place was a nightmare.  The punchline to this story?  The landlord wanted $900 a month plus utilities.</p>
<p>So why am I posting this on Librations?  What does it have to do with libraries, or beer for that matter?  First, I really wanted a drink after seeing this place.  And second, this is a great example of how I could have applied my super-librarian powers of information literacy skillz to a real-life situation.</p>
<p>Even though the cottage was advertised in an actual newspaper (this wasn’t some shady Craigslist posting), and the owner paid money (albeit a small amount) for the ad, this doesn’t mean that any of the implied authority that comes with such a source should be automatically associated with the product being advertised.  As librarians, we deal with this sort of thing all the time.  Venerated publishers can do sleazy things (like Elsevier publishing <a href="http://www.guardian.co.uk/commentisfree/2009/may/09/bad-science-medical-journals-companies" target="_blank">fake journals</a> to sell pharmaceuticals).  And Wikipedia (the anti-Elsevier?) has a large number of well written, clearly cited, and authoritative articles, particularly on topics related to popular culture and technology.</p>
<p>The owner’s use of the term “rustic” probably should have set off alarm bells in my head.  In a similar vein, pseudo-research about controversial topics can often be spotted based on the language and style used to discuss an issue.</p>
<p>And finally, sometimes you just have to dive into something to figure out if its credible, relevant to your research, and appropriate for the task at hand.  Man cannot survive on abstracts alone.  It was in the owner’s interest not to tell me too much about the cottage over the phone, so I had to see it for myself and experience the horror first hand.</p>
<p>Seeing this terrifying building wasn’t a failure, just as coming across an article or a book you end up not needing isn’t a failure, either.  It’s just part of the process.  Research (and house hunting), isn’t always clean, linear, quick, or easy.  Sometimes it involves dead ends, wrong turns, and readjustments.</p>
<p>And what’s a good house hunt without at least one horror story, right?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librations.us/2009/08/20/information-literacy-in-real-life/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Nicholson Baker on the Kindle</title>
		<link>http://www.librations.us/2009/07/30/nicholson-baker-on-the-kindle/</link>
		<comments>http://www.librations.us/2009/07/30/nicholson-baker-on-the-kindle/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 02:15:51 +0000</pubDate>
		<dc:creator>mkahn</dc:creator>
				<category><![CDATA[by Meredith Kahn]]></category>
		<category><![CDATA[aesthetics]]></category>
		<category><![CDATA[book as object]]></category>
		<category><![CDATA[ebooks]]></category>

		<guid isPermaLink="false">http://www.librations.us/?p=431</guid>
		<description><![CDATA[Say what you will about Nicholson Baker (of Above the Fold fame/infamy). The man can write.  Persuasively and well.  In the most recent edition of the New Yorker, Baker takes on the Kindle, writing a humorous and thought-provoking first-hand account of his recent purchase of a Kindle 2.
As an author, lover of literature, and a [...]]]></description>
			<content:encoded><![CDATA[<p>Say what you will about Nicholson Baker (of <em>Above the Fold</em> fame/infamy). The man can write.  Persuasively and well.  In the most recent edition of the <em>New Yorker</em>, Baker takes on the Kindle, writing a humorous and thought-provoking <a href="http://www.newyorker.com/reporting/2009/08/03/090803fa_fact_baker" target="_blank">first-hand account</a> of his recent purchase of a Kindle 2.</p>
<p>As an author, lover of literature, and a man concerned with the aesthetic qualities of books, Baker provides a detailed review of his experience using the Kindle 2 and Kindle DX.  Highlights include:</p>
<p><em>The lack of contrast on its screen:</em><br />
&#8220;The problem was not that the screen was in black-and-white; if it had really been black-and-white, that would have been fine. The problem was that the screen was gray. And it wasn&#8217;t just gray; it was a greenish, sickly gray. A postmortem gray. The resizable typeface, Monotype Caecilia, appeared as a darker gray. Dark gray on paler greenish gray was the palette of the Amazon Kindle.&#8221;</p>
<p><em>An elegant and effective description of the rights you have (and the ones you sign away) to your digital content: </em><br />
&#8220;Here&#8217;s what you buy when you buy a Kindle book. You buy the right to display a grouping of words in front of your eyes for your private use with the aid of an electronic display device approved by Amazon. &#8230;Kindle books aren&#8217;t transferrable. You can&#8217;t give them away or lend them or sell them. You can&#8217;t print them. They are closed clumps of digital code that only one purchaser can own. A copy of a Kindle book dies with its possessor.&#8221;</p>
<p><em>And a hilarious accounting of the ecological ramifications of the device:</em><br />
&#8220;Yes, it&#8217;s made of exotic materials that are shipped all over the world&#8217;s oceans; yes, it requires electricity to operate and air-conditioned server farms to feed it; yes, it&#8217;s fragile and it duplicates what other machines do; yes, it&#8217;s difficult to recycle; yes, it will probably take a last boat ride to a Nigerian landfill in five years. But no tree farms are harvested to make a Kindle book; no ten-ton presses turn, no ink is spilled.&#8221;</p>
<p>Ultimately, Baker concludes that while Amazon &#8220;is very good at selling things,&#8221; it hasn&#8217;t yet designed an ebook reader that can truly replace the utility and aesthetic joy of books and newspapers.  For books, Baker recommends reading on an iPod Touch or an iPhone over the Kindle.</p>
<p>As a book lover, librarian, and student of art and design, I&#8217;m stuck ruminating on Baker&#8217;s descriptions of the Kindle&#8217;s many failings when it comes to replicating the aesthetic experience of books and newspapers.  But I get paid to care about books, to understand and evaluate their properties as both objects and containers for information.  Will the average reader care about any of this?  Will he or she notice the lack of contrast between creamy paper and crisp, black letters in a beautiful and (readable!) font?  What about the lack of typographical design, illustrations, color, or other features?Â At first, no, they might not.  But I think they will eventually.</p>
<p>Beautiful and functional design often has the ability to be transparent if not invisible, especially to those unfamiliar with kerning, gutters, serifs, paper quality, binding methods, or other features of the books that occupy our shelves, coffee tables, and nightstands.  But I&#8217;m confident that readers will eventually notice they&#8217;re being sold an inferior product, and I look forward to widespread demand for higher-quality ebooks and readers.  If the Kindle is a terrible device, then the solution isn&#8217;t to reject the whole idea of ebooks and machines for reading.  Instead, I believe that readers, librarians, book lovers, and everyone else should be making lots of noise about the kind of ebooks and devices we&#8217;d like to see&#8211;their features, licensing and rights schemes, and overall user experience.</p>
<p>What do <strong><em>you</em></strong> think?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.librations.us/2009/07/30/nicholson-baker-on-the-kindle/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>&#8220;Orwellian&#8221; Kindle Deletions: Legitimate Copyright Kerfuffle, Giant Yawn, or Teachable Moment?</title>
		<link>http://www.librations.us/2009/07/22/%e2%80%9corwellian%e2%80%9d-kindle-deletions-legitimate-copyright-kerfuffle-giant-yawn-or-teachable-moment/</link>
		<comments>http://www.librations.us/2009/07/22/%e2%80%9corwellian%e2%80%9d-kindle-deletions-legitimate-copyright-kerfuffle-giant-yawn-or-teachable-moment/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 20:45:20 +0000</pubDate>
		<dc:creator>mkahn</dc:creator>
				<category><![CDATA[by Meredith Kahn]]></category>
		<category><![CDATA[access]]></category>
		<category><![CDATA[copyright]]></category>
		<category><![CDATA[digital rights management]]></category>
		<category><![CDATA[ebooks]]></category>
		<category><![CDATA[information literacy]]></category>
		<category><![CDATA[outreach]]></category>

		<guid isPermaLink="false">http://www.librations.us/?p=291</guid>
		<description><![CDATA[

Last week, Amazon remotely deleted copies of George Orwell&#8217;s 1984 and Animal Farm from users&#8217; Kindles.  As it turns out, the ebook publisher selling the editions didn&#8217;t actually own the rights for these works.  As one could imagine, the blogospheric reaction to this event has been a mixture of smirking irony, outrage, confusion, and lots [...]]]></description>
			<content:encoded><![CDATA[<div>
<div>
<p>Last week, Amazon <a href="http://opinionator.blogs.nytimes.com/2009/07/20/kindle-swindle/" target="_blank">remotely deleted</a> copies of George Orwell&#8217;s <em>1984</em> and <em>Animal Farm</em> from users&#8217; Kindles.  As it turns out, the ebook publisher selling the editions <a href="http://www.nytimes.com/2009/07/18/technology/companies/18amazon.html" target="_blank">didn&#8217;t actually own the rights</a> for these works.  As one could imagine, the blogospheric reaction to this event has been a mixture of smirking irony, outrage, confusion, and lots of I-told-you-so.  (See the first link above for an excellent overview of the reaction.)</p>
<p>I had a quick succession of thoughts while reading about the deletions:</p>
<ul>
<li>ZOMG!  Jeff Bezos is stealing your stuff!</li>
<li>Um, you bought an unauthorized ebook from a shady publisher.  Why are you so surprised?</li>
<li>Wait, how were you supposed to know the publisher was shady?</li>
<li>Huh, remote deletion wasn&#8217;t in the terms of service. But who reads those anyway?</li>
<li>How can consumers avoid this in the future?</li>
</ul>
<p>In answer to the question that serves as a title for this post, I see the deletions as all three&#8230; Yes, they are a perfect example of why copyright is weird. No, I&#8217;m not really surprised (although the level of comic irony is staggering). And the whole thing could prove to be an interesting conversation starter!</p>
<p>At that point my librarian-<em>jutsu</em> kicked in, and I started thinking about how to talk about this nugget of current events goodness with my users (students and faculty).  How can I use this as an opportunity to talk about things like DRM, reading legalese before you buy/agree, copyright terms, applying information literacy beyond books, etc.?  And how can I segue that conversation into a discussion of services provided by librarians and the library?</p>
<p>Have YOU run into any interesting teachable moments lately?Â  And how did you make the most of them?</p>
<p>[A modified version of this post originally appeared at <a href="http://arlisnap.org/2009/07/21/orwellian-kindle-deletions-legitimate-copyright-kerfuffle-or-giant-yawn/" target="_blank">ArLiSNAP.org</a>]</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.librations.us/2009/07/22/%e2%80%9corwellian%e2%80%9d-kindle-deletions-legitimate-copyright-kerfuffle-giant-yawn-or-teachable-moment/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

