<?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/"
	xmlns:cc="http://creativecommons.org/ns#" >

<channel>
	<title>Molly Kleinman &#187; Libraries</title>
	<atom:link href="http://mollykleinman.com/category/libraries/feed/" rel="self" type="application/rss+xml" />
	<link>http://mollykleinman.com</link>
	<description></description>
	<lastBuildDate>Sun, 23 Oct 2011 16:51:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<cc:license >Attribution CC BY</cc:license><dc:rights  >Attribution CC BY</dc:rights>		<item>
		<title>When librarians are obstacles</title>
		<link>http://mollykleinman.com/2010/11/16/when-librarians-are-obstacles/</link>
		<comments>http://mollykleinman.com/2010/11/16/when-librarians-are-obstacles/#comments</comments>
		<pubDate>Wed, 17 Nov 2010 00:28:24 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Musings]]></category>
		<category><![CDATA[Mozilla Drumbeat Festival]]></category>
		<category><![CDATA[Open Ed 2010]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/?p=190</guid>
		<description><![CDATA[Heading into the Open Ed Conference and especially the Mozilla Drumbeat Festival, I expected to be one of only a handful of librarians participating. Librarians haven&#8217;t been terribly involved or engaged with the open education movement, but our values and &#8230; <a href="http://mollykleinman.com/2010/11/16/when-librarians-are-obstacles/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Heading into the Open Ed Conference and especially the Mozilla Drumbeat Festival, I expected to be one of only a handful of librarians participating. Librarians haven&#8217;t been terribly involved or engaged with the open education movement, but our values and missions align so well that I expected to be welcomed by the professors and the edupunks as a peer and fellow traveller. Well, I got the first part right &#8211; I met only a couple of librarians all week &#8211; but the second, not so much. Imagine my surprise when the other two speakers in the session on libraries and the future of OER spent much of their time <em>criticizing</em> the ways in which librarians have engaged with open education, and lamenting the possibility of librarians being anything other than a liability. </p>
<p>Julià Minguillón, a computer science professor who spoke about <a href="http://hdl.handle.net/10609/4963">digital preservation issues</a>, described attempting to deposit an equation into his university library&#8217;s OER repository, only to be told that because his equation did not have a title, it could not be included in the collection. He then went on to criticize librarians&#8217; obsession with the &#8220;useless&#8221; metadata of &#8220;author, title, date.&#8221; He argued that if we put librarians in charge of OER repositories (exactly the thing I argued for in my paper), we will sacrifice broad, immediate access in favor long-term preservation and proper metadata schemas. </p>
<p><a href="http://blogs.cetis.ac.uk/johnr/">R. John Robertson</a> gave a paper about the <a href="http://hdl.handle.net/10609/4847">role libraries can play in supporting OER initiatives</a> but a significant portion of his presentation was given over to his concerns about librarian participation in this work. His experience with librarians is that they are so risk averse that the merest hint of a copyright issue is likely to send them running for the hills. Like Minguillón, he had anecdotes to back up his worries about librarians as obstacles in the field of open education.</p>
<p>In a word: Blergh! How did this happen? Why, despite biannual New York Times articles about how <a href="http://www.nytimes.com/2009/02/16/books/16libr.html">modern</a> and <a href="http://www.nytimes.com/2007/07/08/fashion/08librarian.html">hip</a> librarians have become, are we still perceived on our own campuses as fearful impediments to progress?  </p>
<p>Okay, I know why. Some librarians <em>are</em> fearful impediments to progress. Some librarians allow perfect metadata to be the enemy of good access. Some libraries, as institutions, do not foster innovation and experimentation, and are deeply resistant to change. It&#8217;s so disappointing. </p>
<p>It probably says something about <a href="http://mollykleinman.com/2009/07/14/personal-update-new-job-same-library/">the job I&#8217;ve had for the last year and a half</a> that I see this primarily as a failure of management. On the plane to Barcelona I read a column by Meredith Farkas in American Libraries called &#8220;<a href="http://americanlibrariesmagazine.org/columns/practice/nurturing-innovation">Nurturing Innovation: Tips for Managers and Administrators</a>.&#8221; She offers a number of excellent suggestions for ways to adjust the institutional culture at libraries to support and embrace innovation: Encourage staff to learn and play, give staff time to experiment with potential new initiatives, keep an open mind, develop a risk tolerant culture. These suggestions kept coming back to me at Open Ed as I struggled to defend librarians and libraries against accusations of stodginess. I wanted to hand the article over to the people who complained about their uptight, change resistant libraries and say, &#8220;It doesn&#8217;t have to be this way. Go talk to your Dean. Make it better.&#8221; I also, in that way that sometimes happens, added one more suggestion to the list, thinking it was from Farkas but it&#8217;s from somewhere else, part of a theme that developed at Open Ed: Library administrators must make some room in their budgets for failure. </p>
<p>Innovation and progress can&#8217;t happen without failure. It&#8217;s how we learn, as individuals and as institutions and as species. Yes, library budgets are tight these days. Tighter than we ever thought they could get. With money so tight, and cuts so deep, it&#8217;s easy to think that now is not the time to take risks, but of course, now is exactly the time to take risks. How else will we prepared to address the challenges that await us in next year&#8217;s budget cycle, and the one after that, and the one 15 years from now? </p>
<p>To use one relevant example: The current commercial scholarly publishing apparatus <a href="http://www.arl.org/sparc/pricing/index.shtml">is choking us</a>. We know this. Knowing this, we have two choices: We can invest in activities that could ease the financial pressure &#8211; open repositories, deposit mandates, awareness campaigns &#8211; or we can choke. In this case, many libraries are experimenting, and sometimes <a href="http://www.ala.org/ala/mgrps/divs/acrl//publications/crlnews/2009/oct/pyrrhicvict.cfm">those experiments even fail</a>. As Farkas points out, when our experiments fail we still learn something valuable from them, something that can set us on a path to succeed the next time. </p>
<p>It&#8217;s not enough simply to encourage our staff to experiment. We need to give them money to play with, to set up a repository or buy a license to a promising tool or hire an expert to train staff in something new. It doesn&#8217;t have to be a lot of money, but it does have to be relatively free from strings. And then, we need to make sure our experimenting staff share what they&#8217;ve learned with colleagues in other libraries, the successes and the failures. It&#8217;s how we will all evolve. </p>
<p>So to wrap up this meandering post with a tidy bow: Higher education is changing, and our campuses are full of people (many of whom were at Open Ed and Drumbeat) experimenting with new models, tools, and philosophies related to teaching, learning, and research. The primary responsibility of academic libraries is to support teaching, learning, and research, and so those experiments and the people conducting them are highly relevant to us. We must make sure that we remain relevant to them. If they see us as an obstacle it is only a matter of time before we become obsolete. We want those experimenters and innovators to view the library as both a resource for and a partner in their work, and we can do that by funding innovation among our own staff, expanding our definition of the library&#8217;s role on campus, and embracing the possibility of failure. If we neglect to do these things, we don&#8217;t just risk becoming obsolete, we guarantee it. </p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2010/11/16/when-librarians-are-obstacles/feed/</wfw:commentRss>
		<slash:comments>31</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
		<item>
		<title>The OCLC data licensing saga: Adapt or die</title>
		<link>http://mollykleinman.com/2008/11/24/oclc-licensing-saga/</link>
		<comments>http://mollykleinman.com/2008/11/24/oclc-licensing-saga/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 00:14:38 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[licensing]]></category>
		<category><![CDATA[metadata]]></category>
		<category><![CDATA[OCLC]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/?p=83</guid>
		<description><![CDATA[I&#8217;m coming late to the OCLC WorldCat records policy conversation, but that gives me the advantage of having digested some of the discussion that&#8217;s already happened. There&#8217;s a little bibliography at the end of this post that points to many &#8230; <a href="http://mollykleinman.com/2008/11/24/oclc-licensing-saga/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m coming late to the OCLC WorldCat records policy conversation, but that gives me the advantage of having digested some of the discussion that&#8217;s already happened. There&#8217;s a little bibliography at the end of this post that points to many of the comments I read and considered.</p>
<p><del datetime="2008-11-25T15:07:19+00:00">Peter Suber</del> <a href="http://www.earlham.edu/~peters/fos/2008/11/oclc-fighting-oa-to-bibliographic-data.html">Gavin Baker</a> summarized the issue nicely:</p>
<blockquote><p>There&#8217;s been a dust-up lately over a policy change announced by the <a href="http://www.oclc.org/">Online Computer Library Center</a> for the terms of use for <a href="http://www.worldcat.org/">WorldCat</a>, the union catalog of bibliographic records contributed by OCLC member libraries.</p>
<p>It&#8217;s disputed whether OCLC provides [Open Access] to the full WorldCat data: Open Library&#8217;s Aaron Swartz <a href="http://www.aaronsw.com/weblog/oclcscam">says it doesn&#8217;t</a>; OCLC&#8217;s Karen Calhoun <a href="http://www.aaronsw.com/weblog/oclcscam#c11">says it does</a>.</p>
<p>The new <a href="http://www.oclc.org/worldcat/catalog/policy/">Policy for Use and Transfer of WorldCat Records</a> supercedes the earlier <a href="http://www.oclc.org/support/documentation/worldcat/records/guidelines/">Guidelines for the Use and Transfer of OCLC-Derived Records</a>, last revised in the pre-Web era. (Karen Coyle <a href="http://www.opencontentalliance.org/?p=162#comment-16">points out</a> that the Guidelines were themselves a response to an earlier attempt by OCLC to claim copyright in WorldCat records. The new policy avoids the term <em>copyright</em>, but does make an oblique reference to &#8220;the intellectual property rights [in WorldCat or WorldCat Records]&#8220;.) The new policy is slated to go into effect in February 2009.</p>
<p>Aside from the name change (from &#8220;guidelines&#8221; to &#8220;policy&#8221;, implying enforceability), key points of the new policy include prohibitions on commercial or &#8220;unreasonable&#8221; use. (An earlier version of the policy also required attribution to OCLC in each record re-used; in the latest version, the attribution requirement has been weakened to a recommendation.)</p></blockquote>
<p>The dust-up arose because OCLC&#8217;s new policy for use of WorldCat records seems to restrict what people can do with OCLC&#8217;s records, in ways that the old guidelines hinted at but didn&#8217;t actually do. Though it sounds like this was not OCLC&#8217;s intention (more on that in a moment) the new policy, if taken literally, prohibits uses that many libraries and organizations are already making of OCLC records, and blocks potential uses that could have been opened up by a more liberal policy.</p>
<p>A couple of people have asked me to write about the brouhaha from a copyright perspective, but this isn&#8217;t a copyright issue at all. Like many of the challenges facing libraries in the digital age, the problem isn&#8217;t copyright, it&#8217;s license agreements; in this case, the agreement between OCLC and the libraries that participate in WorldCat.</p>
<p>Most of the elements that make up a WorldCat record &#8211; metadata that includes information on author, title, and year of publication &#8211; are not copyrightable. They&#8217;re facts. Indeed, much of what makes OCLC&#8217;s purported attempt to control WorldCat records so objectionable is that not only are the records uncopyrightable, but even if they were, the copyright would belong to the libraries that created the records. OCLC does not produce the records in WorldCat, it merely ingests them from member libraries. For OCLC to claim copyright or any other kind of ownership over those records offends the sensibilities of the librarians who create the records that make up the catalog and who pay a lot of money to participate in the system, and it worries the librarians and others who depend on the catalog as a shared source of quality metadata. When OCLC took it even further, and used the policy to place extensive license restrictions on the kinds of uses that members can make of the records &#8211; limiting acceptable activities not just to non-commercial uses but to &#8220;reasonable&#8221; non-commercial uses &#8211; that was the last straw.</p>
<p>The irony here is that OCLC&#8217;s stated goal was to <strong>expand</strong> sharing and re-use of WorldCat records, and my sense is that this really is what they tried to do. OCLC Vice President Karen Calhoun&#8217;s discussion of Creative Commons, and OCLC&#8217;s &#8220;human readable&#8221;-esque summary that is a direct nod to CC licenses, suggest that this policy was created as a good faith effort to clarify the terms of use in a way that would improve members&#8217; ability to use and share WorldCat records. In both public and private statements, people at OCLC have said that the policy isn&#8217;t intended to prohibit the kinds of non-profit record sharing that libraries traditionally engage in. In a podcast interview on <a href="http://blogs.talis.com/panlibus/archives/2008/11/oclc-talk-with-talis-about-the-new-record-use-policy.php">Talking with Talis</a>, Karen Calhoun said that the old guidelines were terribly out of date and overly restrictive, and that the aim in creating a new policy was to reduce confusion about the many ways that people could use WorldCat records by clarifying and modernizing the language of the policy.</p>
<p>So how did OCLC get it so wrong? How did they end up with a policy that is so very un 2.0, so very unsharing? A policy that has librarians all over the web questioning its motives and its non-profit status?  Terry Reese <a href="http://oregonstate.edu/~reeset/blog/archives/574">frames it in terms of power hungry monopolies</a>, but I think it comes down to fear. The same fear that has publishers <a href="http://toc.oreilly.com/2008/11/on-digital-book-drm.html">begging for interoperable DRM for e-books</a>, the same fear that has <a href="http://recordingindustryvspeople.blogspot.com/">music and movie companies continuing to sue their fans</a> despite <a href="http://www.boingboing.net/2008/11/17/legendary-harvard-la.html">growing resistance</a>. <strong>It&#8217;s the fear that the old business models don&#8217;t work anymore, and that the old businesses will die.</strong> OCLC likes the idea of Creative Commons licensing, likes the idea of open data, but what OCLC likes even more is survival. OCLC wants to embrace the librarianish ethos of sharing, but only if that sharing does not in any way threaten its revenue stream. This is the policy of an organization that is trying to protect its market share by restricting access to its content, instead of protecting its market share by providing products and services that are better than everyone else&#8217;s. Sure, there are overtones of monopoly, but OCLC&#8217;s monopoly on catalog data is fragile at best and its leaders know that. Rather, this is about resisting the dramatic changes that a web-based business model would require. One in which OCLC isn&#8217;t the only place to access catalog data, it&#8217;s the best place.</p>
<p><strong>Additional readings (only includes material not linked in the post itself)</strong></p>
<ul>
<li><a href="http://www.betaversion.org/~stefano/linotype/news/220/">Stefano&#8217;s Linotype: Rule #1 for Surviving Paradigm Shifts: Don’t S**t Where You Eat</a></li>
<li><a href="http://www.libology.com/blog/2008/11/03/oclc-worldcat-is-the-tiger-not-the-lady.html">Libology Blog: OCLC WorldCat is the Tiger, not the Lady?</a></li>
<li><a href="http://wiki.code4lib.org/index.php/OCLC_Policy_Change">Code4Lib Wiki: OCLC Policy Change</a></li>
<li><a href="http://www.aaronsw.com/weblog/oclcscam">Raw Thought: Stealing Your Library: The OCLC Powergrab</a></li>
<li><a href="http://blog.ecorrado.us/2008/11/03/oclcs-new-policy-for-use-and-transfer-of-worldcat-records/">blog.ecorrado.us: OCLC&#8217;s new Policy for Use and Transfer of WorldCat Records</a></li>
<li><a href="http://dynamicorange.com/2008/11/06/oclc-record-usage-copyright-contracts-and-the-law/">Rob Styles: OCLC Record Usage, Copyright, Contracts, and the Law</a></li>
</ul>
<p>Hat tip to Jake Glenn for first telling me about the story and passing on many useful links.</p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2008/11/24/oclc-licensing-saga/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
		<item>
		<title>DLF Forum: Library of Congress and Flickr</title>
		<link>http://mollykleinman.com/2008/11/13/dlf-forum-library-of-congress-and-flickr/</link>
		<comments>http://mollykleinman.com/2008/11/13/dlf-forum-library-of-congress-and-flickr/#comments</comments>
		<pubDate>Thu, 13 Nov 2008 20:43:29 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Conferences]]></category>
		<category><![CDATA[HOWTO]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Musings]]></category>
		<category><![CDATA[DLF Fall Forum 2008]]></category>
		<category><![CDATA[Flickr]]></category>
		<category><![CDATA[Library of Congress]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/?p=79</guid>
		<description><![CDATA[Phil Michel and Michelle Springer from the Library of Congress presented on the LOC&#8217;s Flickr Pilot Project. The Library of Congress was the first cultural heritage institution to partner with Flickr to share photographic content and invite user participation and &#8230; <a href="http://mollykleinman.com/2008/11/13/dlf-forum-library-of-congress-and-flickr/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://flickr.com/photos/library_of_congress/2179923220/"><img class="alignnone size-medium wp-image-80" title="Women at work on bomber" src="http://mollykleinman.com/wp-content/uploads/2008/11/womenatworkloc-300x241.jpg" alt="Women at work on bomber, from the Library of Congress " width="300" height="241" /></a></p>
<p>Phil Michel and Michelle Springer from the Library of Congress presented on the LOC&#8217;s Flickr Pilot Project. The Library of Congress was the first cultural heritage institution to partner with Flickr to share photographic content and invite user participation and comments. With 15 institutions participating in what is now the <a title="Flickr Commons" href="http://flickr.com/commons" target="_blank">Flickr Commons</a>, it is an idea that caught on quickly and has been quite successful. I&#8217;ve been very excited about this project since its launch, and so I was motivated to clean up and blog my rather extensive notes on the session. For more information about the project, check out this <a href="http://www.loc.gov/today/cyberlc/feature_wdesc.php?rec=4281">LOC webcast</a>.</p>
<h3>Background</h3>
<p>The motivation for the project came from a desire to explore including user generated content (UGC) in LOC descriptive processes. Photos seemed like a good place to start because there is no language barrier, there was already a big collection of photos online, and because they&#8217;re fun.</p>
<p>Initial investigations showed that bringing tagging to LOC collections would have had high technical barriers if handled in-house. There was a desire to keep initial expenditures low, and so they started looking around for existing web 2.0 sites that were doing the things they wanted to do.</p>
<p>The project had three goals: Increase awareness of LOC collections; gain better understanding of social tagging; gain experience participating in the kinds of web communities that are interested in LOC materials</p>
<p>There were a number of principles that guided the development of the pilot project: The involved content must already be available on the LOC site; the agreement with the third party site must be non-exclusive; access to the content must must be free; there must be an option to control or exclude advertising on the account; LOC should be clearly identified as the source of the images; must allow LOC to remove and moderate user-supplied content to prevent inappropriate tags and comments; UGC must be clearly distinguishable from Library generated content; must be possible to accurately convey copyright status.</p>
<p>Flickr had a great deal of appeal as a partner: It recently announced the upload of its 3 billionth picture, and has an active user community of over 23 million members. It had a pre-existing, vibrant community built around photography and a conversation that included notes, comments, and tags. From a technical standpoint, it also had APIs that allow for batch uploads and batch downloads of UGC, and a history of dealing with alternative copyright status (Creative Commons licenses).</p>
<h3>Getting it off the ground</h3>
<p>Flickr programmed the &#8220;No Known Restrictions&#8221; option especially for the LOC partnership, and it is now used by most of the institutions participating in The Commons. Every institution has its own page in its own webspace the explains exactly what they mean by the statement.</p>
<p>Some time and effort was required on the part of the General Counsel&#8217;s office to work with Flickr to create a modified Terms and Conditions agreement that could deal appropriately with the Library&#8217;s status as a government institution.</p>
<p>Technical process: Someone (I missed who &#8211; Flickr, LOC, or both) built a Java(?) app called Flickrj to push and pull content between the LOC databases and Flickr&#8217;s. They chose selected MARC fields whose content would go to Flickr along with the photos: The MARC 856 field was used as unique machine tag value, and so was the DublinCore identifier field.</p>
<p>All together, getting the project off the ground took about 100 hours of work for technical staff.</p>
<p>The photos all went to Flickr in their rough state. LOC folks didn&#8217;t do any cropping, color fixing, or clean up of dust or scratches. Part of the curiosity was to see how the public would respond to the images in this rough form.</p>
<p>Startup investments: The Library of Congress purchased a $24.95 Flickr Pro account, which offers members unlimited uploads and stats about traffic to photos. The Pro account is an annual expense that will go on as long as the project does. All Commons member institutions have pro accounts. There was no full time staff assigned to the project, but it required General Counsel involvement, some big conference calls, and eight staffers who contributed about 20 hours each to collaborate with Flickr on development.</p>
<h3>Launching and maintaining</h3>
<p>This was the first project that LOC ever announced without a press release. There were announcements on the Library of Congress and Flickr blogs, and the organizers considered it a soft launch. Though it involved no mainstream press, there was an enormous initial response, totally out of proportion to what was expected. The result was some near-immediate revisions of plans for maintenance and direct staff involvement; the scale was too big to be as involved as they&#8217;d planned.</p>
<p>A number of LOC staff share responsibility for monitoring all new comments, notes, and tags. They use the Flickrj app to pull all the new UGC at once. It takes about 2 hours a week to moderate comments/notes/tags for spam and inappropriateness. Sometimes users call attention to these things before staff find them. There are very few problems with inappropriate tags or comments; the Flickr community is quite well-behaved. LOC staff don&#8217;t correct spelling or syntax or remove seemingly useless tags. Staff do accept group invitations from public group administrators, but they only join public, nudity/vulgarity-free groups, so monitoring the group invites also takes time.</p>
<p>Updates to the images themselves take 15-20 hours a week. These involve corrections to descriptive information, fixes in the LOC catalog, and occasionally image fixes. Sometimes the orientation of images is wrong. First they fix it on the LOC server, then they generate new derivatives, and then send corrected versions to Flickr. In general, they limit edits to very basic changes and real errors. Sometimes they&#8217;ll point people from the LOC catalog back to Flickr when large amounts of conversation, updating, and information-sharing are taking place for a particular photo.</p>
<p>During the Q&amp;A, someone asked about how have time pressures changed over the course of the project. Turns out, they haven&#8217;t exactly gone down, though they have shifted. When the project first launched, staff was checking the new comments and tags every 24 hours, and it was totally overwhelming. Efficiencies have come from the technical solutions, like the ability to batch download all new comments, notes, and tags. However, as the number of photos keeps going up, time demands on moderators continue to go up. Part of time demand comes from level of participation in the community, which is a steady stream; activity doesn&#8217;t stop on the older photos, so the rising total number of images leads to a rising total amount of new user generated content.</p>
<h3>Outcomes</h3>
<p>One of the main goals of the project was to drive more traffic to the LOC photo collections website, and it worked. People visit the LOC pages for higher resolution images, to get additional information, and to browse related collections. The organizers feel that the pilot has definitely achieved goal of raising awareness of LOC photo collections.</p>
<p>An unexpected outcome: Major search engines are finding, exposing, and weighting LOC&#8217;s Flickr images in search results. Many of the photos rank very high in images searches. It&#8217;s an unforseen way to further expose the content to the world.</p>
<p>Many of LOC photos are also being embedded in blogs all over the web (including this one). When it happens via &#8220;Blog this&#8221; function in Flickr, it&#8217;s easy for LOC to track it (and I imagine it&#8217;s trackable even when it happens in other ways).</p>
<p>The user involvement has been very interesting as a source of further study. There is a core group of about 20 commenters who provide historical research, fixes, comments, notes, etc. They&#8217;ll often support the information with citations, links to NYTimes archives and other external sites and archives. There are also 10 &#8220;power taggers&#8221; who have applied more than 3,000 tags each. One person was responsible for over 5,000 tags. The people at LOC did some work examining the different types of tags that people apply, and identified nine different categories: LC description based, new descriptive words, new subject words, emotional/aesthetic responses, personal knowledge/research, machine tags, variant forms, foreign language, and miscellaneous.</p>
<p>Users frequently post modern photos in the comments to show what the featured locations look like now. Sometimes people will go to the featured location and reenact the photos. There is quite a bit of playfulness and humor in much of the user involvement. Notes are a useful way to identify people in crowd shots and to transcribe text that appears in the photos. Some people also use notes to make jokes or silly comments, and while some people in the Flickr community have objected to the proliferation of notes, LOC has decided that for now the value of the function outweighs the irritation.</p>
<p>Conclusion: There has been a great response to the pilot, and great user participation, learned a lot. It stimulated conversation both between users &amp; librarians and also between librarians. The project tapped into expertise in that resides in communities of interest. It brought up issues related to presentation and engagement that can inform decisions about how materials are presented on the Library&#8217;s own web site. While there are some risks associated with jumping into the web 2.0 world, and you have to be willing to cede some control, the benefits and rewards have been terrific.</p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2008/11/13/dlf-forum-library-of-congress-and-flickr/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
		<item>
		<title>University of Michigan Library adopts Creative Commons licenses</title>
		<link>http://mollykleinman.com/2008/10/16/university-of-michigan-library-adopts-creative-commons-licenses/</link>
		<comments>http://mollykleinman.com/2008/10/16/university-of-michigan-library-adopts-creative-commons-licenses/#comments</comments>
		<pubDate>Thu, 16 Oct 2008 14:19:07 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Creative Commons Evangelism]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[MLibrary]]></category>
		<category><![CDATA[University of Michigan]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/?p=71</guid>
		<description><![CDATA[I am thrilled to report that the University of Michigan Library has adopted Creative Commons licenses for Library-produced content. From the press release: The University of Michigan Library is adopting Creative Commons Attribution-Non-Commercial licenses for all works created by the &#8230; <a href="http://mollykleinman.com/2008/10/16/university-of-michigan-library-adopts-creative-commons-licenses/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I am thrilled to report that the University of Michigan Library has adopted Creative Commons licenses for Library-produced content. </p>
<p>From the <a href="http://www.lib.umich.edu/creativecommons/">press release</a>:</p>
<blockquote><p>The University of Michigan Library is adopting Creative Commons Attribution-Non-Commercial licenses for all works created by the Library for which the Regents of the University of Michigan hold the copyrights. These works include bibliographies, research guides, lesson plans, and technology tutorials. The Library believes that the adoption of Creative Commons licenses is perfectly aligned with our mission, “to contribute to the common good by collecting, organizing, preserving, communicating, and sharing the record of human knowledge.”</p>
<p>Commented University Librarian Paul Courant, &#8220;Using Creative Commons licenses is another way the University Library can act on its commitment to the public good. By marking our copyrighted content as available for reuse, we offer the University community and the public a rich set of educational resources free from traditional permissions barriers.&#8221;</p></blockquote>
<p>It is a proud week to be a Michigan librarian (see also <a href="http://www.ns.umich.edu/htdocs/releases/story.php?id=6774">this announcement</a> about the new Hathi Trust shared digital repository, and <a href="http://www.ns.umich.edu/htdocs/releases/story.php?id=6735">this one</a> about our shiny new Espresso Book Machine). It&#8217;s amazing to work in a library that has strongly committed to innovation without losing sight of a core value system centered around public service. I feel very lucky. Go blue!</p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2008/10/16/university-of-michigan-library-adopts-creative-commons-licenses/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
		<item>
		<title>UM receives grant for Copyright Review Management System</title>
		<link>http://mollykleinman.com/2008/09/11/um-copyright-review-management-system/</link>
		<comments>http://mollykleinman.com/2008/09/11/um-copyright-review-management-system/#comments</comments>
		<pubDate>Thu, 11 Sep 2008 21:01:48 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Public domain]]></category>
		<category><![CDATA[digitization]]></category>
		<category><![CDATA[IMLS]]></category>
		<category><![CDATA[Michigan]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/?p=67</guid>
		<description><![CDATA[This is local news for me, but exciting and important on a national level (at least I like to think so). The University of Michigan Library was just awarded a grant for over half a million dollars from the Institute &#8230; <a href="http://mollykleinman.com/2008/09/11/um-copyright-review-management-system/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This is local news for me, but exciting and important on a national level (at least I like to think so).</p>
<p>The University of Michigan Library was just awarded a grant for over half a million dollars from the <a href="http://www.imls.gov/about/about.shtm">Institute of Museum and Library Services</a>, to develop a copyright review management system which will improve the reliability of copyright status determinations. </p>
<p><a href="http://www.imls.gov/news/2008/091008a_list.shtm#MI">Here are the details</a>:</p>
<blockquote><p>The University of Michigan Library will create a Copyright Review Management System (CRMS) to increase the reliability of copyright status determinations of books published in the United States from 1923 to 1963, and to help create a point of collaboration for other institutions. The system will aid in the process of making vast numbers of these books available online to the general public. Nearly half a million books were published in the United States between 1923 and 1963, and although many of these are likely to be in the public domain, individuals must manually check their copyright status. If a work is not in the public domain, it cannot be made accessible online. The CRMS will allow users to verify if the copyright status has been determined. </p></blockquote>
<p>The project was inspired by the work that the Michigan Library is already doing to determine the copyright status of the thousands of books published between 1923 and 1963 that Google has digitized from our collections. Books published during that period are in the public domain if their copyrights were not renewed or if proper copyright notice was not included in the publication. Most digitization projects, including Google&#8217;s, block access to all books published after 1922 because their copyright status is unknown and difficult to determine. Michigan has a workflow in place that uses copyright renewal records and page images from the books to research the copyright status of those works, and to open up access to the ones that turn out to be in the public domain. </p>
<p>The Copyright Review Management System will build on this work, and support efficient collaboration among institutions. It joins <a href="http://mollykleinman.com/2008/08/26/oclcs-new-copy…dence-registryoclcs-new-copyright-evidence-registry/">OCLC&#8217;s new Copyright Evidence Registry </a> in the growing field of collaborative library copyright determination projects. My understanding is that Michigan is already sharing data with OCLC, and presumably our collaborators will as well.  It&#8217;s nice when collaborative projects collaborate with each other. </p>
<p>Michigan&#8217;s project will raise the impact and usefulness of mass digitization projects by drastically increasing the number of digitized works that libraries can safely share with the public. In the absence of a reasonable orphan works bill, or even, dare I say it, some much-needed improvements in copyright law, it&#8217;s great to see libraries working to expand the known public domain and squeeze every last usable work from their massively digitized stacks. </p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2008/09/11/um-copyright-review-management-system/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
		<item>
		<title>OCLC&#8217;s new Copyright Evidence Registry</title>
		<link>http://mollykleinman.com/2008/08/26/oclcs-new-copyright-evidence-registry/</link>
		<comments>http://mollykleinman.com/2008/08/26/oclcs-new-copyright-evidence-registry/#comments</comments>
		<pubDate>Tue, 26 Aug 2008 15:55:25 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[OCLC]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/?p=64</guid>
		<description><![CDATA[OCLC has launched the WorldCat Copyright Evidence Registry. From the press release: The WorldCat Copyright Evidence Registry is a community working together to build a union catalog of copyright evidence based on WorldCat, which contains more than 100 million bibliographic &#8230; <a href="http://mollykleinman.com/2008/08/26/oclcs-new-copyright-evidence-registry/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>OCLC has launched the <a href="http://www.worldcat.org/copyrightevidence">WorldCat Copyright Evidence Registry</a>.</p>
<p>From the <a href="http://www.oclc.org/news/releases/200832.htm">press release</a>: </p>
<blockquote><p>The WorldCat Copyright Evidence Registry is a community working together to build a union catalog of copyright evidence based on WorldCat, which contains more than 100 million bibliographic records describing items held in thousands of libraries worldwide. In addition to the WorldCat metadata, the Copyright Evidence Registry uses other data contributed by libraries and other organizations&#8230;</p>
<p>&#8220;Having a practical registry of copyright evidence is vital to our objective of providing our scholars and students with more digital content, one goal of Stanford&#8217;s mass digitization projects,&#8221; said Catherine Tierney, Associate University Librarian for Technical Services, Stanford University. &#8220;By leveraging the value of its massive database, OCLC is in a unique position to champion cooperative efforts to collect evidence crucial to determining copyright status.&#8221;</p></blockquote>
<p>It&#8217;s good that OCLC is creating a copyright status registry. A well-populated registry, by and for librarians, with good and useful metadata, could eventually save users real time and money. Currently, we have a handful of institutions doing major digitization projects that are separately investigating copyright status on a large scale. It&#8217;s inefficient, with lots duplicated effort. Copyright evidence is exactly the kind of thing on which libraries can and should be collaborating, and OCLC seems like a logical organization to take the lead.</p>
<p>I do have a couple of questions/concerns. </p>
<ol>
<li><a href="http://www.oclc.org/support/documentation/worldcat/records/guidelines/">OCLC claims and enforces copyrights</a> in its bibliographic records. While it grants member libraries permission to make broad use of those records, my understanding is that the same is not true for non-members. If OCLC extends that policy to the Copyright Evidence Registry, it risks becoming just another walled garden that is useful only to a select (and paying) group of members, and less useful even to that group than it would be if it were truly open. </li>
<li>Right now the registry is sparsely populated. It will take a critical mass of records and contributors to become a trustworthy source of copyright evidence. Where will that critical mass come from? What is OCLC doing to build it quickly? How will users know when the registry has reached it?</li>
</ol>
<p>Via <a href="http://digital-scholarship.org/digitalkoans/2008/08/25/oclc-announces-worldcat-copyright-evidence-registry-beta/">Digital Koans</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2008/08/26/oclcs-new-copyright-evidence-registry/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
		<item>
		<title>Life on the command line</title>
		<link>http://mollykleinman.com/2008/06/27/life-on-the-command-line/</link>
		<comments>http://mollykleinman.com/2008/06/27/life-on-the-command-line/#comments</comments>
		<pubDate>Fri, 27 Jun 2008 13:26:28 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Technology and Web 2.0]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[Dianne Dietrich]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/?p=45</guid>
		<description><![CDATA[A grad school classmate of mine, Dianne Dietrich, has created an excellent set of tutorials for librarians who want to learn how to use command line. Here&#8217;s why: If you&#8217;re a librarian, and you&#8217;re working with lots of information &#8212; &#8230; <a href="http://mollykleinman.com/2008/06/27/life-on-the-command-line/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>A grad school classmate of mine, Dianne Dietrich, has created <a title="Life on the Command Line" href="http://www.hellodot.net/lute/life-on-the-command-line" target="_blank">an excellent set of tutorials</a> for librarians who want to learn how to use command line. Here&#8217;s why:</p>
<blockquote><p>If you&#8217;re a librarian, and you&#8217;re working with lots of information &#8212; and I mean, lots, like information overload lots &#8212; you need to be equipped with a way to handle this information without resorting to mind-numbing data entry methods. No, really. Every time someone says, &#8220;I guess I have to do this exhaustingly repetitive task by hand, I cry a little. It doesn&#8217;t matter if you&#8217;re one thousand miles away; I know, and I weep.</p></blockquote>
<p>The tutorials are funny, easy to understand, and created especially for librarians (the examples use the LC Classification Outline!). I&#8217;ve been having a great time working my way through them, discovering some of the ways that command line can make my life easier, and it&#8217;s just too terrific a resource not to share. If you ever wanted to learn how to use the command line but weren&#8217;t sure where to start, look no further. </p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2008/06/27/life-on-the-command-line/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
		<item>
		<title>Collected stories: Paul Krugman on e-books; Science vs. the RIAA; Cory Doctorow is a bestseller; pictures of libraries</title>
		<link>http://mollykleinman.com/2008/06/13/collected-stories-paul-krugman-on-e-books-science-vs-the-riaa-cory-doctorow-is-a-bestseller-pictures-of-libraries/</link>
		<comments>http://mollykleinman.com/2008/06/13/collected-stories-paul-krugman-on-e-books-science-vs-the-riaa-cory-doctorow-is-a-bestseller-pictures-of-libraries/#comments</comments>
		<pubDate>Fri, 13 Jun 2008 19:11:59 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Collected Stories]]></category>
		<category><![CDATA[Creative Commons Evangelism]]></category>
		<category><![CDATA[Libraries]]></category>
		<category><![CDATA[Publishing]]></category>
		<category><![CDATA[Amsterdam]]></category>
		<category><![CDATA[Cory Doctorow]]></category>
		<category><![CDATA[MPAA]]></category>
		<category><![CDATA[Paul Krugman]]></category>
		<category><![CDATA[RIAA]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/?p=40</guid>
		<description><![CDATA[I just got back from a week of vacation, followed by a week of post-vacation crunch, so here&#8217;s a small assortment of things I would have blogged about sooner, but didn&#8217;t. Paul Krugman says it better In a column titled &#8230; <a href="http://mollykleinman.com/2008/06/13/collected-stories-paul-krugman-on-e-books-science-vs-the-riaa-cory-doctorow-is-a-bestseller-pictures-of-libraries/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I just got back from a week of vacation, followed by a week of post-vacation crunch, so here&#8217;s a small assortment of things I would have blogged about sooner, but didn&#8217;t.</p>
<p><strong>Paul Krugman says it better</strong> In a column titled <a href="http://www.nytimes.com/2008/06/06/opinion/06krugman.html">Bits, Bands, and Books: Paying for Creativity in a Digital World</a>, Paul Krugman describes the impact of the digital revolution on the market for creative content. I think he gets it exactly right. He also calls the Grateful Dead &#8220;business pioneers.&#8221; Who knew? </p>
<blockquote><p>Bit by bit, everything that can be digitized will be digitized, making intellectual property ever easier to copy and ever harder to sell for more than a nominal price. And we’ll have to find business and economic models that take this reality into account.</p></blockquote>
<p><strong>Cory Doctorow and Creative Commons are bestsellers</strong> Like all his other books, Cory Doctorow&#8217;s latest novel, <a href="http://craphound.com/littlebrother/">Little Brother</a>, was released online using a Creative Commons license (BY-NC-SA). Unlike his other books, and unlike any other CC-licensed anything, Little Brother has now <a href="http://www.boingboing.net/2008/06/04/little-brother-goes.html">spent four weeks</a> on the <a href="http://www.nytimes.com/2008/06/15/books/bestseller/0615bestchildren.html">New York Times bestseller list</a>. It&#8217;s the first CC-licensed novel to make the list, and excellent news for people like me who argue that giving stuff away for free online doesn&#8217;t mean you can&#8217;t sell it for profit, too. Also fun to think about in the context of Paul Krugman&#8217;s column on e-books.</p>
<p><strong>Science proves the MPAA and the RIAA are jerks</strong> <a href="http://bits.blogs.nytimes.com/2008/06/05/the-inexact-science-behind-dmca-takedown-notices/">A recent piece in the NYTimes Bits Blog</a> points out <a href="http://dmca.cs.washington.edu/">a study from the University of Washington</a> which showed that the technologies Big Media uses to investigate illegal file sharing regularly produce false positives. </p>
<p>From the Bits blog:</p>
<blockquote><p>In two separate studies in August 2007 and May of this year, the researchers set out to examine who was participating in BitTorrent file-sharing networks and what they were sharing. The researchers introduced software agents into these networks to monitor their traffic. Even though those software agents did not download any files, the researchers say they received more than 400 take-down requests accusing them of participating in the downloads.</p>
<p>The researchers concluded that enforcement agencies are looking only at I.P. addresses of participants on these peer-to-peer networks, and not what files are actually downloaded or uploaded — a more resource-intensive process that would nevertheless yield more conclusive information.</p>
<p>In their report, the researchers also demonstrate a way to manipulate I.P. addresses so that another user appears responsible for the file-sharing. </p></blockquote>
<p><a href="http://chronicle.com/wiredcampus/article/2687/movie-industry-admits-error-in-study-on-campus-piracy">This is not the first time</a> flaws in the RIAA/MPAAs&#8217; strategy have been revealed, and <a href="http://paulcourant.net/2008/01/25/mpaa-bad-universities-goodmpaa-bad-universities-good/">librarians</a> and <a href="http://www.eff.org/">other</a> <a href="http://www.freedom-to-tinker.com/">concerned</a> <a href="http://recordingindustryvspeople.blogspot.com/">parties</a> have been calling for more transparency in their tactics for quite some time. Now opponents of file-sharing lawsuits &#8211; not to mention the defendants in those lawsuits &#8211; have scientific evidence that these tactics implicate innocent people. </p>
<p><strong>Pictures of Libraries</strong> When I travel, instead of collecting souvenirs I like to visit and take pictures of libraries. I saw a few very cool libraries on my recent vacation, including the brand new Openbare Amsterdam Bibliotheek, the Amsterdam public library. I was incredibly impressed with the design of the Amsterdam library. It has a lot of good signage, open spaces and tables for people to hang out and collaborate, tons and tons of computers (both Mac and Windows), good light, inviting stacks that weren&#8217;t too tall, and seemingly intuitive organization (from what I could understand of the Dutch). </p>
<p>If you&#8217;re interested, have a peek at <a href="http://flickr.com/photos/mollyali/sets/72157602816617141/">my Libraries set</a> on Flickr. Also check out the <a href="http://www.oba.nl/index.cfm/t/New_library/vid/53C6A39A-9969-DC55-21E64E8759ACEE68">page about the new library</a> at the <a href="http://www.oba.nl/index.cfm/t/Homepage/vid/BC638BCA-3FFA-497D-9CA1C74A819C832A">Openbare Amsterdam Bibliotheek website</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2008/06/13/collected-stories-paul-krugman-on-e-books-science-vs-the-riaa-cory-doctorow-is-a-bestseller-pictures-of-libraries/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
		<item>
		<title>Library Camp Ann Arbor, 2008</title>
		<link>http://mollykleinman.com/2008/03/21/library-camp-ann-arbor-2008/</link>
		<comments>http://mollykleinman.com/2008/03/21/library-camp-ann-arbor-2008/#comments</comments>
		<pubDate>Fri, 21 Mar 2008 16:23:38 +0000</pubDate>
		<dc:creator>Molly</dc:creator>
				<category><![CDATA[Libraries]]></category>
		<category><![CDATA[AADL]]></category>
		<category><![CDATA[Library Camp]]></category>

		<guid isPermaLink="false">http://mollykleinman.com/2008/03/21/library-camp-ann-arbor-2008/</guid>
		<description><![CDATA[I spent yesterday afternoon at the Ann Arbor District Library, attending Library Camp. I joined the group discussing how to sell Web 2.0 to our colleagues, administrators, and patrons. Overall, I was pretty proud of how the group managed not &#8230; <a href="http://mollykleinman.com/2008/03/21/library-camp-ann-arbor-2008/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I spent yesterday afternoon at the <a href="http://aadl.org">Ann Arbor District Library</a>, attending <a href="http://libsuccess.org/index.php?title=Library_Camp">Library Camp</a>. I joined the group discussing how to sell Web 2.0 to our colleagues, administrators, and patrons.  Overall, I was pretty proud of how the group managed not to devolve into a whine fest about how hard it is to get libraries and librarians to experiment with new technologies, though there were a few requisite moans and groans. A lot of folks in the room had already had some successes introducing 2.0 technologies, and they shared their strategies, which tended to fall into one of two camps:</p>
<ol>
<li><strong>Build first, explain later:</strong> People found that it was very hard to sell anyone on a 2.0 experiment when all they could do was try and describe it. &#8220;Well, <a href="http://twitter.com">Twitter</a> is like microblogging&#8230; Well microblogging is like blogging, but smaller&#8230; Well, blogging is like when people post about different stuff, like news and stuff, and it shows up chronologically on the webpage&#8230;&#8221; etc. If they actually created a few Flickr sets, or set up a blog, it was much easier to demonstrate the utility of such a thing, and they were able to generate buy-in from the administration and the users.</li>
<li><strong>Talk about the ends, not the means: </strong>In trying to explain Web 2.0 technologies to upper level administration, Dave Carter of the University of Michigan focused on their ability to help us better connect with our users, rather than on the details of how they work or what they are. By explaining the end goal &#8211; building a relationship with users, encouraging interaction, and improving services &#8211; he was able to sell the principle of 2.0 without getting bogged down by the minutiae of various sites and and technologies. U of M ended up offering <a href="http://www.lib.umich.edu/lib20/">a whole summer series on Library 2.0</a>, and blogs, wikis, and Facebook have been adopted by librarians all over campus.</li>
</ol>
<p>After the breakout sessions we had a show and tell, where several people got up and demonstrated a cool new thing they&#8217;re doing in their library. They included</p>
<ul>
<li>A video about gaming tournaments for teens at the AADL</li>
<li>All sorts of awesome embedded media in the catalog at <a href="http://www.dalnet.lib.mi.us/demos/">DALNET</a></li>
<li>A library toolbar for Firefox and IE, from <a href="http://www.columbuslibrary.org/">Columbus Metropolitan Libraries</a></li>
<li><a href="http://dplteens.blogspot.com/">A blog run by teens</a> at the Detroit Public Library</li>
<li>A new tagging application, <a href="http://www.lib.umich.edu/news/stories/introducing_mtagger_353.html">MTagger</a>, from the University of Michigan.</li>
</ul>
<p>We also saw a library book blog, but apparently I didn&#8217;t write down the URL or the name. I was especially impressed by all the different embedded media options from DALNET (that&#8217;s Detroit Area Library Network, I think). They&#8217;re doing stuff like embedding movie previews from YouTube in the catalog, so that if a patron is looking at a record for <em>Spiderman 2</em>, she could actually watch the preview right there on the page. And they&#8217;re doing it all with MARC! Very cool.</p>
<p>It was nice to meet librarians from all over the Midwest, and also to be reminded of some of the stuff I&#8217;ve been meaning to experiment with but just haven&#8217;t gotten around to. When I learned that there was no Wikipedia entry for the AADL, I went home and <a href="http://en.wikipedia.org/wiki/Ann_Arbor_District_Library" title="Wikipedia article on AADL">created one</a>, my first ever new Wikipedia article (it&#8217;s still a stub &#8211; go edit it!). I also decided to take my Twittering to the next level, to see if I can finally understand what the fuss is about. If you&#8217;re interested, follow me at <a href="http://twitter.com/mollyali">http://twitter.com/mollyali</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://mollykleinman.com/2008/03/21/library-camp-ann-arbor-2008/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	<cc:license>Attribution CC BY</cc:license><dc:rights>Attribution CC BY</dc:rights>	</item>
	</channel>
</rss>

